devel

devel@lists.centos.org

1 participants
4650 discussions

how to use livecd-creator to create my own livecd iso which is same as offical release iso？
by wqlxx007＠gmail.com 10 Apr '17

10 Apr '17

Hi Fabian >Just to be sure : are you using livecd-tools-21.4-2.el7.x86_64 (and >corresponding python-imgcreate) packages that are on >http://mirror.centos.org/centos/7/extras/x86_64/Packages/ and so on a >CentOS 7 node to build your livecd ? I use CentOS-7-x86_64-Minimal-1511.iso to install the system on my pc. I have check the version of livecd-creator is 21.4, and release number is 2.el7 >Also, that ks file isn't updated as only LiveGnome/LiveKDE are >maintained so maybe compare with the other ks files located on >https://git.centos.org/tree/sig-core!livemedia.git/4c99f5ea4fa3399f533cd223… >(for example that old ks still points to outdated and non existing >repositories) As you say, the centos-7-livecd.cfg is out of date. I try the centos-7-live-gnome.cfg, the command is: livecd-creator -v --config=centos-7-live-gnome.cfg --fslabel=centos-7-live-gnome --cache=/var/cache/live but finally the ISO which i build with centos-7-live-gnome.cfg is also the same structure like: centos-7-live-gnome.iso |+++EFI |+++BOOT |+++fonts |+++BOOTX64.EFI |+++grub.cfg |+++grubx64.cfg |+++isolinux |+++boot.cat |+++initrd0.img |+++vmlinuz0 .... |+++LiveOS |+++osmin.img |+++squashfs.img I guess the maybe the different of config file for livecd-tools cause the different ISO. Would you please provide the Kickstart config file which used to build CentOS-7-x86_64-Minimal-1511.iso or other version of offical distro iso. Best Regards Qiang Wang

2 1

Re: [CentOS-devel] how to use livecd-creator to create my own
by wqlxx007＠gmail.com 10 Apr '17

10 Apr '17

1 0

how to use livecd-creator to create my own livecd iso which is same as offical release iso？
by 王强 09 Apr '17

09 Apr '17

2 1

CentOS PaaS SIG meeting (2017-04-05)
by Troy Dawson 05 Apr '17

05 Apr '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 05 April 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated testing and Automated rpm building -- Images and Image building -- Multi-arch -- separate repo work -- minishift - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2017/march/centos-devel.2017-03-29-16.57.log…

1 1

updated external-repos for CBS with CentOS 6.9
by Fabian Arrotin 05 Apr '17

05 Apr '17

As we announced/released 6.9 today (https://lists.centos.org/pipermail/centos-announce/2017-April/022351.html) , we reflected that in the internal mirror used by koji/cbs.centos.org so from now on, all built content will be built against 6.9. We regenerated also all the metadata from within koji to reflect this. Should you have issues, feel free to discuss those on this list, or #centos-devel on irc.freenode.net -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

CentOS PaaS SIG meeting (2017-03-29)
by Troy Dawson 31 Mar '17

31 Mar '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 29 March 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current StatusI -- rpms -- Documentation -- Automated testing and Automated rpm building -- Multi-arch -- separate repo work -- minishift - Open Floor

2 2

Status update on CentOS Community Container Pipeline
by Bamacharan Kundu 30 Mar '17

30 Mar '17

Hi All, Below is updates for the recent works done on CentOS Community Container Pipeline * Clear up the pods and environment once build is complete * Getting all mails from container-pipeline logged in a mailing list * RPM tracking and updating container images based on RPM updates. * Postgresql (upstream) and making sure they work with openshift * Wildfly swarm stack is containerized now. * Ported Alpine based NSQ (https://nsq.io) container image to CentOS * Linter upgrade to prevent the message raised by `FROM` statement Our Current focus is on: * Single mail notification for end to end status for builds in pipeline to user * Setting up external registry * Fixing up current build repeat issue * Refactoring workers to make them more efficient * Fix jenkins issue on CI and debug failing builds on CI * Resolve container dependencies during build * Work on provision to update container images (using jenkins to use a trigger based system to pull in image when new image is pushed to the registry.) * Containerize Kyto Tycoon with the ability to run the same on openshift * Implement the usage of container graph for rpm based rebuilds in controlled and efficient manner. * Integrated container capabilities scanner with scan worker Regards Bama Charan Kundu

1 0

Pull request/Changes to CentOS Extras repo??
by Martin Juhl 29 Mar '17

29 Mar '17

Hi guys... I have some packages in the Extras repo, that I would like to be built for python3 as well as python2... I can provide the changes for the spec files, but what is the official way to commit changes / pull requests???? I would of cource then become the package manager of these packages... (we need them in the COPR project) Regards Martin Juhl

2 1

Providing checksums for our Vagrant images
by Laurentiu Pancescu 23 Mar '17

23 Mar '17

Hi there, I've been looking at making it easier for Vagrant users to verify our images when adding them. The Vagrant documentation mentions that the checksum can be added to the box metadata[1], and that this is done automatically if you build the box on Atlas - indeed, the source code shows they are verifying a checksum from the downloaded metadata[2]. Unfortunately, Atlas does not seem to provide such a checksum for any of the boxes I checked - neither those hosted by them, like debian/jessie64, nor external ones like ours' or Fedora's. The Bento boxes seemed to offer a checksum, but that's just their complete JSON metadata somehow ending up in the description field on Atlas (I assume that's an automatic step not doing what the Bento developers intended - I saw no message about verifying the checksum when adding bento/debian-8.7). We already host the images on cloud.centos.org. We could also generate the needed JSON metadata (we only need one file for all centos/7 images, and one for centos/6), including the SHA256 checksums. We could also create two Apache aliases (e.g. cloud.centos.org/vagrant/7) to make life easier for our users - after an initial "vagrant box add https://cloud.centos.org/vagrant/7", which would prove the checksum automatically, they would also be notified when new images appear and be able to use "vagrant box update centos/7", just like they do now. This would allow us to even move away from Atlas, if desired. We would finally be able to completely automate our Vagrant releases, instead of manually adding the releases to Atlas every month, and not even having embedded checksums. There was an Atlas CLI that proved not to work as expected: our 1701 and 1702 releases didn't end up on Atlas, we had to intervene. The big question is how we could communicate this to our users, not the technical side: I already tested this with a local webserver, serving the centos/7 JSON downloaded from Atlas, which I edited to add an SHA256 checksum - Vagrant automatically verified the checksum after the download was finished. Any thoughts? Laurențiu [1] https://www.vagrantup.com/docs/boxes/format.html#box-metadata [2] https://github.com/mitchellh/vagrant/blob/master/lib/vagrant/action/builtin…

3 6

CentOS PaaS SIG meeting (2017-03-22)
by Troy Dawson 22 Mar '17

22 Mar '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 22 March 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current StatusI -- rpms -- Documentation -- images / image building -- Multi-arch -- separate repo work -- minishift - Open Floor

1 1

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