297933 – BASHOPTS needs filtering from environment with bash-4.1

Bug 297933 - BASHOPTS needs filtering from environment with bash-4.1

Summary: BASHOPTS needs filtering from environment with bash-4.1

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core - Ebuild Support (show other bugs)
Hardware:	All All

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:	InVCS

Depends on:
Blocks:	288499
	Show dependency tree

Reported:	2009-12-22 19:44 UTC by SpanKY
Modified:	2012-05-23 01:15 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description SpanKY gentoo-dev

2009-12-22 19:44:26 UTC

bash-4.1 introduces a new read-only variable (BASHOPTS).  it'll need to be filtered when saving/restoring the environment.  i dont know how you guys manage these save/restore steps, but portage shows multiple:
/var/tmp/portage/app-shells/bash-4.1_rc1/temp/environment: line 7: declare: BASHOPTS: readonly variable

you'll probably want to get this fixed before bash-4.1 is released and i add to the tree ...

Comment 1 Arfrever Frehtes Taifersar Arahesis (RETIRED) gentoo-dev

2009-12-22 20:08:22 UTC

It should be fixed in r15130.

Comment 2 Brian Harring (RETIRED) gentoo-dev

2009-12-23 01:08:28 UTC

Thanks for the heads up, committing it now, will hit the tree w/in the week or so as pkgcore 0.5.7.

Comment 3 Ciaran McCreesh 2009-12-23 22:21:04 UTC

Thanks. Is there a rough estimate of when 4.1's going to be out? I'm wondering whether it's worth backporting and doing a minor release with this in.

Comment 4 SpanKY gentoo-dev

2009-12-24 01:41:42 UTC

no idea really ... the bash release process doesnt seem to be consistent:

http://lists.gnu.org/archive/html/bug-bash/2009-12/msg00139.html

Comment 5 Zac Medico gentoo-dev

2009-12-24 06:29:29 UTC

(In reply to comment #1)
> It should be fixed in r15130.

This is in portage-2.1.7.16 and 2.2_rc61. If the message is just a warning then I guess there's we don't need to make bash-4.1 block older portage.

Comment 6 SpanKY gentoo-dev

2010-01-05 00:53:06 UTC

ive added bash-4.1 to the tree now (no KEYWORDS atm)

if there's some version it should block, now is the time to commit and/or comment

ive added !<sys-apps/portage-2.1.7.16

Comment 7 Zac Medico gentoo-dev

2012-05-23 01:15:13 UTC

(In reply to comment #6)
> ive added !<sys-apps/portage-2.1.7.16

I've backported the fix to portage-2.1.6.7_p1, and adjusted the blocker accordingly. This should not hurt people upgrading from later portage-2.1.6.x or 2.1.7.x releases, since the message about BASHOPTS being readonly is only cosmetic.