On 27/06/2019 23:07, Michal Suchánek wrote:
On Sat, 22 Jun 2019 13:02:10 +0200 Richard Brown <RBrownCCB@opensuse.org> wrote:
On Sat, 22 Jun 2019 at 12:09, Simon Lees <sflees@suse.de> wrote:
No my criticism of what you'd like to do is intentional, as someone who spends a lot of time looking at small things across many many packages I appreciate the fact that there are certain rules all packages follow to make them the same, one such rule is if I am dealing with a large changes file I can put a patches filename into the search field of my editor and find when the patch was added / removed, I don't want to have to skim 5000 lines of a changes file manually to find vdr-${cur_ver}-01..42"vdr-${cur_ver}-01..42" even if yes having 40 patches listed in a changes file doesn't look as "pretty" changes files should be about function over prettyness. But I guess we are going to have to agree to disagree, although if as others have said more people agree with you then me the rule could be changed. But don't dismiss the way it is now and not allowing exceptions as completely illogical there is at least a small amount of logic behind it.
+1
As a release engineer who has regular cause to analyse, debug, and assist on dozens, if not hundreds of packages across the distribution, almost all of which are nominally maintained by other people, there is no way I want to learn all the various anachronistic standards of hundreds of different packagers.
"vdr-${cur_ver}-01..42" might make sense for the VDR maintainer, but there are thousands of packages and they all need to work together and I don't have the time or the inclination to learn every maintainers quirky way of documenting what they're doing.
I need to be able to know when a patch was added, and when it was removed. Such changes are one of the most likely causes of packaging or functional problems with a package. I need to be able to look that up using simple things like filenames in changelogs. Any alternative standard requires more work for maintainers, because I'm going to be less able to help with their package, and with so many packages in the distro, anyone with a package at the bottom of the pile is likely to find it dropped before I can help fix it.
I am not a bot, and the rule that is enforced by the factory-auto bot is for the benefit of contributors like myself and the others like me who work across the entire distribution rather than treating a handful of packages like private little fiefdoms.
Please look at this topic with less ego, and more consideration of the needs of collaboration with others please.
So why don't you as release engineers use OBS to tell you which patch was added and removed when?
OBS's ability to search history is poor to non existent atleast from the webui, where as its quite quick and simple to open the changelog in your browser and hit ctrl+f. I didn't try using obs to search for a patch for rather a long time, so there is a chance its better, but thats just my past experience. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org