You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
--revision currently a) refuses to bump the revision of projects with
upstream Meson support or whose current version is not tracked by Anitya
and b) bumps the version instead of the revision if a new version is
available. Both behaviors are based on faulty assumptions. We might
plausibly want to bump a wrap's revision after changing the wrap file,
regardless of the project's status in other respects. And it's reasonable
to want to fix something in a Meson port without taking responsibility for
updating it to the latest version.
Change the semantics of --revision to always bump the revisions of the
specified wraps, even if --port is not specified. If no wraps are
specified, bump all wraps for consistency.
Rework the help text to describe the various things autoupdate can do,
rather than only emphasizing projects with upstream Meson support.
description='Attempt to automatically update wraps that support Meson upstream.'
375
+
help='automatically update wraps',
376
+
description="Automatically update wraps that support Meson upstream, update metadata only (releases.json and *.wrap) for wraps that don't, or increment wrap revision in releases.json."
357
377
)
358
378
autoupdate.add_argument(
359
379
'names', metavar='name', nargs='*', help='wrap to update'
360
380
)
361
381
autoupdate.add_argument(
362
382
'-p', '--port', action='store_true',
363
-
help='allow updating wraps with Meson support added in wrapdb'
383
+
help='allow updating metadata for wraps without upstream Meson support',
364
384
)
365
385
autoupdate.add_argument(
366
386
'-r', '--revision', action='store_true',
367
-
help="update port's revision if version is current"
387
+
help='increment wrap revision and do nothing else'
0 commit comments