[bug-notifications] [mgar 0004834]: mgar doesn't assert SPKG_PACKAGER / SPKG_EMAIL

Mantis Bug Tracker noreply at opencsw.org
Sun Sep 25 13:11:33 CEST 2011


A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4834 
====================================================================== 
Reported By:                skayser
Assigned To:                skayser
====================================================================== 
Project:                    mgar
Issue ID:                   4834
Category:                   regular use
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2011-09-25 12:56 CEST
Last Modified:              2011-09-25 13:11 CEST
====================================================================== 
Summary:                    mgar doesn't assert SPKG_PACKAGER / SPKG_EMAIL
Description: 
When using mgar for the first time you might not have taken care of your
~/.garrc. When you then execute e.g. mgar package, mgar will just trigger
GAR which in turn will complain loudly (but not fail hard) with each
invocation.

...
        ==> Trying file://files/COPYING
/home/skayser/mgar/pkg/.buildsys/v2/gar//gar.pkg.mk:175: Please set
SPKG_PACKAGER in your .garrc file to your name
/home/skayser/mgar/pkg/.buildsys/v2/gar//gar.pkg.mk:180: Please set
SPKG_EMAIL in your .garrc file to your email address
...

Let mgar assert these settings and provide a template ~/.garrc that's
displayed to the user if the settings are missing.
====================================================================== 

---------------------------------------------------------------------- 
 (0009302) skayser (administrator) - 2011-09-25 13:11
 https://www.opencsw.org/mantis/view.php?id=4834#c9302 
---------------------------------------------------------------------- 
Also consider to disable Git patching in the ~/.garrc template
(NOGITPATCH=1) so that new users don't need to set the git config bits
(user.email, user.name) right away, but can do so, once they start creating
patches.



More information about the bug-notifications mailing list