[scl.org] CentOS SCLo SIG sync-up meeting (2016-05-17)
The meeting will be at 13:00 UTC (9:00 EST, 15:00 Brno) in #centos-devel on Freenode. Agenda: * setting up Jenkins for Github PRs * anything else? Honza ___ 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)
On 16/05/16 23:17, Honza Horak wrote: > The meeting will be at 13:00 UTC (9:00 EST, 15:00 Brno) in #centos-devel > on Freenode. > > Agenda: > * setting up Jenkins for Github PRs > * anything else? * add vagrant-openstack-provider plugin to sclo-vagrant1 for use with the CentOS CI OpenStack instance (I've worked on this at https://copr.fedorainfracloud.org/coprs/domcleal/sclo-vagrant1-openstack/) -- 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)
Hi, what about automating updates of php scls? Also, adding some of the packages available in php5x-more to the official php scls, like the mcrypt and imap modules for example? Regards, Daniel -Ursprüngliche Nachricht- Von: sclorg-boun...@redhat.com [mailto:sclorg-boun...@redhat.com] Im Auftrag von Dominic Cleal Gesendet: Dienstag, 17. Mai 2016 10:47 An: The CentOS developers mailing list. ; sclorg@redhat.com Betreff: Re: [scl.org] [CentOS-devel] CentOS SCLo SIG sync-up meeting (2016-05-17) On 16/05/16 23:17, Honza Horak wrote: > The meeting will be at 13:00 UTC (9:00 EST, 15:00 Brno) in > #centos-devel on Freenode. > > Agenda: > * setting up Jenkins for Github PRs > * anything else? * add vagrant-openstack-provider plugin to sclo-vagrant1 for use with the CentOS CI OpenStack instance (I've worked on this at https://copr.fedorainfracloud.org/coprs/domcleal/sclo-vagrant1-openstack/) -- Dominic Cleal domi...@cleal.org ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg smime.p7s Description: S/MIME cryptographic signature ___ 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)
> Also, adding some of the packages > available in php5x-more to the official php scls, like the mcrypt and > imap modules for example? I have started adding some in centos-sclo-sclo repository See: http://ftp-stud.fht-esslingen.de/pub/Mirrors/centos/7/sclo/x86_64/sclo/sclo-php56/ I was mostly waiting for user feedback before adding more. BTW - mcrypt => missing libmcrypt which is not in RHEL/CentOS for very good reason. See: http://blog.remirepo.net/post/2015/07/07/About-libmcrypt-and-php-mcrypt I think all serious project have dropped dep. on this extension (and often only keep it as a fallback when openssl not availalble) - imap => missing libc-client So all is about, what should we do for dependencies not in base repository (but in EPEL). 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] CentOS SCLo SIG sync-up meeting (2016-05-17)
On 05/17/2016 02:57 PM, Remi Collet wrote: Also, adding some of the packages available in php5x-more to the official php scls, like the mcrypt and imap modules for example? I have started adding some in centos-sclo-sclo repository See: http://ftp-stud.fht-esslingen.de/pub/Mirrors/centos/7/sclo/x86_64/sclo/sclo-php56/ I was mostly waiting for user feedback before adding more. BTW - mcrypt => missing libmcrypt which is not in RHEL/CentOS for very good reason. See: http://blog.remirepo.net/post/2015/07/07/About-libmcrypt-and-php-mcrypt I think all serious project have dropped dep. on this extension (and often only keep it as a fallback when openssl not availalble) - imap => missing libc-client So all is about, what should we do for dependencies not in base repository (but in EPEL). From my PoV it would be fine to use EPEL deps for packages in SCLo (especially those that do not have a counterpart in RHSCL), but I'm almost sure kbsingh and bstinson will be against -- am I right? Is it a rule to use only packages built in CBS as deps> Honza ___ 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)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/05/16 15:08, Honza Horak wrote: > On 05/17/2016 02:57 PM, Remi Collet wrote: >> >>> Also, adding some of the packages available in php5x-more to >>> the official php scls, like the mcrypt and imap modules for >>> example? >> >> I have started adding some in centos-sclo-sclo repository >> >> See: >> http://ftp-stud.fht-esslingen.de/pub/Mirrors/centos/7/sclo/x86_64/scl o/sclo-php56/ >> >> >> >> I was mostly waiting for user feedback before adding more. >> >> BTW >> >> - mcrypt => missing libmcrypt which is not in RHEL/CentOS for >> very good reason. >> >> See: >> http://blog.remirepo.net/post/2015/07/07/About-libmcrypt-and-php-mcry pt >> >> >> I think all serious project have dropped dep. on this extension (and >> often only keep it as a fallback when openssl not availalble) >> >> - imap => missing libc-client >> >> >> So all is about, what should we do for dependencies not in base >> repository (but in EPEL). > > From my PoV it would be fine to use EPEL deps for packages in SCLo > (especially those that do not have a counterpart in RHSCL), but > I'm almost sure kbsingh and bstinson will be against -- am I right? > Is it a rule to use only packages built in CBS as deps> > > Honza yeah, cant use deps from outside of cbs. you'd need to rebuild those deps from epel. - - KB - -- Karanbir Singh, Project Lead, The CentOS Project, London, UK Red Hat Ext. 8274455 | DID: 0044 207 009 4455 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJXOyddAAoJEI3Oi2Mx7xbtzVAH/R92UH3D5FHLpQUcLZO/nP4T 79o2UBwCLDTf4Aq2EYgUh+QB+VPi/SffJqSrlj5I/WUxGRZ3sB4ks22srR+JmjN4 RKile+awIOillcYOxcekJuW2TmfU+FDhPA2PTz7WcX03+44bjh+i5Lmn8K9aEUcj Ttu/h34rxGz9onjsrB1lkPUSoM925VPB3I18/Qdpbbb6YIet6Q7Dl0lKCOV4n/Dg 97Hl94BDf5qjBXnGhErvyV3iHzlPKnvxRsPClONuj8Oq/qQh8ZzgHV46s0XB30aJ jvIHdCaDSMKkH7Vca5FmOAZZPedTmj7NOVmJ0qWKS9qC730DoBSnV5m5I1cbtsU= =b9Na -END PGP SIGNATURE- ___ 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)
On 05/17/2016 04:14 PM, Karanbir Singh wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/05/16 15:08, Honza Horak wrote: On 05/17/2016 02:57 PM, Remi Collet wrote: I think all serious project have dropped dep. on this extension (and often only keep it as a fallback when openssl not availalble) - imap => missing libc-client So all is about, what should we do for dependencies not in base repository (but in EPEL). From my PoV it would be fine to use EPEL deps for packages in SCLo (especially those that do not have a counterpart in RHSCL), but I'm almost sure kbsingh and bstinson will be against -- am I right? Is it a rule to use only packages built in CBS as deps> Honza 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? Honza ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
[scl.org] sclo-vagrant1 1.8.1 builds
A new sclo-vagrant1-vagrant build appeared today,
sclo-vagrant1-vagrant-1.8.1-4.el7, but it doesn't seem to be working
well with plugins built with 1.7.4-3.el7 as the root Vagrant
installation path changed.
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.
This breaks builds of vagrant-libvirt which have scriptlets built using
%vagrant_plugin_register pointing to ../usr/share/vagrant, and new
builds of plugins (http://cbs.centos.org/koji/buildinfo?buildID=1)
are being built with plugin names in the same place, e.g.
usr/share/sclo-vagrant1-vagrant-openstack-provider/lib.
thrcka, it looks like your build, could you look at this please?
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?
Cheers,
--
Dominic Cleal
domi...@cleal.org
___
SCLorg mailing list
SCLorg@redhat.com
https://www.redhat.com/mailman/listinfo/sclorg
Re: [scl.org] sclo-vagrant1 1.8.1 builds
On 05/17/2016 05:21 PM, Dominic Cleal wrote:
A new sclo-vagrant1-vagrant build appeared today,
sclo-vagrant1-vagrant-1.8.1-4.el7, but it doesn't seem to be working
well with plugins built with 1.7.4-3.el7 as the root Vagrant
installation path changed.
Sorry for the inconvenience, this has to slip through my hands.
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
This breaks builds of vagrant-libvirt which have scriptlets built using
%vagrant_plugin_register pointing to ../usr/share/vagrant, and new
builds of plugins (http://cbs.centos.org/koji/buildinfo?buildID=1)
are being built with plugin names in the same place, e.g.
usr/share/sclo-vagrant1-vagrant-openstack-provider/lib.
thrcka, it looks like your build, could you look at this please?
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.
Cheers,
___
SCLorg mailing list
SCLorg@redhat.com
https://www.redhat.com/mailman/listinfo/sclorg
Re: [scl.org] sclo-vagrant1 1.8.1 builds
There is a test that has been running for every new build, but the test
itself keeps failing (never worked properly imho). You might want to
fix/rewrite it, so you can easily check status of every rebuild:
https://github.com/sclorg/sclo-ci-tests/tree/master/collections/sclo-vagrant1-sclo/vagrant-up
results are then in
https://ci.centos.org/view/SCLo/job/SCLo-sclo-vagrant1-sclo-C7-x86_64/
Honza
On 05/17/2016 06:27 PM, Tomas Hrcka wrote:
On 05/17/2016 05:21 PM, Dominic Cleal wrote:
A new sclo-vagrant1-vagrant build appeared today,
sclo-vagrant1-vagrant-1.8.1-4.el7, but it doesn't seem to be working
well with plugins built with 1.7.4-3.el7 as the root Vagrant
installation path changed.
Sorry for the inconvenience, this has to slip through my hands.
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
This breaks builds of vagrant-libvirt which have scriptlets built using
%vagrant_plugin_register pointing to ../usr/share/vagrant, and new
builds of plugins (http://cbs.centos.org/koji/buildinfo?buildID=1)
are being built with plugin names in the same place, e.g.
usr/share/sclo-vagrant1-vagrant-openstack-provider/lib.
thrcka, it looks like your build, could you look at this please?
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.
Cheers,
___
SCLorg mailing list
SCLorg@redhat.com
https://www.redhat.com/mailman/listinfo/sclorg
___
SCLorg mailing list
SCLorg@redhat.com
https://www.redhat.com/mailman/listinfo/sclorg
