Re: [CentOS] Centos 7 Yum conflict libicalss
On 7 Dec 2015 05:55, "John R Pierce" wrote: > > On 12/6/2015 9:28 PM, david wrote: >> >> Thanks for that. It appears to have solved the problem. I just wonder if it should have been taken care of "automatically" without my intervention, running nightly "yum -y update" commands. > > > epel needs to fix that package, probably. > Keep in mind the release of 7.2 has happened in the world of RHEL. This has updated a lot of components and included some that weren't there before. EPEL tracks RHEL not CentOS, so there is always some uncertainty during these times. This is one of the reasons it's worth spending some time setting up local mirrors so that they are kept stable during these transitions. There's a lot of packages in epel-testing right now and now will probably still have to be rebuilt yet. Please file bugs if epel-testing does not already have a working package so maintainers can get notification and work on them. Remember that EPEL policy is packages at least two weeks in testing so there's still some time before many can be pushed stable - and testers are always welcome! ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 7 Yum conflict libicalss
On 12/6/2015 9:28 PM, david wrote: Thanks for that. It appears to have solved the problem. I just wonder if it should have been taken care of "automatically" without my intervention, running nightly "yum -y update" commands. epel needs to fix that package, probably. -- john r pierce, recycling bits in santa cruz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 7 Yum conflict libicalss
At 09:39 PM 12/5/2015, Earl Ramirez wrote: On Sat, 2015-12-05 at 17:39 -0800, david wrote: > Folks > > My Centos 7 systems are all failing to update because of > > Error: Package: orage-4.10.0-4.el7.x86_64 (@epel) > Requires: libicalss.so.0()(64bit) > Removing: libical-0.48-6.el7.x86_64 (@base) > libicalss.so.0()(64bit) > Updated By: libical-1.0.1-1.el7.x86_64 (cr) >~libicalss.so.1()(64bit) > Error: Package: orage-4.10.0-4.el7.x86_64 (@epel) > Requires: libicalvcal.so.0()(64bit) > Removing: libical-0.48-6.el7.x86_64 (@base) > libicalvcal.so.0()(64bit) > Updated By: libical-1.0.1-1.el7.x86_64 (cr) >~libicalvcal.so.1()(64bit) > Error: Package: orage-4.10.0-4.el7.x86_64 (@epel) > Requires: libical.so.0()(64bit) > Removing: libical-0.48-6.el7.x86_64 (@base) > libical.so.0()(64bit) > Updated By: libical-1.0.1-1.el7.x86_64 (cr) >~libical.so.1()(64bit) > You could try using --skip-broken to work around the problem > You could try running: rpm -Va --nofiles --nodigest > > > Is there something I should (not) be doing? > The command was: >yum update > > > > David > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos Hello David, The conflict is caused by 'orage' from epel, I am not to familiar with that package, you can try and uninstall it and run 'yum clean all' and try to update your box again. Or you can exclude it from epel repo. _ Thanks for that. It appears to have solved the problem. I just wonder if it should have been taken care of "automatically" without my intervention, running nightly "yum -y update" commands. David ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On Sun, Dec 06, 2015 at 09:22:15PM -0500, Jonathan Billings wrote: > On Sun, Dec 06, 2015 at 06:35:58PM +, Timothy Murphy wrote: > > Always Learning wrote: > > > > > I always admire Johnny's prose, passion for Centos and his calm approach > > > to everything. > > > > Agreed. > > But two possibly OT and probably ignorant queries: > > > > 1. I am running a standard Centos 32-bit system on my home servers. > > I keep them up-to-date, but have not re-booted for several months. > > I see from /etc/centos-release that I am running 7.1. > > If I re-booted would this become 7.2? > > > > 2. If so, is this kernel panic a widespread phenomenon? > > You're running the 32-bit AltArch build of CentOS? > > The /etc/centos-release is owned by the centos-release package, and > the contents will be updated when you update that pacakge. A reboot > won't change that. In the default x86_64 release, I think that you'd > need to pull updates from the CR repo to get the 7.2.1511 packages, > still. And just look at the confusion -- because the website almost never mentions 7.1.1053 or 7.2.1511, it can be really hard to understand this discussion -- one person using "7.1" and "7.2" and the other using "7.2.1511". Good thing the 2nd person didn't use "7 (1511)", like the website does. Oh, wait: CentOS, love it or leave it. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On Sun, Dec 06, 2015 at 06:35:58PM +, Timothy Murphy wrote: > Always Learning wrote: > > > I always admire Johnny's prose, passion for Centos and his calm approach > > to everything. > > Agreed. > But two possibly OT and probably ignorant queries: > > 1. I am running a standard Centos 32-bit system on my home servers. > I keep them up-to-date, but have not re-booted for several months. > I see from /etc/centos-release that I am running 7.1. > If I re-booted would this become 7.2? > > 2. If so, is this kernel panic a widespread phenomenon? You're running the 32-bit AltArch build of CentOS? The /etc/centos-release is owned by the centos-release package, and the contents will be updated when you update that pacakge. A reboot won't change that. In the default x86_64 release, I think that you'd need to pull updates from the CR repo to get the 7.2.1511 packages, still. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos-7: odd yum output
On Sun, Dec 06, 2015 at 03:25:52PM -0500, Fred Smith wrote: > Package 1:totem-mozplugin-3.8.2-5.el7.x86_64 is obsoleted by > 1:totem-3.14.3-5.el7.x86_64 which is already installed > Nothing to do > > I don't understand, UNLESS it's saying that the totem package now includes > the plugin? > > OK, I can understand that. But looking at the contents of the RPM, it seems > to contain only plugins for itself. > > I'm just upgrading to 7.x, now, and the 6.x box previously had several > plugins installed that I can't find, nor even remember where I found 'em. > (probably has to do with my age... :[ ) The new totem plugin Obsoletes the totem-mozplugin package: # rpm -q --obsoletes -p totem-3.14.3-5.el7.x86_64.rpm totem-mythtv < 1:2.91.0-1 totem-upnp < 1:3.1.4-1 totem-jamendo < 1:3.1.4-1 totem-tracker < 1:3.1.4-1 totem-publish < 1:3.1.4-1 totem-mozplugin < 1:3.13.90-1 totem-mozplugin-vegas < 1:3.13.90-1 Its a component in GNOME, and was updated along with the rest of GNOME in RHEL 7.2 (and subsequently CentOS). It appears that that in GNOME/totem 3.14, the mozilla plugin was removed, perhaps because browsers are dropping NPAPI support. If the totem plugin *didn't* obsolete the package, you wouldn't be able to upgrade because there would be missing dependencies. This is how RPM handles this kind of situation. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On Sat, Dec 05, 2015 at 11:12:32PM -0200, Marcelo Ricardo Leitner wrote: > Damn :-( > Serial cable then? heh If you don't have IPMI serial console, yes. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Centos-7: odd yum output
Hi all! On 7.1 + CR updates, running "yum list installed | grep -y totem" gives this: yum list installed | grep -y totem totem.x86_64 1:3.14.3-5.el7 @cr totem-nautilus.x86_64 1:3.14.3-5.el7 @cr totem-pl-parser.x86_643.10.5-1.el7 @cr and "yum list installed | grep -y totem" gives this: yum list available | grep -y totem gnome-python2-totem.x86_64 2.32.0-20.el7.nuxnux-dextop totem-devel.x86_64 1:3.14.3-5.el7 cr totem-mozplugin.x86_64 1:3.8.2-5.el7base totem-mozplugin-vegas.x86_64 1:3.8.2-5.el7base totem-pl-parser.i686 3.10.5-1.el7 cr totem-pl-parser-devel.i686 3.10.5-1.el7 cr totem-pl-parser-devel.x86_64 3.10.5-1.el7 cr so then, why is it that "yum install totem-mozplugin" gives this? yum install totem-mozplugin Loaded plugins: fastestmirror, langpacks, nvidia Loading mirror speeds from cached hostfile * base: mirrors.lga7.us.voxel.net * elrepo: iad.mirror.rackspace.com * epel: mirrors.mit.edu * extras: mirror.ash.fastserv.com * nux-dextop: mirror.li.nux.ro * updates: centos.chi.host-engine.com Package 1:totem-mozplugin-3.8.2-5.el7.x86_64 is obsoleted by 1:totem-3.14.3-5.el7.x86_64 which is already installed Nothing to do I don't understand, UNLESS it's saying that the totem package now includes the plugin? OK, I can understand that. But looking at the contents of the RPM, it seems to contain only plugins for itself. I'm just upgrading to 7.x, now, and the 6.x box previously had several plugins installed that I can't find, nor even remember where I found 'em. (probably has to do with my age... :[ ) Advice will be appreciated. thanks in advance! Fred -- -- Under no circumstances will I ever purchase anything offered to me as the result of an unsolicited e-mail message. Nor will I forward chain letters, petitions, mass mailings, or virus warnings to large numbers of others. This is my contribution to the survival of the online community. --Roger Ebert, December, 1996 - The Boulder Pledge - ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] openvpn + routing
ip route: 0.0.0.0/1 via 10.8.0.5 dev tun0 default via 192.168.2.1 dev br0 proto static metric 425 10.8.0.1 via 10.8.0.5 dev tun0 10.8.0.5 dev tun0 proto kernel scope link src 10.8.0.6 88.198.140.127 via 192.168.2.1 dev br0 192.168.2.0/24 dev br0 proto kernel scope link src 192.168.2.101 metric 425 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 traceroute gmx.de traceroute to gmx.de (213.165.65.60), 30 hops max, 60 byte packets 1 Speedport.ip (192.168.2.1) 0.578 ms 0.662 ms 0.859 ms ^C [root@h1 ~]# traceroute spiegel.de traceroute to spiegel.de (62.138.116.3), 30 hops max, 60 byte packets 1 10.8.0.1 (10.8.0.1) 35.009 ms 34.982 ms 34.956 ms Why the routing is different, in first case over br0 in second over the vpn device? Have no idea what 0.0.0.0/1 is, but 62.138.116.3 is part of 0.0.0.0/1 and 213.165.65.60 is not. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] openvpn + routing
Hello, i have a little question. My system: ip route: 0.0.0.0/1 via 10.8.0.5 dev tun0 default via 192.168.2.1 dev br0 proto static metric 425 10.8.0.1 via 10.8.0.5 dev tun0 10.8.0.5 dev tun0 proto kernel scope link src 10.8.0.6 88.198.140.127 via 192.168.2.1 dev br0 192.168.2.0/24 dev br0 proto kernel scope link src 192.168.2.101 metric 425 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 traceroute gmx.de traceroute to gmx.de (213.165.65.60), 30 hops max, 60 byte packets 1 Speedport.ip (192.168.2.1) 0.578 ms 0.662 ms 0.859 ms ^C [root@h1 ~]# traceroute spiegel.de traceroute to spiegel.de (62.138.116.3), 30 hops max, 60 byte packets 1 10.8.0.1 (10.8.0.1) 35.009 ms 34.982 ms 34.956 ms Why the routing is different, in first case over br0 in second over the vpn device? How can i disable "push default route" from the server-directive on client-side in OpenVPN? I want, that only traffic, incoming over tun0 routing back over tun0. Is this possible with firewalld-cmd? Thx. Grüße Axel ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
Always Learning wrote: > I always admire Johnny's prose, passion for Centos and his calm approach > to everything. Agreed. But two possibly OT and probably ignorant queries: 1. I am running a standard Centos 32-bit system on my home servers. I keep them up-to-date, but have not re-booted for several months. I see from /etc/centos-release that I am running 7.1. If I re-booted would this become 7.2? 2. If so, is this kernel panic a widespread phenomenon? -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] lunar notation in crontab
On Sun, 6 Dec 2015 02:25:53 -0800 Alice Wonder wrote: > On 12/06/2015 02:23 AM, ken wrote: > > Crontab offers many refined facilities for Western calendaring, but none > > for traditional Eastern-- lunar-- designations. > > This could be very useful in biology where a lot of cycles are lunar based. It can also be useful for female sysadmins to schedule cleaning jobs to times when she is eager for this sort of work in the according phases of her menstrual cycle :) When a lot of users are interested in the feature, the appropriate addressee for the enhancement request are the Developers: https://fedorahosted.org/cronie/ Thanks for sharing the idea ~ Gabriele ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] lunar notation in crontab
On 12/06/2015 02:23 AM, ken wrote: Crontab offers many refined facilities for Western calendaring, but none for traditional Eastern-- lunar-- designations. So for example, if one wants specify regular occurring events on full moons or on new moons, there is no way to do this. Emacs (a text processor!?) accomplishes this. The math for calculating lunar calendaring is already available; mathematical functions are already available for simple downloading and so would need simply integration into crond. User settings in crontab would make most sense designated in the 'day of month' field with keyword either 'full' or 'new' (abbreviated with 'f' or 'n') prepended to a signed integer number of days (N * 24 hours). I.e., "new+5" would specify '5 days after the new moon'; "full-1" would specify "24 hours prior to the full moon"; "new+0", "new-0" and "new" would all mean the same: "the moment of the new moon". I suppose that alternate syntaxes could be more refined, including hours and minutes before/after new/full, so possibly useful, but then also more complex. Alternate and more refined time periods would be a question for developers. This could be very useful in biology where a lot of cycles are lunar based. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] lunar notation in crontab
Crontab offers many refined facilities for Western calendaring, but none for traditional Eastern-- lunar-- designations. So for example, if one wants specify regular occurring events on full moons or on new moons, there is no way to do this. Emacs (a text processor!?) accomplishes this. The math for calculating lunar calendaring is already available; mathematical functions are already available for simple downloading and so would need simply integration into crond. User settings in crontab would make most sense designated in the 'day of month' field with keyword either 'full' or 'new' (abbreviated with 'f' or 'n') prepended to a signed integer number of days (N * 24 hours). I.e., "new+5" would specify '5 days after the new moon'; "full-1" would specify "24 hours prior to the full moon"; "new+0", "new-0" and "new" would all mean the same: "the moment of the new moon". I suppose that alternate syntaxes could be more refined, including hours and minutes before/after new/full, so possibly useful, but then also more complex. Alternate and more refined time periods would be a question for developers. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
