Skip to Content.
Sympa Menu

sm-grimoire-bugs - [SM-Grimoire-Bugs] [Bug 16113] New: deprecation of gnupg (casting gnupg-2.2) leaves cleanse confused with gnupg dependencies

sm-grimoire-bugs AT lists.ibiblio.org

Subject: SourceMage Grimoire Bug List

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-grimoire-bugs AT lists.ibiblio.org
  • Subject: [SM-Grimoire-Bugs] [Bug 16113] New: deprecation of gnupg (casting gnupg-2.2) leaves cleanse confused with gnupg dependencies
  • Date: Sat, 18 May 2019 08:11:33 +0000

Bug ID 16113
Summary deprecation of gnupg (casting gnupg-2.2) leaves cleanse confused with gnupg dependencies
Product Codex
Version test grimoire
Hardware x86
OS Linux
Status NEW
Severity normal
Priority P2
Component crypto
Assignee sm-grimoire-bugs AT lists.ibiblio.org
Reporter sobukus AT sourcemage.org
Classification Unclassified

I started with stable-0.62 chroot and upgraded to test. After various
issues (lib soname changes, sorcery being incompatible with bash 5.0), I
am surprised by cleanse complaining about gnupg dependencies after
gnupg has been dispelled in favour of gnupg-2.2. First was
smgl-archspecs. It was fixed by re-casting. Then followed bzip2, so
I presume it is a common pattern:

# cleanse
Fixing packages...
Pass 1 (bad lines)
Pass 2 (non-existant spells)
Pass 3 (duplicate entries)
Done fixing packages.
Delinting...
Pass one (malformed depends lines)
Pass two (stale depends entries)
    0 bad lines, 460 good lines in your depends file.
Pass three (duplicate depends entries)
Pass four (duplicate sub_depends entries)
Pass five (stale sub_depends entries)
    0 bad lines, 8 good lines in your sub_depends file.
Pass six (duplicate trigger entries)
Pass seven (stale trigger entries)
    0 bad lines, 34 good lines in your trigger file.
Delint done.
Cleaning log files...
Pruning...
bzip2 needs gnupg (required).
    (0)  Ignore
    (1)  Dispel bzip2
    (2)  Cast gnupg

I'll just do a rebuild now, but it would probably be better to find a proper
fix.


You are receiving this mail because:
  • You are the assignee for the bug.



Archive powered by MHonArc 2.6.24.

Top of Page