Re: [CentOS] CPAN not working, or is it?
On Mar 11, 2019, at 6:16 PM, Bruce Ferrell wrote: > > What I've learned to do when I have this sort of issue is to pop out of CPAN > and into ~/.cpan/build. If you mean that you do that manually, you don’t have to. The “look” command in the cpan shell or the --look option to cpanm does that automatically. That is, it unpacks the module and drops you into a sub-shell where you can work with the module manually. Back when I still had to support CentOS 5, I’d occasionally have to do this to get some modules to build because they required local edits or configuration overrides that the upstream developers didn’t want to support, its Perl being deemed too old to bother with any more. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CPAN not working, or is it?
On Mar 11, 2019, at 5:24 PM, Pete Biggs wrote: > I use both RPM and CPAN and install into system locations. That’s the advice I’m responding to: you don’t need to install CPAN modules only to system locations to make Perl-based programs work. CPAN’s defaults on CentOS 7 are perfectly usable as-is, because CPAN is part of Perl, and Perl knows how to search multiple locations for a given package, including in CPAN’s default location *when* you run it as root. > CPAN will install the modules in ~/perl5/ That’s only true when you run cpan or cpanm as a normal user. If you run it as root, cpanm puts modules in a directory Perl finds by default — /usr/local/share/perl5 on CentOS 7 — but which doesn’t conflict with CPAN modules installed via RPM. ~/perl5 isn’t in @INC by default, though, so that’s why Perl fails to find modules installed there by default. However, there are a bunch of ways to adjust @INC to suit local needs, so installing to ~/perl5 isn’t always a problem: https://perlmaven.com/how-to-change-inc-to-find-perl-modules-in-non-standard-locations A useful variant on one of those methods is to put lib/ in a known location relative to the main program, then use the FindBin module to adjust @INC at run time via “use lib”: https://perldoc.perl.org/FindBin.html The second class of problems I think I covered adequately in my first reply. > All I was trying to do was to explain to Gary *why* his CPAN installs > weren't working as expected, and that it is because of the possibility > of CPAN over-writing RPM installed modules That’s why you don’t want to be telling CPAN to install to system locations in the first place. RPMs and cpanm-installed libraries should never conflict on disk. They may conflict in their dependency graphs, of course, which again takes us back to my advice in the prior reply for managing dependencies. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 7 Installation Problems
I attempted to install CentOS 7 x86_64 on my machine that has the following hardware: Motherboard: ASRock X99 Taichi BIOS: AMI v P1.40 08/04/2016 CPU: Intel Core I7-5820K RAM: 64 GB (8 x 8 GB DIMM) Optical: LG Blu Ray 25 G / 50 G burner Storage: 2 - 120GB PNY CS1311 SSD 4 - 4 TB Western Digital hard drives The 2 SSD drives are divided into 3 software RAID-1 devices: /dev/sda1 | /dev/sdb1 = /dev/md0 (2 GB) /dev/md0 /boot /dev/sda2 | /dev/sdb2 = /dev/md1 (77 GB) LVM /dev/VG_opsys /dev/vg_opsys/lv_root / 8 GB /dev/vg_opsys/lv_archive /archive 2 GB /dev/vg_opsys/lv_opt /opt 2 GB /dev/vg_opsys/lv_tmp /tmp 5 GB /dev/vg_opsys/lv_usr /usr 12 GB /dev/vg_opsys/lv_usr_local /usr/local 2 GB /dev/vg_opsys/lv_var /var 8 GB /dev/sda3 | /dev/sdb3 = /dev/md2 (32 GB) LVM /dev/vg_sysswap /dev/vg_sysswap/lv_sysswap swap 16 GB 4 - 4 TB Western Digital hard drives The 4 WD drives are divided into a single software RAID-10 device: /sdc1 | /sdd1 | /sde1 | /sdf1 = /dev/md3 (7.28 TB) LVM /dev/vg_jpd1data /dev/vg_jpd1data/lv_dbmsu00 /dbmsu00 160 GB /dev/vg_jpd1data/lv_websoft /websoft 70 GB ... ETC ... I like this configuration so I thought ... Installation attempt 1: Machine had been running CentOS 6.10 x86_64 with no problems at all. But I wanted to do some things on this machine and I didn't want to have to do a upgrade next year. I backed up all of the data on another machine so I wouldn't suffer a data loss. Inserted the CentOS 7 DVD and rebooted - for whatever reason it didn't see the DVD. Installation attempt 2: Rebooted and selected F11 for the boot menu and selected the SATA device for the Blu Ray (BTW, there was another selection that allowed me to boot UEFI for the Blu Ray). The installation continued and when I got the the storage screen I selected all 6 storage devices. When I got to the point where I tried to select all of the file systems (BTW, the /boot device was listed as unknown) I wanted format the volumes /boot, OpSys, and swap and I wanted to just mount the devices defined on the RAID-10 device. When I tried to accept the definitions the install just hung at the point. I had to power off the machine. Installation attempt 3: I decided to start from scratch so I went into rescue mode and removed all of the partitions on all 6 disks. So when I got the the storage screen I only selected the 2 120GB disks and went through a complete definition for /boot, vg_opsys, and vg_sysswap. But once again when I got to the point where I had to accept what was to be formatted it hung and had to be powered off t restart the install. I thought it might be my DVD so I downloaded a minimal install to try again. Installation attempt 4. I remembered that there are instructions on how to add software raid-1 on a running machine. So I did the allocations on a single 120 GB drive (/dev/sda). When I got to the same point as the first 3 attempts it once again hung. I rebooted on my GParted DVD and removed all the partitions on all 6 drives. Then rebooted using the CentOS 6 DVD and did the complete install including the RAID-10 devices. Why could I install completely CentOS 6 but not CentOS 7? Note: When booting I saw a selection for PF2 so I could setup UEFI. Also PF11 allows me to make a choice to boot from SATA3 standard MBR or UEFI boot. What am I doing wrong? -- Eugene Poole Woodstock, Georgia ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS-es] Revista Atix 29
Estimad@s, comunicarles que la Revista Atix, ha liberado su nuevo numero, que puede ser descargado desde su sitio web. http://revista.atixlibre.org salu2 -- -- Esteban Saavedra López CEO AtixLibre - Bolivia esteban.saave...@atixlibre.org estebansaave...@yahoo.com estebansaave...@gmail.com jesaave...@opentelematics.org Bolivia _ Te Invito a Visitarme y conocer mis Áreas de Investigación http://esteban.opentelematics.org http://revista.atixlibre.org http://www.atixlibre.org GPG Key ID: 0x0E96FE54 65A1 CEA6 712D 355B F9DD 5B62 DE1B 7381 0E96 FE54 _ ___ CentOS-es mailing list CentOS-es@centos.org https://lists.centos.org/mailman/listinfo/centos-es
Re: [CentOS] CPAN not working, or is it?
On 3/11/19 9:53 AM, Gary Stainburn wrote: On Monday 11 March 2019 16:42:21 Pete Biggs wrote: I'm afraid I'm not expert on these things - I tend to do the naughty thing of using CPAN to install in system locations! Hi Peter, Do you have any instructiions on how to do this? I realise it's far from ideal, but I need to get this system working, and can do it on a stand alone server. But I think the .spec file generated, or the variables used for the it is trying to package /usr/share/ I think you need the help of someone who knows about .spec files! I did wonder if maybe my rpmbuild spec is wrong as every RPM I'm trying to create is looking in the wrong location for the man pages, and the perl module files. I commented out the line for the man pages, but can't comment out the perl modules :) ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos What often happens when you have "larger" modules, they reply on libraries. To build the perl module from source, you need to devel rpm of the library installed to link against. example libxml2-2.7.6-21.el6_8.1.x86_64 libxml2-devel-2.7.6-21.el6_8.1.x86_64 XML::Simple won't build unless the devel is present CPAN isn't real good at reporting why the build failed, just that it failed. What I've learned to do when I have this sort of issue is to pop out of CPAN and into ~/.cpan/build. Locate the unpacked module and try the build manually. I get better errors that way. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CPAN not working, or is it?
> > I started off as always by using RPM's for everything I possibly can. > > I try to do that, too. The claim in another reply that RPM CPAN > modules and cpan- or cpanm-installed modules cannot work together is > incorrect. Since I'm the only other person to reply, I presume you mean something I said, but I don't think I ever said they "cannot work together" - in fact I said that personally, I use both RPM and CPAN and install into system locations. All I was trying to do was to explain to Gary *why* his CPAN installs weren't working as expected, and that it is because of the possibility of CPAN over-writing RPM installed modules (and the confusion that may result), and that this was deemed to be a bad thing so the default install location was changed. P. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] nvidia on 7.6
Hi Phil, On 3/11/19 12:25 PM, Phil Perry wrote: On 11/03/2019 12:41, Pete Geenhuizen wrote: Hi Pete, Apologies, that one is our fault. To fix (or rather work around), please could you force remove the above package then the yum update should proceed smoothly: rpm -e --nodeps nvidia-x11-drv-340xx-libs then: yum update and reboot your system to ensure you pick up the changes. Alternatively, just uninstall the nvidia drivers and reinstall them which will pick up the latest versions, thus also working around the issue above. No worries some things just happen, your solution worked just fine. Thanks Pete -- If money can fix it, it's not a problem. -- Click and Clack the Tappet brothers -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CPAN not working, or is it?
On 3/11/19 1:57 PM, Warren Young wrote: *snip* What is correct is that the CentOS-provided RPMs are often sufficiently outdated that they no longer work with the latest releases that cpanm wants to download by default. Often I end up downloading a src.rpm from Fedora for perl modules and building that. It means security patches are now my responsibility for it, and sometimes it has other perm module dependencies that I have to do the same thing with first, but it usually it works without too much fuss. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS-announce] CEBA-2019:0479 CentOS 6 java-1.8.0-openjdk BugFix Update
CentOS Errata and Bugfix Advisory 2019:0479
Upstream details at : https://access.redhat.com/errata/RHBA-2019:0479
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
2fe8e956a1fde3b17a3fbb6375fded2cf217d1975ec8af8e62a7bf8074e6cec1
java-1.8.0-openjdk-1.8.0.201.b09-2.el6_10.i686.rpm
afa77339d1a036d20033ef51306d12cd02571657d4fd7c48502ac7a0f3ec78e9
java-1.8.0-openjdk-debug-1.8.0.201.b09-2.el6_10.i686.rpm
7404ea7c297949267a7078d74ded744674cd3160862f02a2dc575dea911b60c5
java-1.8.0-openjdk-demo-1.8.0.201.b09-2.el6_10.i686.rpm
5bbf1ebc4435d111e3215d1a42fbe87a5fc7d82c42b4e7132e54df997b8f2a44
java-1.8.0-openjdk-demo-debug-1.8.0.201.b09-2.el6_10.i686.rpm
a3334a115ab3067167abbed8d98683b92d6b095d6ce127c0475f2c142c7b4328
java-1.8.0-openjdk-devel-1.8.0.201.b09-2.el6_10.i686.rpm
6dc8345628aaff8e0ccfcbc5632f9eeac9146313cc34804b6c2e3c92175b012d
java-1.8.0-openjdk-devel-debug-1.8.0.201.b09-2.el6_10.i686.rpm
37c3df334dd5006a2e8ce2c71fb7ade3cae8bf38093f918e16edbfcfc95298c4
java-1.8.0-openjdk-headless-1.8.0.201.b09-2.el6_10.i686.rpm
7ea58fcbfb9153bc2ad278c00d5d34bcaafe16b853b321795546957de38281b7
java-1.8.0-openjdk-headless-debug-1.8.0.201.b09-2.el6_10.i686.rpm
16c016d68790d1ac98af90c250b325567a4835a5ddb3cc1f32bc56da28b2ebeb
java-1.8.0-openjdk-javadoc-1.8.0.201.b09-2.el6_10.noarch.rpm
7d5f25a2dc59f614089a6fb32df5d6629ffa044c33994f856690425324a67c9e
java-1.8.0-openjdk-javadoc-debug-1.8.0.201.b09-2.el6_10.noarch.rpm
89efdce04af33883b72119c2982c640cfee49707c8c9e2aa07876f05fec3ff60
java-1.8.0-openjdk-src-1.8.0.201.b09-2.el6_10.i686.rpm
6caec6b37885983d9b61b0e383eed167caa93c83b58522892f0e9b0c62c4d70a
java-1.8.0-openjdk-src-debug-1.8.0.201.b09-2.el6_10.i686.rpm
x86_64:
aebc0831d818aa4011107bbf32ed7d0bcbe350f6b1bb9ea3d3d16d26bbf3a8f9
java-1.8.0-openjdk-1.8.0.201.b09-2.el6_10.x86_64.rpm
626d04faa658cc4d243bd7b7e24243e48e75538d1546b70d0a395a28da640e99
java-1.8.0-openjdk-debug-1.8.0.201.b09-2.el6_10.x86_64.rpm
f504d15cb99f34d690ef34fd60e592ce0dfb4495e4c15c7b6f9e97cdc5fea86f
java-1.8.0-openjdk-demo-1.8.0.201.b09-2.el6_10.x86_64.rpm
c09f89875b81d01ab39ad3ba327382316ff1499d614725bd0a326d7e46530eae
java-1.8.0-openjdk-demo-debug-1.8.0.201.b09-2.el6_10.x86_64.rpm
84a3f313db2dfce7ca1245f5bf36e6a16d3688e4d1a038f1ca418c53feb89926
java-1.8.0-openjdk-devel-1.8.0.201.b09-2.el6_10.x86_64.rpm
9a8e4d8667a689ffa27edb72b78a06286431caa520b40324f973ffa47a12243d
java-1.8.0-openjdk-devel-debug-1.8.0.201.b09-2.el6_10.x86_64.rpm
1d2cfe49fcb8aa2fa3ee52453faee27df62e5eeb52978f54404b4998f15b0c62
java-1.8.0-openjdk-headless-1.8.0.201.b09-2.el6_10.x86_64.rpm
c8b4de089bb0ca589d0bca526ac59fd918b86d1b0fa8439974179e1a7d9b4f9f
java-1.8.0-openjdk-headless-debug-1.8.0.201.b09-2.el6_10.x86_64.rpm
16c016d68790d1ac98af90c250b325567a4835a5ddb3cc1f32bc56da28b2ebeb
java-1.8.0-openjdk-javadoc-1.8.0.201.b09-2.el6_10.noarch.rpm
7d5f25a2dc59f614089a6fb32df5d6629ffa044c33994f856690425324a67c9e
java-1.8.0-openjdk-javadoc-debug-1.8.0.201.b09-2.el6_10.noarch.rpm
ecf829a845ff9f466ea32956109bbe314711e1b3f870348945f7f46f005a4cf3
java-1.8.0-openjdk-src-1.8.0.201.b09-2.el6_10.x86_64.rpm
9d227593bd94a71f38b5e801fa5e032a94407cd557cc4e629df23b3eb301b3ab
java-1.8.0-openjdk-src-debug-1.8.0.201.b09-2.el6_10.x86_64.rpm
Source:
35da6bd4135bb3d8e2af49950d447d6180da0317d620b6406b6ca65ec55d0d04
java-1.8.0-openjdk-1.8.0.201.b09-2.el6_10.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
[CentOS-announce] CESA-2019:0462 Moderate CentOS 6 java-1.7.0-openjdk Security Update
CentOS Errata and Security Advisory 2019:0462 Moderate
Upstream details at : https://access.redhat.com/errata/RHSA-2019:0462
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
c3586d95e2fa824ec412d2f80596f82fbe2b40301076695cc77b3c14f83f4bde
java-1.7.0-openjdk-1.7.0.211-2.6.17.1.el6_10.i686.rpm
bb7ff3eb2f4e0b76ea93028304445a8e5c705eccabcd52b3b24f3b0b63226ea9
java-1.7.0-openjdk-demo-1.7.0.211-2.6.17.1.el6_10.i686.rpm
3ae9e1e7a626483ee9e4dd6ff1ba253f09d9e3d7efd65a9580b990a554a2e8cf
java-1.7.0-openjdk-devel-1.7.0.211-2.6.17.1.el6_10.i686.rpm
1ee44e9cfbe5f6a16937c09333e7bec92151d598cc7b2f8803a1d6be79cd06aa
java-1.7.0-openjdk-javadoc-1.7.0.211-2.6.17.1.el6_10.noarch.rpm
50cebaa3180efa9307414f95d91096001296afb04e548c3f8043d00a98e1d12d
java-1.7.0-openjdk-src-1.7.0.211-2.6.17.1.el6_10.i686.rpm
x86_64:
2c3796a0d7ea50c8a42f11d2497e3e621874c0c99dbf560ee891e87e127853f1
java-1.7.0-openjdk-1.7.0.211-2.6.17.1.el6_10.x86_64.rpm
f76a02ac6d800d638ff5c240a32dfbe971c8951968f65243354d0cbb7ecd5d61
java-1.7.0-openjdk-demo-1.7.0.211-2.6.17.1.el6_10.x86_64.rpm
e38faa76e6932f73560cc97a3881778d90884b44a8d40a342317934015abe6ce
java-1.7.0-openjdk-devel-1.7.0.211-2.6.17.1.el6_10.x86_64.rpm
1ee44e9cfbe5f6a16937c09333e7bec92151d598cc7b2f8803a1d6be79cd06aa
java-1.7.0-openjdk-javadoc-1.7.0.211-2.6.17.1.el6_10.noarch.rpm
3644db16af85dab6ffc6f315eed6dc4d7d2a44e28c9240d7a25df371f6d40b87
java-1.7.0-openjdk-src-1.7.0.211-2.6.17.1.el6_10.x86_64.rpm
Source:
3f4ee6b87f651c81639a673b89a91f437fd1ceccd4af70c04ba6b6a9deb4cc96
java-1.7.0-openjdk-1.7.0.211-2.6.17.1.el6_10.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
Re: [CentOS] CPAN not working, or is it?
On Mar 11, 2019, at 8:01 AM, Gary Stainburn wrote: > > Anyone got any ideas what I need to do? First, use cpanm instead of the old cpan shell: $ sudo yum install perl-App-cpanminus It has a number of advantages: 1. It’s much smarter about chasing dependencies, which is your core problem here. 2. It autoconfigures, not requiring all that outdated stuff about “where is your FTP program,” “what mirror should I use,” and such. 3. It’s easy to feed it a cpanfile with a curated set of dependencies for a one-command “install everything I need here” upgrade: https://metacpan.org/pod/distribution/Module-CPANfile/lib/cpanfile.pod 4. When it fails, it keeps its output in a log file that’s easy to send to mailing lists when asking for help. Hint. :) > I started off as always by using RPM's for everything I possibly can. I try to do that, too. The claim in another reply that RPM CPAN modules and cpan- or cpanm-installed modules cannot work together is incorrect. What is correct is that the CentOS-provided RPMs are often sufficiently outdated that they no longer work with the latest releases that cpanm wants to download by default. The older the CentOS installation, the greater the chance of this happening, and the greater the chance that it will happen to a module that’s so deeply tied into your dependency tree that it seems to break everything. There are three main solutions: 1. Tell cpanm to download an older version that works with the other RPM-installed CPAN modules: $ sudo cpanm Foo::Bar@1.2.3 1b: Same thing, but in cpanfile syntax: requires 'Foo::Bar', ‘== 1.2.3'; cpanfile is very flexible and can be given much more granular rules; see the link above. 2. Selectively remove CPAN modules installed via RPM that conflict and let cpanm upgrade you to the latest. This works as long as the newer modules are upwards compatible with the remaining RPM-installed CPAN modules. 3. Use a system like App::Fatpacker or Carton to bundle your app and its dependencies into a self-contained bundle that doesn’t depend on system CPAN modules: https://metacpan.org/release/Carton https://metacpan.org/pod/App::FatPacker I prefer using Carton with cpanfile, but others prefer the way App::Fatpacker works. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CPAN not working, or is it?
> > Do you have any instructiions on how to do this? I realise it's far from > ideal, but I need to get this system working, and can do it on a stand alone > server. It's a long time since I've done it, but I think CPAN puts some variables in your .bashrc to configure the process. First you should run 'perl -V' to see if there are any entries that aren't the system wide location - you are looking for the @INC path and/or variables like $PERL_LOCAL_LIB_ROOT If they are ok, at the CPAN prompt do 'o conf' to see what CPAN thinks the config is - I think the crucial options are the ones that start "mbuild_". Ultimately you can redo the CPAN config by 'o conf init'. > > > But I think the .spec file generated, or the variables used for the > > > > > > it is trying to package /usr/share/ > > > > I think you need the help of someone who knows about .spec files! > > > > I did wonder if maybe my rpmbuild spec is wrong as every RPM I'm trying to > create is looking in the wrong location for the man pages, and the perl > module files. I commented out the line for the man pages, but can't comment > out the perl modules :) The build and locations are influenced by some environment variables setup by rpmbuild - I have a feeling that the perl build process is using different locations to the rpmbuild so everything is getting confused. P. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CPAN not working, or is it?
On Monday 11 March 2019 16:42:21 Pete Biggs wrote: > I'm afraid I'm not expert on these things - I tend to do the naughty > thing of using CPAN to install in system locations! Hi Peter, Do you have any instructiions on how to do this? I realise it's far from ideal, but I need to get this system working, and can do it on a stand alone server. > > But I think the .spec file generated, or the variables used for the > > > it is trying to package /usr/share/ > > I think you need the help of someone who knows about .spec files! > I did wonder if maybe my rpmbuild spec is wrong as every RPM I'm trying to create is looking in the wrong location for the man pages, and the perl module files. I commented out the line for the man pages, but can't comment out the perl modules :) ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CPAN not working, or is it?
On Mon, 2019-03-11 at 15:48 +, Gary Stainburn wrote: > On Monday 11 March 2019 14:28:38 Pete Biggs wrote: > > > However, as I went for bigger modules, anything that had dependences > > > were then failing as the dependencie were installed OK but then did not > > > appear to be available. > > A number of things you can do. The sort of recommended way is to > > package the perl modules into an RPM and install them that way (so that > > the package managers know about them and can resolve conflicts). There > > are progs to do it for - look for cpanspec. > > I have found the following page to install using cpanspec, and all went well > until I actually want to build the RPM's. Doesn't matter what I try to build > I get the same problems with the man pages being missing, and nothing gets > built. I'm afraid I'm not expert on these things - I tend to do the naughty thing of using CPAN to install in system locations! But I think the .spec file generated, or the variables used for the build are not quite correct. You can see here: > > Manifying blib/man3/strictures::extra.3pm > Manifying blib/man3/strictures.3pm > Installing > /root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/root/perl5/lib/perl5/strictures.pm > Installing > /root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/root/perl5/lib/perl5/strictures/extra.pm > Installing > /root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/root/perl5/man/man3/strictures::extra.3pm > Installing > /root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/root/perl5/man/man3/strictures.3pm that it's installing into /root/perl5/ whereas here: > > Processing files: perl-strictures-2.06-1.el7.noarch > error: File not found by > glob: > /root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/usr/share/perl5/vendor_perl/* > error: File not found by > glob: > /root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/usr/share/man/man3/* it is trying to package /usr/share/ I think you need the help of someone who knows about .spec files! P. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] nvidia on 7.6
On 11/03/2019 12:41, Pete Geenhuizen wrote: Hi Pete, On 03/07/2019 01:56 AM, Phil Perry wrote: On 06/03/2019 23:03, Stephen John Smoogen wrote: Thank you Stephen. I assumed because they were pulling a dependency from epel that they were also from epel. Been out of town, yes I goofed vlc, smplayer, mplayer, and ffmpeg aren't in EPEL. and are in rpm-fusion. I've resolved all of that and got them all installed from nux-dextop. With all that done now when I run update I get the following error Error: Package: nvidia-x11-drv-340xx-libs-340.107-2.el7_6.elrepo.x86_64 Apologies, that one is our fault. To fix (or rather work around), please could you force remove the above package then the yum update should proceed smoothly: rpm -e --nodeps nvidia-x11-drv-340xx-libs then: yum update and reboot your system to ensure you pick up the changes. Alternatively, just uninstall the nvidia drivers and reinstall them which will pick up the latest versions, thus also working around the issue above. (@elrepo) Requires: nvidia-x11-drv-340xx = 340.107-2.el7_6.elrepo Removing: nvidia-x11-drv-340xx-340.107-2.el7_6.elrepo.x86_64 (@elrepo) nvidia-x11-drv-340xx = 340.107-2.el7_6.elrepo Updated By: nvidia-x11-drv-340xx-340.107-3.el7_6.elrepo.x86_64 (elrepo) nvidia-x11-drv-340xx = 340.107-3.el7_6.elrepo Needless to say I'm a tad confused. Pete ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CPAN not working, or is it?
On Monday 11 March 2019 14:28:38 Pete Biggs wrote:
> > However, as I went for bigger modules, anything that had dependences
> > were then failing as the dependencie were installed OK but then did not
> > appear to be available.
> A number of things you can do. The sort of recommended way is to
> package the perl modules into an RPM and install them that way (so that
> the package managers know about them and can resolve conflicts). There
> are progs to do it for - look for cpanspec.
I have found the following page to install using cpanspec, and all went well
until I actually want to build the RPM's. Doesn't matter what I try to build
I get the same problems with the man pages being missing, and nothing gets
built.
[root@lou cpanspec]# rpmbuild -ba perl-strictures.spec
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.H8RqZz
+ umask 022
+ cd /root/rpmbuild/BUILD
+ cd /root/rpmbuild/BUILD
+ rm -rf strictures-2.06
+ /usr/bin/gzip -dc /root/rpmbuild/SOURCES/strictures-2.06.tar.gz
+ /usr/bin/tar -xf -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd strictures-2.06
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.WPzjcW
+ umask 022
+ cd /root/rpmbuild/BUILD
+ cd strictures-2.06
+ /usr/bin/perl Makefile.PL INSTALLDIRS=vendor
Checking if your kit is complete...
Looks good
Warning: prerequisite bareword::filehandles 0 not found.
Warning: prerequisite indirect 0 not found.
Warning: prerequisite multidimensional 0 not found.
Writing Makefile for strictures
Writing MYMETA.yml and MYMETA.json
+ make -j2
cp lib/strictures/extra.pm blib/lib/strictures/extra.pm
cp lib/strictures.pm blib/lib/strictures.pm
Manifying blib/man3/strictures::extra.3pm
Manifying blib/man3/strictures.3pm
+ exit 0
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.pxcIGj
+ umask 022
+ cd /root/rpmbuild/BUILD
+ '[' /root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64 '!=' / ']'
+ rm -rf /root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64
++ dirname /root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64
+ mkdir -p /root/rpmbuild/BUILDROOT
+ mkdir /root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64
+ cd strictures-2.06
+ rm -rf /root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64
+ make pure_install
PERL_INSTALL_ROOT=/root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64
Manifying blib/man3/strictures::extra.3pm
Manifying blib/man3/strictures.3pm
Installing
/root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/root/perl5/lib/perl5/strictures.pm
Installing
/root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/root/perl5/lib/perl5/strictures/extra.pm
Installing
/root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/root/perl5/man/man3/strictures::extra.3pm
Installing
/root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/root/perl5/man/man3/strictures.3pm
+ find /root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64 -type
f -name .packlist -exec rm -f '{}' ';'
+
find /root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64 -depth
-type
d -exec rmdir '{}' ';'
+ /usr/bin/chmod -Rf
a+rX,u+w,g-w,o-w
/root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/root
+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz
--dwz-low-mem-die-limit
1000 --dwz-max-die-limit
11000 /root/rpmbuild/BUILD/strictures-2.06
/usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 0 CRC32s did match.
+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/redhat/brp-compress
+ /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip
+ /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1
+ /usr/lib/rpm/redhat/brp-python-hardlink
+ /usr/lib/rpm/redhat/brp-java-repack-jars
Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.RIav4H
+ umask 022
+ cd /root/rpmbuild/BUILD
+ cd strictures-2.06
+ make test
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0,
'blib/lib', 'blib/arch')"
t/*.t
t/crash.t ... ok
t/extras.t .. ok
t/strictures.t .. ok
All tests successful.
Files=3, Tests=42, 0 wallclock secs ( 0.02 usr 0.01 sys + 0.06 cusr 0.01
csys = 0.10 CPU)
Result: PASS
+ exit 0
Processing files: perl-strictures-2.06-1.el7.noarch
error: File not found by
glob:
/root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/usr/share/perl5/vendor_perl/*
error: File not found by
glob:
/root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/usr/share/man/man3/*
Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.QDACU6
+ umask 022
+ cd /root/rpmbuild/BUILD
+ cd strictures-2.06
+
DOCDIR=/root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/usr/share/doc/perl-strictures-2.06
+ export DOCDIR
+ /usr/bin/mkdir -p
/root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/usr/share/doc/perl-strictures-2.06
+ cp -pr
Changes
/root/rpmbuild/BUILDROOT/perl-strictures-2.06-1.el7.x86_64/usr/share/doc/perl-strictures-2.06
+ cp
Re: [CentOS] CPAN not working, or is it?
> However, as I went for bigger modules, anything that had dependences were > then failing as the dependencie were installed OK but then did not appear to > be available. CPAN on CentOS 7 doesn't install things in the system locations by default (and by design). This is to stop CPAN from over-writing files that actually belong to rpm packages. A number of things you can do. The sort of recommended way is to package the perl modules into an RPM and install them that way (so that the package managers know about them and can resolve conflicts). There are progs to do it for - look for cpanspec. CPAN will install the modules in ~/perl5/... by default - the "real" way of doing things is to @INC that location at the top of the perl script or set environment variables appropriately. Finally, if you must, fiddle with the CPAN configuration to install them in a system location. But be aware that things might get confused or break. P. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CPAN not working, or is it?
(I've just tried this on a second C7 box, literally clean install, only did it on Friday, with the same results) I'm replacing a dead F19 box with a new C7 one and I'm trying to get my Perl install completed. Ultimately, I need to get Selenium::Remote::Driver working, but I'm struggling before that. I started off as always by using RPM's for everything I possibly can. I then started to use CPAN for everything else. It looked like CPAN was working and things were installing "OK". However, as I went for bigger modules, anything that had dependences were then failing as the dependencie were installed OK but then did not appear to be available. The last thing I've just tried is to update CPAN as the RPM is 1.9800 and the latest is 2.6. As you can see below, the install worked, but when it reloaded, or when I came out and went back in, it still showed 1.9800 Anyone got any ideas what I need to do? cpan[2]> install CPAN Running install for module 'CPAN' Running make for A/AN/ANDK/CPAN-2.25.tar.gz Fetching with LWP: http://mirror.bytemark.co.uk/CPAN/authors/id/A/AN/ANDK/CPAN-2.25.tar.gz Fetching with LWP: http://mirror.bytemark.co.uk/CPAN/authors/id/A/AN/ANDK/CHECKSUMS Checksum for /root/.cpan/sources/authors/id/A/AN/ANDK/CPAN-2.25.tar.gz ok CPAN.pm: Building A/AN/ANDK/CPAN-2.25.tar.gz Importing PAUSE public key into your GnuPG keychain... done! (You may wish to trust it locally with 'gpg --lsign-key 450F89EC') Checking if your kit is complete... Looks good Writing Makefile for CPAN Writing MYMETA.yml and MYMETA.json cp lib/CPAN.pm blib/lib/CPAN.pm cp lib/CPAN/CacheMgr.pm blib/lib/CPAN/CacheMgr.pm cp lib/CPAN/FTP/netrc.pm blib/lib/CPAN/FTP/netrc.pm cp lib/CPAN/LWP/UserAgent.pm blib/lib/CPAN/LWP/UserAgent.pm cp lib/CPAN/FTP.pm blib/lib/CPAN/FTP.pm cp lib/CPAN/Queue.pm blib/lib/CPAN/Queue.pm cp lib/CPAN/Distroprefs.pm blib/lib/CPAN/Distroprefs.pm cp lib/CPAN/Kwalify/distroprefs.yml blib/lib/CPAN/Kwalify/distroprefs.yml cp lib/App/Cpan.pm blib/lib/App/Cpan.pm cp lib/CPAN/Kwalify.pm blib/lib/CPAN/Kwalify.pm cp lib/CPAN/Module.pm blib/lib/CPAN/Module.pm cp lib/CPAN/Author.pm blib/lib/CPAN/Author.pm cp lib/CPAN/Debug.pm blib/lib/CPAN/Debug.pm cp lib/CPAN/HTTP/Credentials.pm blib/lib/CPAN/HTTP/Credentials.pm cp lib/CPAN/API/HOWTO.pod blib/lib/CPAN/API/HOWTO.pod cp lib/CPAN/Complete.pm blib/lib/CPAN/Complete.pm cp lib/CPAN/HTTP/Client.pm blib/lib/CPAN/HTTP/Client.pm cp lib/CPAN/FirstTime.pm blib/lib/CPAN/FirstTime.pm cp lib/CPAN/Exception/blocked_urllist.pm blib/lib/CPAN/Exception/blocked_urllist.pm cp lib/CPAN/Distrostatus.pm blib/lib/CPAN/Distrostatus.pm cp lib/CPAN/Admin.pm blib/lib/CPAN/Admin.pm cp lib/CPAN/Tarzip.pm blib/lib/CPAN/Tarzip.pm cp lib/CPAN/Prompt.pm blib/lib/CPAN/Prompt.pm cp lib/CPAN/URL.pm blib/lib/CPAN/URL.pm cp lib/CPAN/Version.pm blib/lib/CPAN/Version.pm cp lib/CPAN/DeferredCode.pm blib/lib/CPAN/DeferredCode.pm cp lib/CPAN/Distribution.pm blib/lib/CPAN/Distribution.pm cp lib/CPAN/Nox.pm blib/lib/CPAN/Nox.pm cp lib/CPAN/Exception/RecursiveDependency.pm blib/lib/CPAN/Exception/RecursiveDependency.pm cp lib/CPAN/Bundle.pm blib/lib/CPAN/Bundle.pm cp lib/CPAN/Plugin/Specfile.pm blib/lib/CPAN/Plugin/Specfile.pm cp lib/CPAN/Shell.pm blib/lib/CPAN/Shell.pm cp lib/CPAN/InfoObj.pm blib/lib/CPAN/InfoObj.pm cp lib/CPAN/HandleConfig.pm blib/lib/CPAN/HandleConfig.pm cp lib/CPAN/Exception/yaml_process_error.pm blib/lib/CPAN/Exception/yaml_process_error.pm cp lib/CPAN/Plugin.pm blib/lib/CPAN/Plugin.pm cp lib/CPAN/Exception/yaml_not_installed.pm blib/lib/CPAN/Exception/yaml_not_installed.pm cp lib/CPAN/Index.pm blib/lib/CPAN/Index.pm cp lib/CPAN/Kwalify/distroprefs.dd blib/lib/CPAN/Kwalify/distroprefs.dd cp lib/CPAN/Mirrors.pm blib/lib/CPAN/Mirrors.pm cp scripts/cpan-mirrors blib/script/cpan-mirrors /usr/bin/perl -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/cpan-mirrors cp scripts/cpan blib/script/cpan /usr/bin/perl -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/cpan Manifying blib/man1/cpan-mirrors.1 Manifying blib/man1/cpan.1 Manifying blib/man3/CPAN.3pm Manifying blib/man3/CPAN::Admin.3pm Manifying blib/man3/CPAN::Tarzip.3pm Manifying blib/man3/CPAN::Queue.3pm Manifying blib/man3/CPAN::Distroprefs.3pm Manifying blib/man3/CPAN::Version.3pm Manifying blib/man3/App::Cpan.3pm Manifying blib/man3/CPAN::Kwalify.3pm Manifying blib/man3/CPAN::Nox.3pm Manifying blib/man3/CPAN::Plugin::Specfile.3pm Manifying blib/man3/CPAN::Debug.3pm Manifying blib/man3/CPAN::HandleConfig.3pm Manifying blib/man3/CPAN::Plugin.3pm Manifying blib/man3/CPAN::API::HOWTO.3pm Manifying blib/man3/CPAN::Mirrors.3pm Manifying blib/man3/CPAN::FirstTime.3pm ANDK/CPAN-2.25.tar.gz /usr/bin/make -- OK Running make test PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/00signature.t ... skipped: No Module::Signature found [INC = /root/.cpan/build/CPAN-2.25-YZAzWH/blib/lib /root/.cpan/build/CPAN-2.25-YZAzWH/blib/arch
Re: [CentOS] C7 on Dell Precision 7530
On Fri, 2019-03-08 at 18:25 +0100, wwp wrote: > Hello, > > does anybody have experience with installing and running CentOS 7 on > Dell Precision 7530 series (w/ Intel gfx chipset if that matters)? > It can be bought w/ Ubuntu 16.04 LTS pre-installed (which doesn't > attract me at all), but prior to use such hw model at work, I'd like > to > understand where I'm going to. Especially after my bad experiences > installing C7 on "modern" (read since skylake variants) hardware > whereas Ubuntu variants went better, gosh. Or maybe I should wait for > C8. > > Of course I did dig the Internet for intel, found very few stuff and > this: https://access.redhat.com/ecosystem/hardware/3431551 > > Regards, > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos I see you got no replies to your question so here goes. I've got CentOS 7 running on a Dell Precision 7510 workstation. It has NVidia graphics but I've never had problems with Intel graphics on any CentOS box before. The install was straight forward and it runs like a dream. YMMV ;-) -- Tony Molloy Home ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] nvidia on 7.6
On 03/07/2019 01:56 AM, Phil Perry wrote: On 06/03/2019 23:03, Stephen John Smoogen wrote: Thank you Stephen. I assumed because they were pulling a dependency from epel that they were also from epel. Been out of town, yes I goofed vlc, smplayer, mplayer, and ffmpeg aren't in EPEL. and are in rpm-fusion. I've resolved all of that and got them all installed from nux-dextop. With all that done now when I run update I get the following error Error: Package: nvidia-x11-drv-340xx-libs-340.107-2.el7_6.elrepo.x86_64 (@elrepo) Requires: nvidia-x11-drv-340xx = 340.107-2.el7_6.elrepo Removing: nvidia-x11-drv-340xx-340.107-2.el7_6.elrepo.x86_64 (@elrepo) nvidia-x11-drv-340xx = 340.107-2.el7_6.elrepo Updated By: nvidia-x11-drv-340xx-340.107-3.el7_6.elrepo.x86_64 (elrepo) nvidia-x11-drv-340xx = 340.107-3.el7_6.elrepo Needless to say I'm a tad confused. Pete -- Unencumbered by the thought process. -- Click and Clack the Tappet brothers -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
