Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 72134 - up2date-nox ignores --force flag
up2date-nox ignores --force flag
Product: Red Hat Public Beta
Classification: Retired
Component: up2date (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Jay Turner
: 72166 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2002-08-21 08:01 EDT by Markku Kolkka
Modified: 2015-01-07 18:59 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-08-21 08:01:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Markku Kolkka 2002-08-21 08:01:00 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020809

Description of problem:
I was trying to use the console version of (null) up2date to install the new
kernel, but it just tells that the package is marked to be skipped enven if I
use the -f/--force option.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.up2date-nox --force kernel

Actual Results: The following message:
The following Packages were marked to be skipped by your configuration:

Name                                    Version        Rel  Reason
kernel                                  2.4.18         12.2 Pkg name/pattern

None of the packages you requested were found, or they are already updated.

Expected Results:  The kernel RPM is downloaded and installed

Additional info:
Comment 1 Adrian Likins 2002-08-21 15:52:12 EDT
should be fixed in 2.9.50
Comment 2 Adrian Likins 2002-08-21 15:53:26 EDT
*** Bug 72166 has been marked as a duplicate of this bug. ***
Comment 3 Adrian Likins 2002-08-21 15:55:10 EDT
*** Bug 72166 has been marked as a duplicate of this bug. ***

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