| Summary: | bleachbit-4.1.0-1.mga8.noarch is not yet updated whereas version 4.4.2 is already released | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | peter lawford <petlaw726> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | andrewsfarm, davidwhodgins, herman.viaene, sysadmin-bugs |
| Version: | 8 | Keywords: | advisory, validated_update |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | MGA8-64-OK | ||
| Source RPM: | bleachbit-4.1.0-1.mga8.noarch | CVE: | |
| Status comment: | |||
|
Description
peter lawford
2022-05-21 17:17:47 CEST
Is there some other reason to update than "there's a new version available"? Security? Major bug fixes? According to Mageia updates policy [1] "Updates are not the appropriate place for packages created to satisfy certain user's urges for "the latest". These types of builds belong in backports." [1] https://wiki.mageia.org/en/Updates_policy#Version_Policy Thank you Peter for the hint. Await your reply. Yes, please say why it matters. Such requests usually say something like "provides imortant new features or bugfixes", and give a relevant upstream URL (release note). Jani's comment about simply wanting the latest version of something is valid for our current release; but Cauldron should normally have latest versions for our next release, so such alerts are helpful for that. But I see Jani has just done "new version 4.4.2" in Cauldron, so please excuse me for assigning you this request. Do with it what you will: re-assign, bounce, straight update, backport. Assignee:
bugsquad =>
jani.valimaa (In reply to Lewis Smith from comment #2) > Thank you Peter for the hint. Await your reply. > Yes, please say why it matters. Such requests usually say something like > "provides imortant new features or bugfixes", and give a relevant upstream > URL (release note). > Jani's comment about simply wanting the latest version of something is valid > for our current release; but Cauldron should normally have latest versions > for our next release, so such alerts are helpful for that. > > But I see Jani has just done "new version 4.4.2" in Cauldron, so please > excuse me for assigning you this request. Do with it what you will: > re-assign, bounce, straight update, backport. updating doesn't especially matter, but every time I open the gui, it says me that le last version 4.4.2 is released, with a link to the URL, and it seems to me that updating wouldn't be a bad thing. But I've founded 4.4.2 version in cauldron We should disable the update check. (In reply to Jani Välimaa from comment #4) > We should disable the update check. Please test bleachbit-4.1.0-1.1.mga8 from core/updates_testing. RPMS/SRPMS: bleachbit-4.1.0-1.1.mga8 Assignee:
jani.valimaa =>
qa-bugs MGA8-64 Plasma on Lenovo B50 No installation issues. Picked some options and let it run, results seems OK. CC:
(none) =>
herman.viaene Validating. Keywords:
(none) =>
validated_update For the advisory, does this update just disable the upstream update check or is it a new version? CC:
(none) =>
davidwhodgins Advisory committed to svn as
type: bugfix
subject: Updated bleachbit packages fixes update notice
src:
8:
core:
- bleachbit-4.1.0-1.1.mga8
description: |
Updated bleachbit packages fixes update notice by disabling check for
newer release upstream.
references:
- https://bugs.mageia.org/show_bug.cgi?id=30461Keywords:
(none) =>
advisory An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2022-0075.html Resolution:
(none) =>
FIXED |