[Bug-cssc] [bug #57240] new error handling causes non-zero exit statuses even for warnings

[anonymous]

URL:
  <https://savannah.gnu.org/bugs/?57240>

                 Summary: new error handling causes non-zero exit statuses
even for warnings
                 Project: GNU CSSC
            Submitted by: None
            Submitted on: Fri 15 Nov 2019 07:44:51 AM UTC
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

It seems as if new error handling code now caused CSSC commands to exit with a
non-zero status even for warnings.

E.g. `get` will exit with an exit status of 1 whenever it extracts a file
without keywords and gives a "No id keywords" warning:


$ /work/woods/g-cssc/build-x64-netbsd/src/get -p -s -a1
usr.sbin/sendmail/src/SCCS/s.main.c > /dev/null                
/work/woods/g-cssc/build-x64-netbsd/src/get: warning:
usr.sbin/sendmail/src/SCCS/s.main.c: No id keywords
$ echo $?
1


This is new, and very undesirable, behaviour from how 1.4.0 behaved.

Interestingly neither Heirloom SCCS nor Schily SCCS even bother with the
warning for this particular file:


$ /usr/local/heirloom-ccs/bin/get  -p -s -a1
usr.sbin/sendmail/src/SCCS/s.main.c > /dev/null                           
$ echo $?
0
$ /usr/local/ccs/bin/get  -p -s -a1 usr.sbin/sendmail/src/SCCS/s.main.c >
/dev/null          
$ echo $?                                                                     
     
0





    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57240>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/