lbu commit generates error if a blank line exists in include file
If a blank line exists anywhere in the /etc/lbu/include file for some reason, then running lbu ci will generate the following error:
alpinebox:~# lbu ci
tar: : No such file or directory
tar: error exit delayed from previous errors
The apkovl files are still generated correctly, however. I wonder if blank lines could be ignored, or the error message be improved? For example: “Ignoring blank line in include/exclude file”, which the user could then choose to remove manually.
Thanks!
(from redmine: issue id 713, created on 2011-07-26, closed on 2011-08-25)
- Changesets:
- Revision 98bf351b by Natanael Copa on 2011-08-11T08:07:43Z:
main/alpine-conf: upgrade to 2.8.2
ref #687
ref #713
- Revision 8d795d1760f28bedfe605515c7c770389768b5fb by Natanael Copa on 2011-08-11T08:29:23Z:
lbu: do not edit users config
Cope with empty lines in include/exclude without editing the file
ref #713
- Revision 2eead233b82949c359e5659de1d91635d7921750 by Natanael Copa on 2011-08-11T09:54:58Z:
lbu: do not edit users config
Cope with empty lines in include/exclude without editing the file
ref #713
(cherry picked from commit 8d795d1760f28bedfe605515c7c770389768b5fb)
Conflicts:
lbu.in
- Revision 3c17090c by Natanael Copa on 2011-08-23T13:28:27Z:
main/alpine-conf: upgrade to 2.8.2
fixes #687
fixes #713
(cherry picked from commit 98bf351bafa4258da0f7f2989963613cc6e17291)
Conflicts:
main/alpine-conf/0001-setup-disk-fix-data-only-mode-with-no-lvm-and-no-rai.patch
main/alpine-conf/APKBUILD