68354 – emerge block, dependencies of modutils and module-init-tools broken?

Bug 68354 - emerge block, dependencies of modutils and module-init-tools broken?

Summary: emerge block, dependencies of modutils and module-init-tools broken?

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-10-21 00:09 UTC by caspar-gentoo-bugs
Modified:	2004-10-21 03:12 UTC (History)
CC List:	0 users

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 caspar-gentoo-bugs 2004-10-21 00:09:47 UTC

After updating portage from 2.0.50-r11 to 2.0.51 this morning I tried `emerge -Dup system` and got a blocking error:

[blocks B     ] sys-apps/modutils (from pkg sys-apps/module-init-tools-3.0-r2)
[blocks B     ] sys-apps/module-init-tools (from pkg sys-apps/modutils-2.4.25)

Both packages were installed according to qpkg and etcat.

So I unmerged modutils which removed the block with `emerge -Dup system`.

Out of curiosity I reinstalled module-init-tools on one machine which then utilized modutils-2.4.27, which as a standalone package is marked unstable.


bye

caspar

Reproducible: Always
Steps to Reproduce:
1. emerge sync
2. emerge -v portage
3. emerge -Dup system
Actual Results:  
Blocking notice as described above.

Expected Results:  
Don't know what was intended.

Comment 1 Jason Stubbs (RETIRED) gentoo-dev

2004-10-21 03:12:39 UTC

This is correct behaviour. portage-2.0.50 missed some blocks that portage-2.0.51 doesn't.