Bug 8613 - [WISH] Make it possible to hide an update if you've already installed your own created package
Summary: [WISH] Make it possible to hide an update if you've already installed your ow...
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-06 16:44 CET by Kristoffer Grundström
Modified: 2014-08-18 15:32 CEST (History)
4 users (show)

See Also:
Source RPM: mgaonline
CVE:
Status comment:


Attachments

Description Kristoffer Grundström 2013-01-06 16:44:12 CET
Description of problem: I remember when using Windows that once you're offered an update of something installed you can rightclick it in the list inside mgaonline & choose Hide update so that if you feel like going back to an official version from the repo you can easily check what packages you're hiding & then unhide it to install the update.

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

Steps to Reproduce:
1. Add medias.
2. Choose to get updates from thoose medias.
3. Once you're getting a message about an update, open mgaonline & right the update & choose to hide it. Click Exit that window.
4. Wait for urpmi to look for updates & it shouldn't show any.
Comment 1 Manuel Hiebel 2013-01-21 23:11:36 CET
you can do that with the skip.list

Component: Release (media or process) => RPM Packages

Comment 2 Remco Rijnders 2014-08-18 13:23:42 CEST
Closing.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME

Comment 3 Kristoffer Grundström 2014-08-18 14:36:26 CEST
Yes, but how many people that have just started to bild their own package/s know that this solution exists?
Comment 4 Marja Van Waes 2014-08-18 15:05:55 CEST
(In reply to Manuel Hiebel from comment #1)
> you can do that with the skip.list

(In reply to Kristoffer Grundström from comment #3)
> Yes, but how many people that have just started to bild their own package/s
> know that this solution exists?

A fast google search doesn't show we documented this in wiki (other than for Mga2), or in our official documentatio. It would be nice to at least have it documented in one of the pages that apprentices are expected to read.

cc'ing documentation team and malo (mentoring leader)

CC: sysadmin-bugs => doc-bugs, marja11, pmdenielou

Comment 5 Remco Rijnders 2014-08-18 15:13:06 CEST
IMHO, one would ideally take the Mageia package when offered. Once you go to building your own RPM's, with no desire to (eventually) use the Mageia provided builds, you are on your own.

As demonstrated by Manuel, what is asked for is possible. I'm not sure to what extent we should further promote this for the average user.
Comment 6 Rémi Verschelde 2014-08-18 15:18:43 CEST
I don't see a need for a new feature. If you're capable of building your own packages, it means you are already a relatively advanced user and one can expect you to edit the skip.list to fit your needs. I don't think there are many users who build their own packages and don't want newer versions coming from the updates repo.

If you want to make sure that your home-made packages will not be overridden by official Mageia ones, you can probably set a high epoch number (e.g. Epoch: 10).

CC: (none) => remi

Comment 7 Rémi Verschelde 2014-08-18 15:19:13 CEST
Documenting the skip.list in the wiki would be good though.
Comment 8 Marja Van Waes 2014-08-18 15:32:26 CEST
(In reply to Remco Rijnders from comment #5)
> 
> As demonstrated by Manuel, what is asked for is possible. I'm not sure to
> what extent we should further promote this for the average user.

Well, anyone can be that one exception for whom a certain update breaks things, while others aren't affected. When that happens, it is nice to know how to use the skip.list after downgrading the package, until a fix is pushed.

We still need to document "urpmi --downgrade", too, btw
https://bugs.mageia.org/show_bug.cgi?id=6655#c16

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