Re: [scl.org] sclo-vagrant1 1.8.1 builds
On 17/05/16 17:27, Tomas Hrcka wrote:
> On 05/17/2016 05:21 PM, Dominic Cleal wrote:
>> It looks like %{vagrant_dir} has expanded differently, causing the root
>> of the Vagrant installation to be at
>> /opt/rh/sclo-vagrant1/root/usr/share/sclo-vagrant1-vagrant/ rather than
>> /opt/rh/sclo-vagrant1/root/usr/share/vagrant/.
>>
>> 1.7.4-3.el7: http://cbs.centos.org/koji/rpminfo?rpmID=23881
>> 1.8.1-4.el7: http://cbs.centos.org/koji/rpminfo?rpmID=56779
>>
>> The file /usr/lib/rpm/macros.d/macros.vagrant.sclo-vagrant1 in the older
>> build contains "%vagrant_dir %{_datadir}/vagrant", but the newer build
>> uses %{name} which expands to the SCLed name.
>
> I have fixed it back to pkg_name
Thanks, 1.8.1-5 seems to fix both of these issue. There remains another
new one it seems - if you rebuild a plugin against -5, the registration
scriptlet runs "/opt/rh/sclo-vagrant1/root/usr/bin/ruby -e".
%vagrant_plugin_register now uses %{_bindir}/ruby, but this used to be
plain "ruby" - the scl enable should put it in the PATH anyway, so I
don't think this is needed. It was changed at
https://github.com/sclorg-distgit/vagrant/commit/e448388e0cc88a76d9923d86df3e1615a666eeff#diff-0cc501359f9ff39115559ff49a4f0d47L36.
>> Separately I've requested that sclo-vagrant1 be added to the sclo
>> testing repo via https://bugs.centos.org/view.php?id=10869 so I could
>> test the OpenStack package, but we should use the testing repo and
>> process once it's available to check updates work.
>>
>> Also one final point, I couldn't find the source for the update in
>> https://github.com/sclorg-distgit/vagrant/tree/sig-sclo7-sclo-vagrant1-sclo
>> - could the changes be pushed there?
> Sorry I have opened pull request instead of pushing there. Changes are
> now pushed.
Ah OK, probably best to push if it's already built. I'll monitor the PRs
in that repo in future to help with reviewing. Hopefully the testing
repo will help as well so these changes aren't released immediately.
--
Dominic Cleal
domi...@cleal.org
___
SCLorg mailing list
SCLorg@redhat.com
https://www.redhat.com/mailman/listinfo/sclorg
Re: [scl.org] [CentOS-devel] CentOS SCLo SIG sync-up meeting (2016-05-17)
Le 17/05/2016 à 16:34, Honza Horak a écrit : >> yeah, cant use deps from outside of cbs. you'd need to rebuild those >> deps from epel. > > Do you have some estimation of how many packages would have to be needed? Few examples: php-imap => libc-client php-mcrypt => libmcrypt php-tidy => libtidy php-mssql=> freetds php-interbase=> firebird (and probably others) php-pecl-mongodb => libbson + libmongoc php-pecl-amqp=> librabbitmq php-pecl-libsodium => libsodium php-pecl-zmq => zeromq ... Remi -- rcol...@redhat.com | Senior Software Engineer / BaseOS / WebStack team GPG Key: 0x29F16A18 Fingerprint: 5A0E 6F54 D94D 5732 69EE E3FF 614A 6905 29F1 6A18 ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
Re: [scl.org] [CentOS-devel] 'vagrant up' not working after yum update
On 18/05/16 15:52, Dharmit Shah wrote: > Hello all, > > I'm seeing this behaviour since I did `yum update` today on one of my > CentOS 7 boxes in that, `vagrant up` for libvirt provider throws the error: > > "The provider 'libvirt' could not be found, but was requested to > back the machine 'default'. Please use a provider that exists." > > Details of the issue can be found on [1]. I observed the issue when I > was doing testing for Atomic Developer Bundle (ADB) [2]. Could you try this newer build of sclo-vagrant1-vagrant (the -5 release)? http://cbs.centos.org/koji/buildinfo?buildID=3 It's been tagged for release already so I expect it'll appear on the mirrors within a few days. (see also https://www.redhat.com/archives/sclorg/2016-May/msg00014.html where this was discussed and hopefully fixed) > Besides that, earlier, one needed to install only two packages - > centos-release-scl and sclo-vagrant1 - to use Vagrant. But now it seems > to have changed and we need to install sclo-vagrant1-vagrant-libvirt as > well as few other packages/dependencies to make it work. I modified my > Ansible playbook [3] which reflects the set of packages I had to add. This appears to have been changed in http://cbs.centos.org/koji/buildinfo?buildID=10807, but I don't see why. The changelog is pretty unhelpful, but comparing the specs shows that %install_scl's been flipped to zero which isn't common in SCL meta RPMs. > What I'm here to understand is that, am I doing something obviously > wrong here to make things work or, did I miss some notification on this > list that had details about the changes? Or is this some kind of > unexpected behaviour? Unexpected to me, I think the RPMs should have been put to the testing repo before being released. -- Dominic Cleal domi...@cleal.org ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
[scl.org] Building packages depending on SCL
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I've been building RPMs for a while, however SCL is a bit "new" to me. I am trying to build an apache module for SCL apache version (httpd24-httpd) . I have located documentation on how to proceed with building SCL package from scratch, however I didn't come across any information on building atop of existing packages, like in my case. Any pointers (URLs etc.) will be deeply appreciated. - -- Sr System and DevOps Engineer SoM IRT -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJXPJZOAAoJEHd9jKvw5f8b/FsP/jtopReS0MsW5CvZOEQUxczx 3ku2FQZGdHr7cIZUIXZSkLlqC3AT/oL6Ku01aN8AqiOJrAW+c2bR9+eoL+Tpj9+1 c5n24K/u5Bg0OsdT/1RGPgSicyiWzErVvuLLL8CZED6kMYJ8gxxA1+tKYU7GLHZj taY9E37gI6jyhPFHujqkP7PeqGawIq5o3rYHvpRh+nfioUFlHX6fK6ZNuhjYR2OG panqbaM2EPySXmRgJX8Fho2bkL5tE1Z1yQNa+3RvkienowU32+1f65613cYfwI8T SZ+INvCdu8mVyBaT5L2TXKeAlEt8isl+sUpWKX5nrQdvVR4dQa7m7wYHO6C1KT8f eitzbUQ/e64spUIbnzZVgwx8zXjmhBWh5vCnuCfDNFhyoufL2mvteMQRsMs7QFNq RL5z4iKGgL6mResKfrjVq7mVAjDS8rByqRLl77BBg0X0GoXLm+qsmhQSzheBS1ou GR2tAcVaj92eQWu9MYC9oW+2Fs/ynvaNyP6Z9+tjinRcPBhc+PUQlyH8OStx32of hrNrx/j9QP+Oz7eFWgr9qbQwYqc2SCPWcPhpC73U6movuhI/vCrc/sv0/43Mryw4 VXbHPAs45jnZKJxBkqlgVcUY2Hh+6Smr9LIUbexegOnwNmAYyLu+yMHUtWV7E52j FrsJgXv/N0q+ovQIDWOI =kI6T -END PGP SIGNATURE- ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
Re: [scl.org] Building packages depending on SCL
Le 18/05/2016 à 18:20, Dmitry Makovey a écrit : > > Hi, > > I've been building RPMs for a while, however SCL is a bit "new" to me. > I am trying to build an apache module for SCL apache version > (httpd24-httpd) . I have located documentation on how to proceed with > building SCL package from scratch, however I didn't come across any > information on building atop of existing packages, like in my case. > Any pointers (URLs etc.) will be deeply appreciated. In centos-sclo repository you already have 2 apache modules, you can probably have a look at (diffing with base package in Fedora/EPEL) https://github.com/sclorg-distgit/mod_auth_mellon/tree/sig-sclo7-sclo-httpd24more-sclo https://github.com/sclorg-distgit/mod_ruid2/tree/sig-sclo7-sclo-httpd24more-sclo Hope this helps... Remi > > > ___ > SCLorg mailing list > SCLorg@redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > -- rcol...@redhat.com | Senior Software Engineer / BaseOS / WebStack team GPG Key: 0x29F16A18 Fingerprint: 5A0E 6F54 D94D 5732 69EE E3FF 614A 6905 29F1 6A18 ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
