devel

devel@lists.centos.org

4 participants
4640 discussions

GlusterFS 6.0RC Test Days (27th, 28th Feb)
by Rich Bowen 28 Feb '19

28 Feb '19

Gluster users/developers, We are calling out our users, and developers to contribute in validating ‘glusterfs-6.0rc’ build in their usecase. Specially for the cases of upgrade, stability, and performance. Full details and participation information may be found on the Gluster-devel mailing list, here: https://lists.gluster.org/pipermail/gluster-devel/2019-February/055876.html -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

2 1

Need a knob to disable all spectre/meltdown fixes
by Priya, Nupur 26 Feb '19

26 Feb '19

Hi there, I would like to implement a command , to be able to disable all variants(or at least the ones causing performance impact). As per the RH article: https://access.redhat.com/articles/3311301, we would be able to only disable spectre variant 2 and 3(pti). I need an option to disable variant 1, 3a and 4 as well. Some of the recent articles suggest that options like no_spectre_v1, no_spectre_v2 and spec_store_bypass_disable parameters are available in latest versions of kernel(4.15 and above). https://www.zdnet.com/article/linux-kernel-gets-another-option-to-disable-s… https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html?h… Can this be made available in our Centos 7 kernels? Or is there any plan for RH to implement the same in any future release? Regards, Nupur

2 1

Centpkg and the converged git project
by Brian Stinson 22 Feb '19

22 Feb '19

Hi Folks, I've done a bit of work on centpkg, now that we have a testbed at git.stg.centos.org. The goal here is to allow centpkg and fedpkg (Fedora's site) to both understand the different formats. The test version of centpkg described below is the first step in that direction. Basically you can try this out by pulling a container image: `podman pull quay.io/bstinsonmhk/centpkg:develop` Why a container image? - The patches to make this happen involve invasive changes to rpkg, that are still in flight (basically, https://pagure.io/rpkg/pull-request/393) - I wanted to bake in the sources and configs to develop this a little faster as we find problems. What's included, and where to file bugs? - centpkg from: https://bitbucket.org/bstinsonmhk/centpkg/branch/develop - rpkg from: https://pagure.io/fork/bstinson/rpkg/tree/centpkg-inbound - fedpkg from: https://pagure.io/fedpkg/tree/master Here's how I run it for testing CentOS packages (substitute your centos user certificate and a path to RPMs to fit your workstation): `podman run --rm -it -v /home/bstinson/.centos.cert:/home/centpkg-user/.centos.cert:Z -v /home/bstinson/rpms:/home/centpkg-user/rpms:Z quay.io/bstinsonmhk/centpkg:develop` If you're a SIG member, you can push to a sig branch. For example, if I was a mamber of the atomic SIG I could do: # Clone the repo $ centpkg clone -b c7 a2ps # Download the sources from C7 $ centpkg sources # Change to a SIG branch $ git checkout -b c7-sig-atomic-cockpit-preview # Manual push is needed here until we work out a way to register the # new branches $ git push -u origin c7-sig-atomic-cockpit-preview # Upload sources to the SIG branch in the lookaside $ centpkg upload SOURCES/a2ps-4.14.tar.gz SOURCES/i18n-fonts-0.1.tar.gz # CBS does not yet build from SCM, so still need srpms $ centpkg scratch-build --srpm # Try out a fedora branch $ centpkg switch-branch f28 $ centpkg clean # From a Fedora branch this should use your Fedora creds $ centpkg scratch-build # this should work with Fedora's ko What I need help with: - Review the open PRs to rpkg as they come in - Help me find more places where we need to use the new 'Layout' objects (that is where rpkg has paths hard-coded) - Test Fedora workflows, and other commands with centpkg - Help add new commands - to request SIG branches - to translate from one layout to another (ex. bringing a Fedora branch into a CentOS SIG branch) Happy building! --Brian

2 1

git.stg.centos.org upgraded to pagure 5.3 (beta) and new feature like mqtt notifications
by Fabian Arrotin 22 Feb '19

22 Feb '19

Hi, In October 2018, we (pre)announced that we were working on a consolidated pagure infra for git.centos.org and src.fedoraproject.org. (https://lists.centos.org/pipermail/centos-devel/2018-October/016997.html) We asked feedback from community and one of the remarks we had was about being able to follow commits for all /rpms/* While there were requests to have that available through pagure API (for people already using the gitblit RPC feature of current https://git.centos.org instance), another idea was to simply send that to a message broker, so that people can just subscribe to that broker on a particular topic and consume the message payloads posted there. As such MQTT support landed in pagure, we decided to upgrade (both instances) and we have (only at the CentOS side) implemented MQTT notifications to a "public" broker Example : This dummy commit (specific branch) : https://git.stg.centos.org/rpms/bacula/c/61cd3575ba64b5f7afbf16eeb5c8dea729… (automatically replicated to https://src.stg.fedoraproject.org/rpms/bacula/c/61cd3575ba64b5f7afbf16eeb5c…) posted the following json message on our MQTT staging broker : git.stg.centos.org/git.receive {"forced": false, "agent": "arrfab", "repo": {"custom_keys": [], "name": "bacula", "parent": null, "date_modified": "1539692831", "access_users": {"owner": ["centosrcm"], "admin": [], "ticket": [], "commit": []}, "namespace": "rpms", "priorities": {}, "close_status": [], "access_groups": {"admin": [], "commit": [], "ticket": []}, "milestones": {}, "user": {"fullname": "CentOS Sources", "name": "centosrcm"}, "date_created": "1539692831", "fullname": "rpms/bacula", "url_path": "rpms/bacula", "id": 6, "tags": [], "description": " Cross platform network backup for Linux, Unix, Mac and Windows"}, "end_commit": "61cd3575ba64b5f7afbf16eeb5c8dea7293b1241", "branch": "c7-sig-altarch-test", "authors": [{"fullname": "Fabian Arrotin", "name": "arrfab"}], "total_commits": 1, "start_commit": "61cd3575ba64b5f7afbf16eeb5c8dea7293b1241"} The first part is just the topic, while the message payload is the json How can you subscribe to that MQTT broker (if you want to automate some workflow) ? The only requirement is to trust our ACO (https://accounts.centos.org) CA cert and also to have your TLS cert from ACO All those steps are done automatically through centos-cert (from centos-packager, see https://wiki.centos.org/HowTos/CentosPackager) From that point, you can use your MQTT client of choice (mosquitto_sub from mosquitto pkg, or python-paho-mqtt for python client, etc) and point to mqtt.stg.centos.org:8883 Simple example with mosquitto_sub : mosquitto_sub --cafile ~/.centos-server-ca.cert --cert ~/.centos.cert --key ~/.centos.cert -h mqtt.stg.centos.org -p 8883 -t git.stg.centos.org/# -v Hope that it helps people willing to get automatic notifications in "real-time" when repositories are created or that there are new commits landing there. Worth noting that it's still only in staging, but once we have a green light, we should migrate git.centos.org to pagure with the same features set as the one deployed on staging. -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

2 2

[CentOS-docs] Authorization to use CentOS logo in GNOME Boxes
by Ladar Levison 21 Feb '19

21 Feb '19

> Who will prepare the logo? I do not know, we could use a volunteer. > I had to track down SVG logo files for the Robox website. Not sure, is this what you need? https://roboxes.org/res/centos.svg

5 18

FOSSAsia passes available
by Rich Bowen 18 Feb '19

18 Feb '19

As I mentioned last week, CentOS will be sponsoring FOSSAsia next month - http://2019.fossasia.org/ - and I have three passes for the event, available for the low, low price of one hour of "booth duty" at the CentOS table. The Expo at FOSSAsia is open: Thursday: 12:00 - 18:00 Friday and Saturday: 10:00 - 18:00 Sunday: 10:00 - 16:00 At the moment, I expect to be working all of those hours, and could really use someone for at least one hour each day, so that I can step away occasionally. Please contact me off-list if you're interested. First come, first served. Thanks! -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

freeIPA from CR repo - rpm conflicts
by lejeczek 18 Feb '19

18 Feb '19

hi guys do you see the same by any chance? .... --> Processing Dependency: ipa-server-common = 4.6.4-10.el7.centos.2 for package: python2-ipaserver-4.6.4-10.el7.centos.2.noarch --> Processing Dependency: ipa-common = 4.6.4-10.el7.centos.2 for package: python2-ipaserver-4.6.4-10.el7.centos.2.noarch --> Finished Dependency Resolution Error: Package: python2-ipaserver-4.6.4-10.el7.centos.2.noarch (updates) Requires: ipa-server-common = 4.6.4-10.el7.centos.2 Installed: ipa-server-common-4.6.4-10.el7.centos.noarch (@cr) ipa-server-common = 4.6.4-10.el7.centos Error: Package: ipa-server-4.6.4-10.el7.centos.x86_64 (@cr) Requires: python2-ipaserver = 4.6.4-10.el7.centos Removing: python2-ipaserver-4.6.4-10.el7.centos.noarch (@cr) python2-ipaserver = 4.6.4-10.el7.centos Updated By: python2-ipaserver-4.6.4-10.el7.centos.2.noarch (updates) python2-ipaserver = 4.6.4-10.el7.centos.2 Error: Package: python2-ipaclient-4.6.4-10.el7.centos.2.noarch (updates) Requires: ipa-common = 4.6.4-10.el7.centos.2 Installed: ipa-common-4.6.4-10.el7.centos.noarch (@cr) ipa-common = 4.6.4-10.el7.centos Error: Package: python2-ipaclient-4.6.4-10.el7.centos.2.noarch (updates) Requires: ipa-client-common = 4.6.4-10.el7.centos.2 Installed: ipa-client-common-4.6.4-10.el7.centos.noarch (@cr) ipa-client-common = 4.6.4-10.el7.centos Error: Package: python2-ipalib-4.6.4-10.el7.centos.2.noarch (updates) Requires: ipa-common = 4.6.4-10.el7.centos.2 Installed: ipa-common-4.6.4-10.el7.centos.noarch (@cr) ipa-common = 4.6.4-10.el7.centos Error: Package: ipa-client-4.6.4-10.el7.centos.x86_64 (@cr) Requires: python2-ipaclient = 4.6.4-10.el7.centos Removing: python2-ipaclient-4.6.4-10.el7.centos.noarch (@cr) python2-ipaclient = 4.6.4-10.el7.centos Updated By: python2-ipaclient-4.6.4-10.el7.centos.2.noarch (updates) python2-ipaclient = 4.6.4-10.el7.centos.2 Error: Package: python2-ipaserver-4.6.4-10.el7.centos.2.noarch (updates) Requires: ipa-common = 4.6.4-10.el7.centos.2 Installed: ipa-common-4.6.4-10.el7.centos.noarch (@cr) ipa-common = 4.6.4-10.el7.centos You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest

2 4

Re: [CentOS-devel] Please do not push dpdk-18.11 to Extras!
by Sandro Bonazzola 14 Feb '19

14 Feb '19

Il giorno gio 14 feb 2019 alle ore 10:41 Alan Pevec <apevec(a)redhat.com> ha scritto: > Hi Johnny, > > On Wed, Feb 6, 2019, 13:05 Alan Pevec <apevec(a)redhat.com wrote: > > please hold on pushing dpdk-18.11 rebase[1] to Extras, it's breaking > > currently released openvswitch builds in Cloud and Virt SIG. > > We're figuring out workarounds and will update this thread. > > > http://mirror.centos.org/centos/7/extras/x86_64/Packages/dpdk-18.11-2.el7_6… > was still pushed yesterday and broke openstack and ovirt CI and users, > we would appreciate a notice at least since Extras is not going through CR. > > We are trying to mitigate this now, options are to rebuild w/o DPDK > (quick) or to rebundle DPDK 17.11 (bad, takes more time and diverges > from Fedora packaging) > > For the former, we are checking where DPDK with OVS is actually used. > Sandro, is DPDK used in oVirt? > Adding oVirt network team for answering this question. > > Cheers, > Alan > -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

Facing issue while Contributing code to existing Git repos
by Amarjeet Singh 13 Feb '19

13 Feb '19

Hi Team, I am trying to contribute to the existing Git repos. I have followed the process from the below link https://wiki.centos.org/Sources [user@host]$ git clone https://git.centos.org/git/rpms/kernel.git cd kernel# let's work on the centos7 kernel[user@host]$ git checkout c7[user@host]$ ~/bin/get_sources.sh# switch to the local tree to edit[user@host]$ git checkout -b my-kernel# make edits to SPEC file, etc [user@host]$ git commit -m 'my local change' -a This command *~/bin/get_sources.sh has downloaded the xxxx.tar.gz file in the SOURCES directory.* *Now I have extracted the tar file and did the changes. * At this stage If I commit then I have to include all the extracted files. If I run git format-patch c7 it generate the file which includes all the files. Please guide me how to contribute to the existing GIT REPOS. Thanks and Regards, Amarjeet Singh

3 4

Re: [CentOS-devel] weird RPM dependency error; '/bin/sh' needed, but is provided
by Brian Reichert 12 Feb '19

12 Feb '19

(This is a re-send; my first attempt was a day ago, but I did not see this come through. I may not have been subscribed to this list at the time, which may have impacted things. So, I do apologize if you eventually get a dup.) First off, I have to admit that I'm uncertain if this is the appropriate forum; I'd be happy for suggestions about where else to look. I'm doing this work on a stock install of CentOS-7-x86_64-Minimal-1810.iso, with no updates. I'm trying to create an RPM database from a custom set of RPMs. One RPM ('openldap-ltb' from the LDAP Tool Box project (ltb-project.org) has a dependency on '/bin/sh'. The bash RPM is demonstratedly present, yet the the 'rpm' utility thinks this dependency is not met. I'm open to any advice as to how to progress. It pretty easy to demonstrate what's going wrong, rather than trying to describe it. Straightforward to reproduce: Here, I collect the misc bits from the net: $ wget --quiet http://mirrors.mit.edu/centos/7/isos/x86_64/CentOS-7-x86_64-Minimal-1810.iso $ wget --quiet http://mirrors.mit.edu/centos/7/os/x86_64/Packages/libtool-ltdl-2.4.2-22.el… $ wget --quiet https://ltb-project.org/archives/berkeleydb-ltb-4.6.21.NC-4.el7.patch4.x86_… $ wget --quiet https://ltb-project.org/archives/openldap-ltb-2.4.47-1.el7.x86_64.rpm Now, I try to make an RPM database of these packages. The last step fails with an unmet dependency: $ sudo mount ~/CentOS-7-x86_64-Minimal-1810.iso -r -t iso9660 -o loop /mnt $ mkdir -p ~/local_rpm_db $ rpm --initdb --dbpath ~/local_rpm_db $ rpm --justdb --ignoresize --dbpath ~/local_rpm_db -Uvh /mnt/Packages/*.rpm *.rpm warning: /mnt/cdrom/Packages/acl-2.2.51-14.el7.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY warning: berkeleydb-ltb-4.6.21.NC-4.el7.patch4.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 6d45bfc5: NOKEY error: Failed dependencies: /bin/sh is needed by openldap-ltb-2.4.47-1.el7.x86_64 Which is weird, as the 'bash' RPM is clearly part of the set, and 'provides' the needed feature: $ rpm -q -provides -p /mnt/Packages/bash-4.2.46-31.el7.x86_64.rpm | egrep 'sh$' /bin/bash /bin/sh Further, it's not among the list of files in the payload of the RPM: $ rpm -q -l -p /mnt/Packages/bash-4.2.46-31.el7.x86_64.rpm | egrep 'sh$' /usr/bin/bash /usr/bin/sh These tactics did work with the related bits for CentOS 6. Here are some details of my environment; I'm happy to provide more, if anyone has any questions: $ cat /etc/redhat-release CentOS Linux release 7.6.1810 (Core) $ rpm -qf /usr/bin/rpm rpm-4.11.3-35.el7.x86_64 -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel