Summary: | sys-apps/openrc-0.6.1 network script has syntax errors | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Leonid Podolny <leonidp.lists> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | roy, sharkman.ru, weeve3 |
Priority: | High | ||
Version: | 10.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 295613 | ||
Attachments: |
Patches syntax error and a few spurious indentations
openrc-0.6.1-network-initd-fix.patch |
Description
Leonid Podolny
2010-03-22 22:36:41 UTC
maybe need add a line of ";;" before line "*)" ? but this is need to be confirmed. =sys-apps/openrc-0.6.1 sharkman-work ~ # /etc/init.d/network status /etc/init.d/network: line 77: syntax error near unexpected token `)' /etc/init.d/network: line 77: ` *)' * status: started sharkman-work ~ # Created attachment 224819 [details, diff]
Patches syntax error and a few spurious indentations
Upstream should know about this as well... Created attachment 224911 [details, diff]
openrc-0.6.1-network-initd-fix.patch
Cleaner patch without the useless whitespace fixes...
Seriously, how did this make it into the tree? (In reply to comment #6) > Seriously, how did this make it into the tree? > These things happen to everyone, it's absolutely normal. Roy: `git log` on 0276c4f5164f053346dd585639161995ac0e6e75 also shows some whitespace damage in the new network code you might want to fix ive added Lars' patch to 0.6.1-r1 Weeve: /etc/init.d/network isnt the default (/etc/init.d/net is), so i'm not surprised it slipped in. i wouldnt have noticed it myself. also, ive added a shell syntax check to the QA post install to make sure this doesnt happen again to any ebuild http://sources.gentoo.org/portage/main/trunk/bin/misc-functions.sh?r1=15842&r2=15843 My bad, I commited that bit by mistake. It's unfinished :/ This is fixed in upstream git, so it will be in the next release. |