Re: Trouble creating modular metadata for local repo

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2020-01-07 9:05 a.m., Petr Pisar wrote:
> On 2020-01-07, Digimer <lists@xxxxxxxxxx> wrote:
>>   I'm trying to create a local repo of an offline collection of systems.
>> When I try to install, I get:
>>
>> ====
>> No available modular metadata for modular package 'foo.arch', it cannot
>> be installed on the system
>> ====
>>
> I guess the 'foo.arch' name is made up and it is actually a package
> provided by Fedora. Because there is no such package in Fedora and thus
> DNF should not suppose that the package is modular.
> 
> Otherwise if it were a new unique yet modular package, there have to be
> the "modules.yaml" file listing it. And in that case you would know what
> modules are and how they are built and put into a repository.
> 
> Could you explain us what the 'foo.arch' is in your case?
> 
> -- Petr

Since I wrote this, I've made some progress.

I've taken the 'modules.yaml' file from the RHEL 8.1 ISO as a source,
and now I can generate the modules.yaml file. The resolves the error for
all RPMs already listed, but I am trying to add 'libssh2' without luck.

I followed:
https://docs.fedoraproject.org/en-US/modularity/making-modules/defining-modules/
and tried to add this;

====
---
document: modulemd
version: 2
data:
  name: libssh2
  stream: 1.8
  arch: x86_64
  summary: A library implementing the SSH2 protocol
  description: >-
    libssh2 is a library implementing the SSH2 protocol as defined by
    Internet Drafts: SECSH-TRANS(22), SECSH-USERAUTH(25),
    SECSH-CONNECTION(23), SECSH-ARCH(20), SECSH-FILEXFER(06)*,
    SECSH-DHGEX(04), and SECSH-NUMBERS(10).

  license:
    module:
    - BSD
  dependencies:
  - buildrequires:
      platform: []
    requires:
      platform: []
  profiles:
    default:
      rpms:
      - libssh2
  api:
    rpms:
    - libssh2
  components:
    rpms:
      libssh2:
        rationale: Main libssh2 Package
        ref: latest
        arches: [aarch64, i686, ppc64le, s390x, x86_64]
...
---
document: modulemd-defaults
version: 1
data:
  module: libssh2
  stream: 1.8
  profiles:
    default [common]
...
====

  When I generate the modules.yaml using 'modifyrepo_c', I can see the
libssh2 entries get added to the repodata/<hash>-modules.yaml.gz file.
However, when I try to install, it still throws;

====
Dependencies resolved.
====================================================================
 Package      Architecture   Version
               Repository                           Size
====================================================================
Installing:
 libssh2      x86_64         1.8.0-8.module+el8.0.0+4084+cceb9f44.1
 el8-striker01-repo                   99 k

Transaction Summary
====================================================================
Install  1 Package

Total download size: 99 k
Installed size: 199 k
Is this ok [y/N]: y
Downloading Packages:
libssh2-1.8.0-8.module+el8.0.0+4084+cceb9f44.1.x86_64.rpm
                                               41 MB/s |  99 kB
00:00
--------------------------------------------------------------------
Total
                                              9.7 MB/s |  99 kB
00:00
Running transaction check
No available modular metadata for modular package
'libssh2-1.8.0-8.module+el8.0.0+4084+cceb9f44.1.x86_64', it cannot be
installed on the system
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: No available modular metadata for modular package
====

  I know this is RHEL 8, but the documentation is from Fedora (I can't
find anything related to this regarding RHEL specifically). Hopefully I
can still get help here. :)

-- 
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux