170119 – YaST2 "untabooed" packages during update

Bug 170119 - YaST2 "untabooed" packages during update

Summary: YaST2 "untabooed" packages during update

Status:	RESOLVED DUPLICATE of bug 164445
Duplicates (1):	233348 (view as bug list)

Alias:	None

Product:	SUSE Linux 10.1
Classification:	openSUSE
Component:	Installation (show other bugs)
Version:	RC 2
Hardware:	Other Other

Priority:	P5 - None Severity: Enhancement (vote)
Target Milestone:	---
Assignee:	Michael Andres
QA Contact:	Jiri Srain

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2006-04-27 10:38 UTC by Lars Marowsky-Bree
Modified:	2007-01-12 03:29 UTC (History)
CC List:	3 users (show)

See Also:
Found By:	Development
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
yast2 logs (492.83 KB, application/x-bzip2) 2006-04-27 10:40 UTC, Lars Marowsky-Bree	Details
View All 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 Lars Marowsky-Bree 2006-04-27 10:38:57 UTC

When I updated my system from b9 to Build 1011, YaST2 removed the taboo restriction from the AppArmor packages. I thought that "taboo" meant the packages would _never_ be installed?

I'll attach logs.

Comment 1 Lars Marowsky-Bree 2006-04-27 10:40:58 UTC

Created attachment 80476 [details]
yast2 logs

Comment 2 Stephan Binner 2006-04-27 11:13:15 UTC

afaik "Taboo" state is never saved, it's lost as soon as you leave the package manager (prior to your update).

Comment 3 Michael Gross 2006-04-27 12:30:27 UTC

That would make this an Enhancement. Reassigning to Jiri.

Comment 4 Jiri Srain 2006-08-21 11:25:33 UTC

Michael, is there an easy way to store the status of objects in the pool?

Comment 5 Stephan Binner 2007-01-11 11:12:29 UTC

*** Bug 233348 has been marked as a duplicate of this bug. ***

Comment 6 macias - 2007-01-11 12:46:39 UTC

Saving taboo status?
Is this bug report duplicate of
https://bugzilla.novell.com/show_bug.cgi?id=164445

Comment 7 Cristian Rodríguez 2007-01-12 03:29:55 UTC

yes it is the same problem



*** This bug has been marked as a duplicate of bug 164445 ***