devel June 2018

devel@lists.centos.org

35 participants
32 discussions

Authorization to use CentOS logo in GNOME Boxes
by Fabiano Fidêncio 19 Sep '18

19 Sep '18

People, Firstly, sorry for the cross-list post (centos-devel and centos-docs). I'd like to reach you in order to ask for a formal authorization to use CentOS logo on GNOME Boxes[0]. GNOME Boxes already shows a few other distro's logos as you can check here[1]. Would be possible to get the explicit confirmation that we could use CentOS logo as well? [0]: https://wiki.gnome.org/Apps/Boxes [1]: https://gitlab.gnome.org/GNOME/gnome-boxes/raw/master/README.logos Best Regards, -- Fabiano Fidêncio

4 5

SRPMS for AltArch (more specifically aarch64 kernel)
by Dominique Martinet 22 Aug '18

22 Aug '18

Hi folks, I've asked on IRC and have been pointed to this list. I can't seem to find this particular source rpm: kernel-aarch64-4.5.0-29.el7.src.rpm which is what is pointed by `rpm -qi kernel` on my system. Are these supposed to be available anywhere? Looking on google I only see one for an older release in someone's centos user/people page, but I can't seem to find these in any repo. The debuginfo are properly here but it's good to have sources as well when messing around with low level stuff :) Cheers and thanks for the hard work, -- Dominique Martinet

3 8

Experimental Vagrant images
by Laurentiu Pancescu 14 Jul '18

14 Jul '18

Hi there, I would like to change the Vagrant images to use a single partition (xfs) and swap to a file on that partition. This would simplify resizing the OS partition and also adjusting the size of the swap, compared to the current images. Would anyone be interested in testing the images? Please email me off-list for the links. I already had the changes done last month, tested them myself and on CICO but didn't get to wider testing or merging the PR for the monthly release... life is bit complicated lately. :) The only gotcha with swapping to a file is that you have to create the swap file with dd, as fallocate doesn't work properly on XFS. The experimental images come with a preconfigured swap, so this is only important if you want to change to another swap size. Thanks, Laurențiu

2 2

SIGs: Possibility to drop EOL content at 6.10 release time
by Anssi Johansson 02 Jul '18

02 Jul '18

RHEL 6.10 was released today and building CentOS 6.10 has just started. This would be an excellent time to remove any EOL software you may have floating around on mirror.centos.org. SIGs should explicitly state which content they want copied over from 6.9 to 6.10. I'd imagine that for example openstack-juno could be dropped because it went EOL in 2015-12-07 (so actually prior to CentOS 6.8's release..). Is there some other content that could be dropped? If SIGs want to transfer some of their packages from 6.9 to 6.10, please let hughesjr know. You can probably simply reply to this message to let people know of your decision. Content to be transferred over to 6.10 can be specified either by directory name, or by individual package names. There are also various centos-release-* packages in extras, http://mirror.centos.org/centos/6.9/extras/x86_64/Packages/ , perhaps some of those could be trimmed as well. You should also communicate to your users in advance that the EOL packages will disappear, and if necessary, instruct them to migrate to a newer supported version. Having instructions for that procedure published somewhere would be nice. The old content under 6.9, including any EOL content, will be archived to vault.centos.org, and that content will be available in the vault indefinitely. The 6.9 directory on mirror.centos.org will be emptied some time after 6.10 is released. For reference and inspiration, here are some directories from mirror.centos.org, including both up-to-date content and potentially EOL content. SIGs should review the list to make sure these directories can be copied over to 6.10 when that time comes. Making the decisions now would save a bit of time at 6.10 release time. cloud/x86_64/openstack-juno cloud/x86_64/openstack-juno/common sclo/x86_64/rh/devassist09 sclo/x86_64/rh/devtoolset-3 sclo/x86_64/rh/devtoolset-4 sclo/x86_64/rh/devtoolset-6 sclo/x86_64/rh/devtoolset-7 sclo/x86_64/rh/git19 sclo/x86_64/rh/httpd24 sclo/x86_64/rh/mariadb55 sclo/x86_64/rh/maven30 sclo/x86_64/rh/mongodb24 sclo/x86_64/rh/mysql55 sclo/x86_64/rh/nginx16 sclo/x86_64/rh/nodejs010 sclo/x86_64/rh/perl516 sclo/x86_64/rh/php54 sclo/x86_64/rh/php55 sclo/x86_64/rh/postgresql92 sclo/x86_64/rh/python27 sclo/x86_64/rh/python33 sclo/x86_64/rh/rh-git29 sclo/x86_64/rh/rh-java-common sclo/x86_64/rh/rh-mariadb100 sclo/x86_64/rh/rh-mariadb101 sclo/x86_64/rh/rh-mariadb102 sclo/x86_64/rh/rh-maven33 sclo/x86_64/rh/rh-mongodb26 sclo/x86_64/rh/rh-mongodb30upg sclo/x86_64/rh/rh-mongodb32 sclo/x86_64/rh/rh-mongodb34 sclo/x86_64/rh/rh-mysql56 sclo/x86_64/rh/rh-mysql57 sclo/x86_64/rh/rh-nginx18 sclo/x86_64/rh/rh-nginx110 sclo/x86_64/rh/rh-nodejs4 sclo/x86_64/rh/rh-nodejs6 sclo/x86_64/rh/rh-passenger40 sclo/x86_64/rh/rh-perl520 sclo/x86_64/rh/rh-perl524 sclo/x86_64/rh/rh-php56 sclo/x86_64/rh/rh-php70 sclo/x86_64/rh/rh-postgresql94 sclo/x86_64/rh/rh-postgresql95 sclo/x86_64/rh/rh-postgresql96 sclo/x86_64/rh/rh-python34 sclo/x86_64/rh/rh-python35 sclo/x86_64/rh/rh-python36 sclo/x86_64/rh/rh-redis32 sclo/x86_64/rh/rh-ror41 sclo/x86_64/rh/rh-ror42 sclo/x86_64/rh/rh-ror50 sclo/x86_64/rh/rh-ruby22 sclo/x86_64/rh/rh-ruby23 sclo/x86_64/rh/rh-ruby24 sclo/x86_64/rh/rh-scala210 sclo/x86_64/rh/rh-thermostat16 sclo/x86_64/rh/rh-varnish4 sclo/x86_64/rh/ror40 sclo/x86_64/rh/ruby193 sclo/x86_64/rh/ruby200 sclo/x86_64/rh/thermostat1 sclo/x86_64/rh/v8314 sclo/x86_64/sclo/sclo-git25 sclo/x86_64/sclo/sclo-git212 sclo/x86_64/sclo/sclo-httpd24more sclo/x86_64/sclo/sclo-php54 sclo/x86_64/sclo/sclo-php55 sclo/x86_64/sclo/sclo-php56 sclo/x86_64/sclo/sclo-php70 sclo/x86_64/sclo/sclo-python27 sclo/x86_64/sclo/sclo-python34 sclo/x86_64/sclo/sclo-python35 sclo/x86_64/sclo/sclo-ror42 sclo/x86_64/sclo/sclo-subversion19 storage/x86_64/gluster-3.6 storage/x86_64/gluster-3.7 storage/x86_64/gluster-3.8 storage/x86_64/gluster-3.9 storage/x86_64/gluster-3.10 storage/x86_64/gluster-3.12 storage/x86_64/gluster-3.13 storage/x86_64/gluster-4.0 storage/x86_64/gluster-4.1 virt/x86_64/xen-44 virt/x86_64/xen-46 virt/x86_64/xen-48

3 4

Do we know the reason why this below listed CVEs will not be fixed For elfutils-libelf, elfutils-libs and elfutils pakages ?
by Veetil, Vyshnav 30 Jun '18

30 Jun '18

Do we know the reason why this below listed CVEs will not be fixed For elfutils-libelf,elfutils-libs and elfutils pakages ? 1.CVE-2017-7607 2.CVE-2017-7608 3.CVE-2017-7609 4.CVE-2017-7610 5.CVE-2017-7611 6.CVE-2017-7612 7.CVE-2017-7613

4 5

Joining CentOS Storage SIG
by Saravanakumar Arumugam 29 Jun '18

29 Jun '18

Hi, I would like to be part of CentOS Storage SIG. I am from GlusterFS background, but I can contribute to package other solutions too. It will be great if we can add documentation about running CentOS based storage containers (like gluster / ceph containers). I can contribute here as well. Thanks, Saravana

2 2

[ceph storage sig] Possible Ceph Mimic package issue?
by Tobias Urdin 28 Jun '18

28 Jun '18

Hello, Sorry for starting a new thread, I accidentally wiped all email in my CentOS folder... Trying to install the Mimic packages from the test mirror here: http://cbs.centos.org/repos/storage7-ceph-mimic-candidate/x86_64/os/ You can see the commit where its tested here https://review.openstack.org/#/c/571990/ (ignore the ceph-luminous-sig part, I just override the repo URL and not the name as of now). Puppet (err): Execution of '/bin/yum -d 0 -e 0 -y install python-rbd' returned 1: Error: Package: lttng-ust-2.10.0-1.el7.x86_64 (ceph-luminous-sig) Requires: liburcu-bp.so.6()(64bit) Error: Package: lttng-ust-2.10.0-1.el7.x86_64 (ceph-luminous-sig) Requires: liburcu-cds.so.6()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest

2 4

CentOS 7.4 installation getting failed because of nss password prompt during installation.
by Veetil, Vyshnav 26 Jun '18

26 Jun '18

Hi, We have been observing that after migration to CentOS 7.4 the installation fails due to password being prompted for the execution of below command as part of the install script. <custom_location>certutil -N -d <custom location> -f <custom location>/nsspassword The install script contains the above command to create the NSSDB at the install time. Ideally, this command should never prompt for a password when it is already provided as part of '-f' argument but seeing this issue after migration to centOS 7.4. Also frequency of the issue is intermittent. Can anyone please help us to find the cause of this issue? Thanks and regards, Vyshnav

1 0

Removing old centos-release-<sig-project><version> from CentOS Extras?
by Niels de Vos 25 Jun '18

25 Jun '18

Hi, How are other SIGs handling the removal of repositories from the mirrors? There are centos-release-<sig-project> packages around that have YUM .repo files pointing to the now non-existing repos. Some (all?) of these centos-release-<sig-project> packages are still available in CentOS Extras. From #gluster: 21:25 < mallorn1> Anyone know why the 3.13 repository is gone from CentOS? http://mirror.centos.org/centos/7/storage/x86_64/ 21:25 <@glusterbot> Title: Index of /centos/7/storage/x86_64CentOS Mirror (at mirror.centos.org) 21:26 < mallorn1> Installed the centos-release-gluster313.noarch package that CentOS has, but then you can't install gluster because the target doesn't exist. At the moment I am tempted to create a centos-release-gluster-DONTUSE package that replaces centos-release-gluster313 and other unmaintained versions (suggestions for an alternative to DONTUSE welcome!). I do not want to force users to upgrade to a newer Gluster version without manual intervention. Some versions are/may not be compatible between client/server, or require some additional steps depending on the features that are used. Thanks, Niels

3 4

Packages tagged for release not showing up on mirrors
by Sandro Bonazzola 22 Jun '18

22 Jun '18

Hi, cockpit-169-1.el7 <http://cbs.centos.org/koji/buildinfo?buildID=22966> has been tagged for release on Jun 19. I see it published for x86_64: http://mirror.centos.org/centos/7/virt/x86_64/ovirt-4.2/common/ It's still missing on ppc64le: http://mirror.centos.org/altarch/7/virt/ppc64le/ovirt-4.2/common/ and aarch64: http://mirror.centos.org/altarch/7/virt/aarch64/ovirt-4.2/common/ Seems to be recurring issue not only in virt sig: https://bugs.centos.org/view.php?id=14226 https://bugs.centos.org/view.php?id=13633 https://bugs.centos.org/view.php?id=13283 https://bugs.centos.org/view.php?id=14782 Can we prioritize investigation on root cause and a fix for this? Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel June 2018