fedora-modularity / hp Goto Github PK

View Code? Open in Web Editor NEW

8.0 8.0 5.0 242 KB

Host & Platform, the new Fedora base

License: MIT License

Perl 91.23% Makefile 8.77%

hp's People

Contributors

Stargazers

Watchers

Forkers

ignatenkobrain cgwalters jlebon alexxnica kryndex

hp's Issues

bluez?

I think it would make sense to include bluez into Platform... Though it has cups subpackage, but well.

Having bluetooth lib in Platform makes sense to me.

drop xmlrpc-c

upstream maintains 3 streams in parallel and I would like to have xmlrpc-c module with 3 streams while now it is locked by platform.

I tried to remove from toplevel-binary-packages.txt and it went away in runtime.

dnf module install platform fails

>> dnf module install platform
Error: No such module: platform

>> dnf module list platform
Loading repositories.
Last metadata expiration check: 2:23:57 ago on Mon 02 Oct 2017 07:35:52 AM UTC.
Name                      Stream                  Version                         Profiles                                   Installed                  Info                                                       
platform                  master                  20170927180525                  buildroot, srpm-buildroot                                             The base system and common, shared userland

add libtalloc and libtevent

Both are required by a couple of modules like samba, sssd and a couple more.

platform-master-20170818100407 does not define API

The latest platform module build (platform-master-20170818100407) has empty API section. This prevents from programmatic searching for available components among existing modules.

dnf from boltron branch

Could you please pull dnf from the boltron branch of dist-git? I would submit a PR but I am not sure how to do it.

rsyslog?

We have systemd-journald nowadays, why do we need rsyslog?

Filtering unneeded packages from platform

I reviewed platform-master-20170926130931 (module-c67f088e45c73dfa) binary packages and I think these 99 packages can be filtered:

bluez-cups
bluez-obexd
ceph
ceph-base
ceph-common
ceph-debugsource
ceph-fuse
ceph-mds
ceph-mgr
ceph-mon
ceph-osd
ceph-radosgw
ceph-resource-agents
ceph-selinux
ceph-test
cephfs-java
cmirror
cmirror-standalone
cockpit-docker
cockpit-integration-tests
cockpit-kubernetes
cockpit-machines
cockpit-ostree
cockpit-packagekit
cockpit-pcp
cockpit-sosreport
cockpit-storaged
cyrus-sasl-sql
dbus-x11
dmraid-events-logwatch
drpmsync
emacs
emacs-common
emacs-debugsource
emacs-filesystem
emacs-gettext
emacs-lucid
emacs-nox
emacs-terminal
fedora-repos
fedora-repos-rawhide
freetype-demos
glib2-fam
glibc-utils
gnutls-dane
hfsutils-x11
iptables-compat
kernel-rpm-macros
krb5-server
krb5-server-ldap
libblockdev-btrfs
libblockdev-btrfs-devel
libblockdev-plugins-all
libcephfs-devel
libcephfs2
libcephfs_jni-devel
libcephfs_jni1
libidn-java
libidn-javadoc
libpeas-gtk
libproxy-kde
libproxy-mozjs
libproxy-pacrunner
libproxy-webkitgtk4
libreport-gtk
libreport-gtk-devel
libselinux-ruby
libtool
libtool-debugsource
libverto-tevent
libverto-tevent-devel
ntsysv
openldap-servers
openssh-askpass
openssh-cavs
openssl-perl
perl-solv
policycoreutils-gui
policycoreutils-sandbox
python-ceph-compat
python-cephfs
python3-cephfs
python3-tkinter
qgpgme
qgpgme-devel
qt5
qt5-devel
qt5-rpm-macros
rbd-mirror
rpm-cron
setools-console-analyses
setools-gui
texinfo
texinfo-debugsource
texinfo-tex
usermode-gtk
vim-enhanced
vim-X11
xmlrpc-c-apps

And I also have these questions or plan for questionable packages:

All python deps will use platformpython.
cockpit-networkmanager: Do we want NetworkManager for network setup?
cockpit-subscriptions: Do we need subscription-manager in platform?
cmake-filesystem dependecy will be replaced by own directory.
emacs-filesystem dependency will be disabled by build condition.
gnutls-dane: Requires unbound. Will be removed and gnutls-dane-devel files
    subpackaged from gnutls-devel.
gnutls-utils: Needs libgnutls-dane.so.0. Either disable DANE support or remove from
    platform. Also requires libopts.so.25().
gobject-introspection-devel:
    Requires libtool in same cases. Disable the dependency by a build condition.
    Requires python-mako for /usr/bin/g-ir-doc-tool tool. I recommend
    subpacking /usr/bin/g-ir-doc-tool and filtering it out.
libblockdev-* plugins: Which one we really need?
libcurl: Needs libpsl.so.5(). Add it or disable by a build condition. libpsl
    has often updates similar to CA certificate list.
libpeas-devel:
    libpeas is required for microdnf only.
    libpeas-devel requires GTK etc for libpeas-gtk.
    Filter libpeas-devel?
    Or subpackage libpeas-gtk-devel?
libproxy-networkmanager: Requiers libnm.so.0() from NetworkManager.
    Do we need NetworkManager?
libreport-* plugins:
    Do we need some of them?
    They require satyr, libtar, mailx, newt.
libsemanage-devel: requires ustr. Do we support SELinux policy recompilation?
libtirpc-devel: Requires man-db, the dependency should be removed (bug #1496422)
lvm2:
    Requires device-mapper-persistent-data. Do we need thin provisioning?
    device-mapper-persistent-data needs boost.
    The package name is misleading.
lvm2-* plugins: Which one do we need?
policycoreutils-dbus: Reeds python3-slip-dbus (python3-slip-gtk needs pygtk2)
polkit: Needs libmozjs and polkit-pkla-compat. Is libmozjs ready?
python3-debug, python3-tools:
    Requires python3-tkinter that I filtered and will be removed by Python team.
    This must be disabled by a build condition.
selinux-policy-doc:
    Requires xdg-open.
    I recommend to disable the by a build condition. Platform won't have any
    web browser.
systemd-journal-remote:
    Requires firewalld-filesystem for a directory and libmicrohttpd.so.12().
    Do we need it? I'm for removing it.
    Doesn't systemd require libmicrohttpd.so? Where is systemd?
xmlrpc-c-devel:
    Requires nonexistent pkgconfig(xmlrpc_utilpp). Something has changed in
    pkgconfig generator (bug #1482842).

Currently, vim(-minimal) is in platform because sudo used to have a hard dependency on it. From sudo's dist-git commit 3e6b39b18504cd49db16af4725d5799ab177ab23 on it only recommends vim-minimal, so dropping the dependency on it is possible.

"man" is missing from platform

We have man pages but no "man" in platform; it should probably be there, it's definitely needed for the Server somewhere. "info" is already pulled in.

Other packages to place

certmonger, gssproxy, clevis, tang, luks, luksmeta, kerberos, etc.
There are tons of other packages than need to be reviewed for example the python stack. Does it belong to platform?

Crypto packages

I would like to have a clear specification for the crypto packages: openssl, gnutls, nettle, crypt, nss etc.

glib2

I think it makes sense to include such core library (also because upsteam is very careful about keeping ABI stable, didn't remember about API stability, probably they keep it as deprecated for multiple releases and then remove it)

btrfs-progs

Would be useful to have btrfs-progs in Platform, since it is prerequisite for btrfs (which is installed on my laptop).

Dependency issues with lvm2, libblockdev (-btrfs, -kbd, -mdraid)

I attempted to install the udisks2 module on the current modular image (docker.io/jamesantill/boltron-27), and get the following error:

Boltron-27-ae4d664f407d-0# dnf module install udisks2
Last metadata expiration check: 2:54:30 ago on Mon 16 Oct 2017 09:07:24 AM UTC.
Error: 
 Problem 1: package udisks2-lvm2-2.7.2-1.module_3035087f.x86_64 requires lvm2, but none of the providers can be installed
  - conflicting requests
  - nothing provides device-mapper-persistent-data >= 0.7.0-0.1.rc6 needed by lvm2-2.02.174-2.module_1d780a7b.x86_64
 Problem 2: package udisks2-2.7.2-1.module_3035087f.x86_64 requires libblockdev-mdraid >= 2.10, but none of the providers can be installed
  - conflicting requests
  - nothing provides libbytesize.so.1()(64bit) needed by libblockdev-mdraid-2.11-1.module_04d473e8.x86_64
 Problem 3: package udisks2-zram-2.7.2-1.module_3035087f.x86_64 requires libblockdev-kbd >= 2.10, but none of the providers can be installed
  - conflicting requests
  - nothing provides bcache-tools >= 1.0.8 needed by libblockdev-kbd-2.11-1.module_04d473e8.x86_64
 Problem 4: package udisks2-bcache-2.7.2-1.module_3035087f.x86_64 requires libblockdev-kbd >= 2.10, but none of the providers can be installed
  - conflicting requests
  - nothing provides bcache-tools >= 1.0.8 needed by libblockdev-kbd-2.11-1.module_04d473e8.x86_64
 Problem 5: package udisks2-btrfs-2.7.2-1.module_3035087f.x86_64 requires libblockdev-btrfs >= 2.10, but none of the providers can be installed
  - conflicting requests
  - nothing provides libbytesize.so.1()(64bit) needed by libblockdev-btrfs-2.11-1.module_04d473e8.x86_64
 Problem 6: package udisks2-lsm-2.7.2-1.module_3035087f.x86_64 requires udisks2(x86-64) = 2.7.2-1.module_3035087f, but none of the providers can be installed
  - package udisks2-2.7.2-1.module_3035087f.x86_64 requires libblockdev-mdraid >= 2.10, but none of the providers can be installed
  - conflicting requests
  - nothing provides libbytesize.so.1()(64bit) needed by libblockdev-mdraid-2.11-1.module_04d473e8.x86_64
 Problem 7: package udisks2-iscsi-2.7.2-1.module_3035087f.x86_64 requires udisks2(x86-64) = 2.7.2-1.module_3035087f, but none of the providers can be installed
  - package udisks2-2.7.2-1.module_3035087f.x86_64 requires libblockdev-mdraid >= 2.10, but none of the providers can be installed
  - conflicting requests
  - nothing provides libbytesize.so.1()(64bit) needed by libblockdev-mdraid-2.11-1.module_04d473e8.x86_64
Boltron-27-ae4d664f407d-1#

The lvm2 and libblockdev-* packages of the platform module seem to need these missing components (and possibly their dependencies):

device-mapper-persistent-data
libbytesize
bcache-tools

What container runtime would you like to pick?

A brief list of options:

runc -- a few requires, it's not easy to run containers
atomic -- requires python and has a lot of dependencies
cri-o -- work in progress
docker -- 'de facto' standard, fast release-cycle, complex software

DEBUG util.py:439:    - nothing provides cmake-filesystem(x86-64) needed by cmake-3.9.3-1.module_7c9e41dd.x86_64

This is because platform module does not deliver cmake-filesystem package. Please add it.

See cmake-bootstrap build macros for disabling unneeded feature, especially:

%_with_bootstrap 1

for building it without already having cmake in the build root.

platform:f27 is missing python3-rpm-generators package

python3-devel binary package run-requires python3-rpm-generators, but the package is not in the plaform:f27. This bug prevents from building Python 3 packages against platform:f27 and pytothon3:3.6. See https://koji.fedoraproject.org/koji/taskinfo?taskID=23095957.

Please add python3-rpm-generators package into the platform:f27 module.

fedora-modular.repo dnf config file should point to f27 repo

Currently, /etc/yum.repos.d/fedora-modular.repo from fedora-modular-repos.rpm refers to

baseurl=https://kojipkgs.fedoraproject.org/compose/latest-Fedora-Modular-rawhide/compose/Server/$basearch/os

It should point at the latest-Fedora-Modular-27 compose instead.

some packages from platform can't be installed

logs from my recent module build:

 # /usr/bin/dnf --installroot /var/lib/mock/module-autotools-master-20170822063906-PoolThread-twisted.internet.reactor-0/root/ --disableplugin=local --setopt=deltarpm=False install unzip tar cpio gawk xz sed findutils util-linux bash info gcc grep redhat-rpm-config fedora-modular-release diffutils make patch shadow-utils coreutils which rpm-build gzip gcc-c++ bzip2
Unable to detect release version (use '--releasever' to specify release version)
module-fe2a0d24e1b4e764                         123 MB/s | 920 kB     00:00    
Failed to synchronize cache for repo 'localrepo', disabling.
Last metadata expiration check: 0:00:00 ago on Tue 22 Aug 2017 08:42:49 AM CEST.
Error: 
 Problem 1: package gcc-7.1.1-7.module_6faa4f4e.1.x86_64 requires glibc-devel >= 2.2.90-12, but none of the providers can be installed
  - package glibc-devel-2.26-1.module_6faa4f4e.1.x86_64 requires glibc-headers = 2.26-1.module_6faa4f4e.1, but none of the providers can be installed
  - conflicting requests
  - nothing provides kernel-headers >= 2.2.1 needed by glibc-headers-2.26-1.module_6faa4f4e.1.x86_64
 Problem 2: package gcc-7.1.1-7.module_6faa4f4e.1.x86_64 requires glibc-devel >= 2.2.90-12, but none of the providers can be installed
  - package gcc-c++-7.1.1-7.module_6faa4f4e.1.x86_64 requires gcc = 7.1.1-7.module_6faa4f4e.1, but none of the providers can be installed
  - package glibc-devel-2.26-1.module_6faa4f4e.1.x86_64 requires glibc-headers = 2.26-1.module_6faa4f4e.1, but none of the providers can be installed
  - conflicting requests
  - nothing provides kernel-headers >= 2.2.1 needed by glibc-headers-2.26-1.module_6faa4f4e.1.x86_64