Hello, Koji dist-repo creates the repos and populates them with the signed packages in Koji shared storage. That's good, but in our case, we need to have this information on another machine in a directory to be shared with our community. With mash we could download this information from Koji. I was thinking that if I could have a similar result using Pungi, that would be great. Or if there is a way to download the result of the dist-repo from Koji, that will also be helpful. Do you have a suggestion?
Kind regards, Marta Vila Fernandes ________________________________ De: Michael McLean <mi...@redhat.com> Enviado: 7 de novembro de 2022 16:28 Para: Discussion of Fedora build system <buildsys@lists.fedoraproject.org> Cc: Alex Iribarren <alex.iribar...@cern.ch> Assunto: Re: Using Pungi instead of Mash Indeed, dist-repos were written to more or less replace mash. On Mon, Nov 7, 2022 at 6:44 AM Tomas Kopecek <tkope...@redhat.com<mailto:tkope...@redhat.com>> wrote: Maybe misleading, but isn't koji's dist-repo command sufficient here? It looks to me that you're not doing any sophisticated rpm list preparation, nor using multilib, etc. So, maybe using just koji could work for you? On Mon, Nov 7, 2022 at 12:14 PM Marta Vila Fernandes <marta.vila.fernan...@cern.ch<mailto:marta.vila.fernan...@cern.ch>> wrote: > > > Hello, > > I currently use Mash to generate repositories from Koji tags and I'd like to > move to something that isn't abandoned. > Pungi is recommended by the Koji documentation, but I can't get it to produce > the same thing Mash does now. > I can get it to generate repo metadata for a given tag, but it doesn't copy > the RPMs themselves. > > The Pungi version that I'm using is pungi-4.1.38-1.el8.2.noarch and the > configuration: > > # RELEASE > release_name = "mytag8s-testing" > release_short = "mytag8s-testing" > release_version = "1.1.17" > > # GENERAL SETTINGS > variants_file = "variants.xml" > tree_arches = ["x86_64", "aarch64"] > tree_variants = ["os", "debug"] > > # CREATEREPO > createrepo_c = True > createrepo_database = True > createrepo_checksum = "sha256" > > # KOJI > koji_profile = "kojitest" > runroot_method = "koji" > runroot_tag = "mytag8s-testing" > > # PKGSET > sigkeys = ["..."] > pkgset_source = "koji" > pkgset_koji_tag = "mytag8s-testing" > > # GATHER > gather_method = "nodeps" > check_deps = False > > # OTHER SETTINGS > skip_phases = ['buildinstall', 'createiso', 'extra_files', 'extra_isos', > 'image_build', 'image_checksum', 'live_images', 'live_media', 'osbs', > 'ostree_installer', 'productimg', 'test', 'ostree'] > > with variants: > > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE variants PUBLIC "-//CentOS//DTD Variants info//EN" "variants.dtd"> > <variants> > <variant id="os" name="os" type="variant"> > <arches> > <arch>x86_64</arch> > <arch>aarch64</arch> > </arches> > </variant> > <variant id="debug" name="debug" type="variant"> > <arches> > <arch>x86_64</arch> > <arch>aarch64</arch> > </arches> > </variant> > </variants> > > I'm calling pungi-koji: # pungi-koji --config pungi.config --target-dir > "/staging/" --no-label > > This configuration creates the repositories, but doesn't populate them with > the packages. > > During the pkgset phase: > > 1) First it will get the name of the rpms from koji via koji tag - via koji > api (listTaggedRPMS) > > 2) Then it checks if these packages exists in the /mnt/koji path. If it > exists, a dictionary with that info is created. > The path is the default topdir in koji.conf - It can be changed, but there is > a validation to ensure that the directory exists. There is no option to use > the topurl and takes this info from koji on that stage. > > 3) Then it will create the repositories for each arch / variant. > > During the gather phase: > 1) It creates a rpm.json with a empty rpm list > 2) It doesn’t copy the rpms from /mnt/koji to the new repositories. > > > Could you please help me to understand if I'm doing something wrong or what I > can change in the configuration / variants file to make it work? > > Kind regards, > Marta Vila Fernandes > _______________________________________________ > buildsys mailing list -- > buildsys@lists.fedoraproject.org<mailto:buildsys@lists.fedoraproject.org> > To unsubscribe send an email to > buildsys-le...@lists.fedoraproject.org<mailto:buildsys-le...@lists.fedoraproject.org> > 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/buildsys@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- Tomas Kopecek <tkope...@redhat.com<mailto:tkope...@redhat.com>> RHEL Build Development, RedHat _______________________________________________ buildsys mailing list -- buildsys@lists.fedoraproject.org<mailto:buildsys@lists.fedoraproject.org> To unsubscribe send an email to buildsys-le...@lists.fedoraproject.org<mailto:buildsys-le...@lists.fedoraproject.org> 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/buildsys@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________ buildsys mailing list -- buildsys@lists.fedoraproject.org To unsubscribe send an email to buildsys-le...@lists.fedoraproject.org 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/buildsys@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
