Bug 1318293 - packages/RemovedPackages: don't remove foreign packages
Summary: packages/RemovedPackages: don't remove foreign packages
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: preupgrade-assistant-el6toel7
Version: 6.8
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Petr Stodulka
QA Contact: Alois Mahdal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-16 13:02 UTC by Alois Mahdal
Modified: 2019-07-01 15:31 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-01 15:31:13 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github upgrades-migrations preupgrade-assistant-modules issues 108 0 None None None 2018-10-04 16:37:33 UTC

Description Alois Mahdal 2016-03-16 13:02:42 UTC
Description of problem
======================

After upgrade, all packages that start with 'preupgrade-assistant' are
removed.  If user's package starts with this string, it will be removed.

We should only remove packages that we own (i.e. based on hard-coded list or RH signature).


Version-Release number of selected component
============================================

redhat-upgrade-tool-0.7.43-1.el6.noarch
preupgrade-assistant-2.1.5-3.el6.noarch
preupgrade-assistant-el6toel7-0.6.45-1.el6.noarch
preupgrade-assistant-el6toel7-data-0.20160125-1.el6.noarch
preupgrade-assistant-tools-2.1.5-3.el6.noarch
preupgrade-assistant-ui-2.1.5-3.el6.noarch


How reproducible
================

Always


Steps to Reproduce
==================

 1. Install custom package starting with 'preupgrade-assistant',
    possibly without 'el6' in Release

 2. Perform upgrade

     *  I have used --cleanup-post, but I'm not sure if it's needed
        to reproduce

 3. Check your package


Actual results
==============

The package is gone


Expected results
================

The package should be still present (unless it *depends* on one of
our packages)

Comment 4 Petr Stodulka 2019-07-01 15:31:13 UTC
Closing this bugzilla as the component is under a maintenance mode in which the maintainers are going to fix only critical bugs. If you consider the bugzilla critical, feel free to reopen the bug with an explanation.


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