Re: [HEADS UP] gcc/gcc-c++ removal from buildroot and more

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

 



Hi,

On Tue, 2018-07-10 at 12:14 +0200, Vít Ondruch wrote:
> One question though. I see that this works in Koji, but trying to
> test this locally it does not work.
> 1) $ mock -r fedora-rawhide-x86_64 rubygem-abrt-0.3.0-3.fc29.src.rpm
> --enablerepo=local
> This still installs gcc.
> 2) $ mock -r fedora-rawhide-x86_64 rubygem-abrt-0.3.0-3.fc29.src.rpm
> --disablerepo=* --enablerepo=local
> This fails:
> ~~~
> Warning: Module or Group 'buildsys-build' does not exist.
> Error: Nothing to do.
> ~~~
> Trying to get the latest comps from local repository:
> ~~~
> https://kojipkgs.fedoraproject.org/repos/rawhide/latest/x86_64/repoda
> ta/db824c6dd6664943bcec0a8fcd3bda7fc855e5a787623c0da6d49deb79438fc7-
> comps.xml
> ~~~
> This has "build" group which references gcc/gcc-c++ and does not
> reference any buildsys-build group. So where is this file coming
> from? Why does it differ from regular Fedora repos?

The groups in Koji are defined differently from the groups in the
Fedora repos.

In the repos, you can find them defined in the comps.xml file, for
example:

http://dl.fedoraproject.org/pub/fedora/linux/releases/28/Everything/x86
_64/os/repodata/b140b2b55e06b7ba6c765d27dd9dbae905745e788a97a390be8b829
80b8c282e-comps-Everything.x86_64.xml

This contains a `buildsys-build` group, which mock installs when
creating a chroot.

In Koji, the groups can be seen with the command:

$ koji list-groups f29-build
[… snip …]
build  [f29]
  bash: None, mandatory  [f29]
  bzip2: None, mandatory  [f29]
  coreutils: None, mandatory  [f29]
  cpio: None, mandatory  [f29]
  diffutils: None, mandatory  [f29]
  fedora-release: None, mandatory  [f29]
  findutils: None, mandatory  [f29]
  gawk: None, mandatory  [f29]
  grep: None, mandatory  [f29]
  gzip: None, mandatory  [f29]
  info: None, mandatory  [f29]
  make: None, mandatory  [f29]
  patch: None, mandatory  [f29]
  redhat-rpm-config: None, mandatory  [f29]
  rpm-build: None, mandatory  [f29]
  sed: None, mandatory  [f29]
  shadow-utils: None, mandatory  [f29]
  tar: None, mandatory  [f29]
  unzip: None, mandatory  [f29]
  util-linux: None, mandatory  [f29]
  which: None, mandatory  [f29]
  xz: None, mandatory  [f29]
[… snip …]
srpm-build  [f29]
  bash: None, mandatory  [f29]
  fedora-release: None, mandatory  [f29]
  fedpkg-minimal: None, mandatory  [f29]
  gnupg2: None, mandatory  [f29]
  redhat-rpm-config: None, mandatory  [f29]
  rpm-build: None, mandatory  [f29]
  shadow-utils: None, mandatory  [f29]

The `srpm-build` group is what gets installed in the chroot to build
the SRPM (see the buildSRPMFromSCM subtask in any build task) and the
`build` group is what gets installed when building binary RPMs (see the
buildArch subtasks in any build task).

I do not know **why** we have this difference between Koji and the main
repos, I just know that we do have it.

This change needs to be reflected in Comps, so that Mock installs the
same thing in its buildroots as Koji.


-- 
Mathieu
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/TB4YLBIHDCNORB4MHSAUVT2HXXN4MNAQ/




[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