Re: [ATrpms-devel] atrpms-rpm-config for rhel6
On Sat, May 18, 2013 at 10:30:05AM +0100, John Pilkington wrote: On 17/05/13 22:05, John Pilkington wrote: On 17/05/13 20:35, Axel Thimm wrote: thanks for the repost - on el6 both depmod and ldconfig are pulled from the proper locations, in the last days I built tons of packages and could not see the issue. There was an issue with f18 builds, but never with el6. Thanks, Axel. On Fri, May 17, 2013 at 10:34:58AM +0100, John Pilkington wrote: Hi Axel: Welcome back. I'm replying to the gossamer-threads version, so no thread. Copy of Stephen Collier's post on users' list, 9 April: The macro on line 79 of /etc/rpm/macros.atrpms doesn't seem to be working properly. Needed for F18 I guess. I have temporary changed it to build with /usr/sbin/ldconfig changed back to /sbin/ldconfig and same for depmod a few lines later. Cheers, John P I certainly saw this problem. It looks as if 'our' target environments weren't being recognised as el6. Mine was Scientific Linux, or perhaps CentOS. Would be nice to fix it for future use, but not immediately critical if the 'official' builds are ok. /etc/redhat-release contains Scientific Linux release 6.4 (Carbon) (without quotes), so it's not recognised in the first few lines of macros.atrpms and gets the Fedora 18 default? You are right, the distro is considered unknown (so clones are not 100% clones) and gets the default setting (which is not f18, just the default, which on the other hand is always the latest convention, so effectively the latest Fedora release). You can do two things: a) fast and lazy: pass dist to the build like so: rpmbuild ... --define 'dist el6' ... (actually this is the way ATrpms does it - especialy since the minimal chroots don't even contain /etc/redhat-release to have something to recognize the dist with) b) extend the %distinitials macro to include more RHEL clones. We would need a strings to grep for in some /etc/*release|issue file as well as the versioning of the matching package (e.g. rpm -qf /etc/redhat-release) -- Axel.Thimm at ATrpms.net ___ atrpms-devel mailing list atrpms-devel@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-devel
Re: [ATrpms-devel] dovecot
Hi Axel, I'm sure that they do, as I only added what was needed to get it to compile and package all files. You just too fast - I wanted to send clamav too - but you had done i too before I got there! I have a machine following f19, are the spec-files for f18 in good shape? because if they are I can start to see if they will compile there... Thanks for the good repo!!! - I will go play with upgrading to mythtv-0.26 on my f17 machine :-) Regards, Kim On 19-05-2013 09:22, Axel Thimm wrote: Thanks Kim, I had already uploaded new packages. Can you check whether they already have your changes? ___ atrpms-devel mailing list atrpms-devel@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-devel
Re: [ATrpms-devel] dovecot
Hi, On Sun, May 19, 2013 at 09:53:55AM +0200, Kim Bisgaard wrote: Hi Axel, I'm sure that they do, as I only added what was needed to get it to compile and package all files. You just too fast - I wanted to send clamav too - but you had done i too before I got there! I have a machine following f19, are the spec-files for f18 in good shape? because if they are I can start to see if they will compile there... probably the reason people use ATrpms is for the good shape of packages, so yes, they are in quite good shape, and while I haven't looked into the major changes in f19, I'm quite confident that they will rebuilt quite fine against current development/19 repos. I guess soon we'll officially start building against f19. Features are 100% and the beta is just a few days ahead. Thanks for the good repo!!! - I will go play with upgrading to mythtv-0.26 on my f17 machine :-) Great!!! Let's know how that works out! Regards, Kim On 19-05-2013 09:22, Axel Thimm wrote: Thanks Kim, I had already uploaded new packages. Can you check whether they already have your changes? ___ atrpms-devel mailing list atrpms-devel@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-devel -- Axel.Thimm at ATrpms.net ___ atrpms-devel mailing list atrpms-devel@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-devel
[ATrpms-devel] f19 builds (was: dovecot)
On Sun, May 19, 2013 at 08:23:50PM +0200, Axel Thimm wrote: On Sun, May 19, 2013 at 09:53:55AM +0200, Kim Bisgaard wrote: I have a machine following f19, are the spec-files for f18 in good shape? because if they are I can start to see if they will compile there... probably the reason people use ATrpms is for the good shape of packages, so yes, they are in quite good shape, and while I haven't looked into the major changes in f19, I'm quite confident that they will rebuilt quite fine against current development/19 repos. I guess soon we'll officially start building against f19. Features are 100% and the beta is just a few days ahead. actually I felt bit challenged to setup f19 support and just did so. An interesting new feature of rpm in f19 is that it checks changelog dates and spits out warnings if the day of the week doesn't match the given date! :) Other than that some test builds of ffmpeg for example seem to work well. I'll let the builders running, and we'll see what will come out of them. The usual fast bootstrap procedure with new Fedora releases is to allow building against the previous release, e.g. in this case offer the ATrpms packages from f18, so that in theory one pass will do everything. Then to make sure all is self-sustained the builds are redone w/o the f18 repo present. So at the end the packages are build only against f19 bits. As f19 != f19, e.g the beta is not to be assumed to be the same as the GA, the same procedure applies to the GA: Once the packages are known to be frozen on the upstream repo, e.g. there are only installer and mirroring preparations going on, all f19 packages will be rebuilt with their final fc19 tag. Previous tags will look like fc18.something. Have fun! -- Axel.Thimm at ATrpms.net ___ atrpms-devel mailing list atrpms-devel@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-devel
