Bug 80763 – [net-im/jabberd-2.0_p20050119] debug-flag -> RESTRICT is read-only

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Denis Knauf 2005-02-04 11:45:54 UTC]

>>> Source unpacked.
/usr/lib/portage/bin/ebuild.sh: line 53: append-flags: command not found
/usr/lib/portage/bin/ebuild.sh: line 54: RESTRICT: readonly variable
>>> Test phase [not enabled]: net-im/jabberd-2.0_p20050119

the lines in the ebuild:
    use debug && {
        append-flags -O -ggdb -DDEBUG
        RESTRICT="${RESTRICT} nostrip"
        myopts="${myopts} --enable-debug"
    }

[Comment 1 Thomas Kjosmoen 2005-02-20 20:48:39 UTC]

I've got the same problem. I commented out the RESTRICT line in order to be able to debug. I'm not sure if that was wise, but at least it worked.

[Comment 2 Wolfram Schlich (RETIRED) 2005-03-12 03:28:55 UTC]

"inherit flag-o-matic" was missing -- fixed and committed.
please sync your trees in some hours, test and report.
thanks!

[Comment 3 Thomas Kjosmoen 2005-03-20 01:59:21 UTC]

Just tested, and I got this error message:

>>> Source unpacked.
/usr/lib/portage/bin/ebuild.sh: line 53: RESTRICT: readonly variable
>>> Test phase [not enabled]: net-im/jabberd-2.0_p20050119

>>> Install jabberd-2.0_p20050119 into /var/tmp/portage/jabberd-2.0_p20050119/image/ category net-im
make: *** No rule to make target `install'.  Stop.

[Comment 4 Pupeno 2005-05-01 21:55:07 UTC]

I'm still getting the same error on 2.0s8!

>>> md5 files   ;-) files/self-cert.jabberd-2.sh
>>> md5 src_uri ;-) jabberd-2.0s8.tar.gz
>>> Unpacking source...
>>> Unpacking jabberd-2.0s8.tar.gz to /var/tmp/portage/jabberd-2.0.8/work
>>> Source unpacked.
/usr/lib/portage/bin/ebuild.sh: line 53: RESTRICT: readonly variable
>>> Test phase [not enabled]: net-im/jabberd-2.0.8

>>> Install jabberd-2.0.8 into /var/tmp/portage/jabberd-2.0.8/image/ category net-im
make: *** No rule to make target `install'.  Stop.

[Comment 5 Michael Hordijk 2005-11-28 06:46:18 UTC]

I just ran into this today with 2.0.9.  With this package, I am using debug to
get an increased level of output from "/usr/bin/jabberd -D."  I'm not concerned
with whether the binary has symbols in it or not.  Regardless, the ebuild in the
tree is quite obviously _broken_ (i.e. the dabug flag will cause the ebuild to
die).  That should be fixed at a minimum (its a one line change that doesn't
even require a -r bump).

[Comment 6 Jakub Moc (RETIRED) 2006-05-04 02:57:47 UTC]

Still broken in 2.0.9, please punt that ebuild from portage (and 2.0.10 as well, both are vulnerable to Bug 126978). 2.0.11 is fixed.

[Comment 7 Krzysztof Pawlik (RETIRED) 2006-10-04 10:55:42 UTC]

(In reply to comment #6)
> Still broken in 2.0.9, please punt that ebuild from portage (and 2.0.10 as
> well, both are vulnerable to Bug 126978). 2.0.11 is fixed.

Done