[CentOS] last update yum and kernel Problem
Hello, the last update brings much Problems ? On my System the most KVM client have a crashed yum after reboot the new kernel is broken and have a panic screen I have to reboot to a older kernel ? The first I have to run yum-complete-transaction afterward i have to reinstall the kernel ?? this helps to restart the KVM Client ! is it possible the deltarpm is broken ? Also RPM or "yum check" have a problem with the new update for ipa-* I mean the problem is the naming 4.4.0-14.el7.centos.6 -- mit freundlichen Grüssen / best regards Günther J. Niederwimmer ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] last update yum and kernel Problem
I had a similar issue. On one of my vms. My host rebooted while the vm was running its update. I had to remove the kernel then reinstall and it corrected the issue. On Sat, Mar 4, 2017, 7:37 AM Günther J. Niederwimmer wrote: > Hello, > > the last update brings much Problems ? > > On my System the most KVM client have a crashed yum > > after reboot the new kernel is broken and have a panic screen > > I have to reboot to a older kernel ? > > The first I have to run > yum-complete-transaction > > afterward i have to reinstall the kernel ?? > > this helps to restart the KVM Client ! > > is it possible the deltarpm is broken ? > > Also RPM or "yum check" have a problem with the new update for ipa-* > I mean the problem is the naming > > 4.4.0-14.el7.centos.6 > > > > -- > mit freundlichen Grüssen / best regards > > Günther J. Niederwimmer > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] New C7 kernel ABI and kmods
On 03/03/17 22:56, Fred Smith wrote: On Fri, Mar 03, 2017 at 12:03:52PM -0800, Akemi Yagi wrote: On Fri, Mar 3, 2017 at 9:16 AM, Lamar Owen wrote: All, This is just a heads-up that the new C7 update kernel breaks ABI compatibility, at least as far as using the ELrepo nVidia drivers is concerned. I have posted more details to the ELrepo list; but since many folks use the Elrepo kmods I thought a heads-up would be appropriate. If you use the ELrepo nvidia kmod you will either need to hold off on the kernel update or uninstall the nvidia kmod. This is being tracked here: https://elrepo.org/bugs/view.php?id=720 didn't we just go thru this a few months ago? they're breaking it again? It's not uncommon for bits (non kABI whitelisted bits) of the kernel ABI to change at point releases, but in my experience it's very uncommon for the ABI to change within a point release series. To the best of my knowledge I recall it happening twice before on the EL6 kernel, once such example was here: http://elrepo.org/bugs/view.php?id=406 Of course any kABI changes will only affect 3rd party kernel modules using those specific ABIs so the vast majority of users will be oblivious to the changes. It just so happens in this case it affected the 3rd party nvidia drivers which are widely used. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 iso file SHA-256 hashes
On 03/03/2017 09:17 PM, Darr247 wrote: > I downloaded CentOS-7-x86_64-Everything.iso (8,233,418,752 bytes) by > clicking on the 'Everything' link in the 'Rolling' line on > https://wiki.centos.org/Download (supposedly the 1611 build). > > But when I look in the sha256sum.txt file from > https://buildlogs.centos.org/rolling/7/isos/x86_64/ (where Chrome says that > iso came from), there is no SHA hash for a file of that name. > > The reason I wanted to check it is because it's a different size than > another one I found on my hard drive while looking through the Downloads > history in Chrome. > > The other file I found was CentOS-7-x86_64-Everything-1611.iso > (8,280,604,672 bytes), which returns a hash of > af4969ebbdc479d330de97c5bfbb37eedc64c369f009cb15a97f9553ba441c88 and that > matches the value given in the sha256sum.txt file for the file of that name. > > So, my question is tri-fold. what's the SHA-256 hash supposed to be for the > file given when clicking the 'Everything' link on centos.org. > then, why is the 'official' download link sending a file that's not listed > in the hash results. > and finally, why is the file sent thusly, different from another > 'everything' iso allegedly from the same build? > The CentOS-7-x86_64-Everything.iso (without a version) is a symlink to the 'lastest' Everything iso. If you look at the sha256sum file, the last Everything file listed will be the version you use. Currently that would be: 1c1983b5bd1b5db281ee0b706c8c09f57f107a89a9d8418f60b384ef2b30b8a8 CentOS-7-x86_64-Everything-1702-01.iso signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 iso file SHA-256 hashes
CentOS [centos-boun...@centos.org], On Behalf Of Johnny Hughes, spake thusly: > The CentOS-7-x86_64-Everything.iso (without a version) is a symlink to the > 'lastest' Everything iso. If you look at the sha256sum file, the last > Everything file listed will be the version you use. > > Currently that would be: > > 1c1983b5bd1b5db281ee0b706c8c09f57f107a89a9d8418f60b384ef2b30b8a8 > CentOS-7-x86_64-Everything-1702-01.iso Good info; thanks again... but shouldn't the date code in the column labeled "Minor release" now say (1702) instead of (1611) ? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Python search path
Hello,
Working on a project to create clean spec files for libbitcoin for
CentOS 7 (and eventually I want them to work in Fedora 25+ too)
These spec files must work with the user defines an alternate %{_prefix}
before building them.
This means that python components would be installed in /opt/libbitcoin
(or whatever) instead of in /usr so %{python2_sitelib} and
%{python2_sitearch} no longer would apply.
sys.path.append looks like the way to tell python about a new path to
look for stuff, but I'm guessing there are guidelines somewhere for how
that is suppose to properly done from within spec files.
Unfortunately I can't find them, and search engines are getting harder
and harder to use to find technical related information, always changing
my query and showing me completely unrelated results.
Anyway I didn't see anything in the Fedora packaging guidelines for
python, that seems to be targeting a prefix of /usr
Thanks for any links or suggestions.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Python search path
So you want to build something independent of the system python? Is
virtualenv and / or anaconda interesting here?
On 4 March 2017 at 17:36, Alice Wonder wrote:
> Hello,
>
> Working on a project to create clean spec files for libbitcoin for CentOS
> 7 (and eventually I want them to work in Fedora 25+ too)
>
> These spec files must work with the user defines an alternate %{_prefix}
> before building them.
>
> This means that python components would be installed in /opt/libbitcoin
> (or whatever) instead of in /usr so %{python2_sitelib} and
> %{python2_sitearch} no longer would apply.
>
> sys.path.append looks like the way to tell python about a new path to look
> for stuff, but I'm guessing there are guidelines somewhere for how that is
> suppose to properly done from within spec files.
>
> Unfortunately I can't find them, and search engines are getting harder and
> harder to use to find technical related information, always changing my
> query and showing me completely unrelated results.
>
> Anyway I didn't see anything in the Fedora packaging guidelines for
> python, that seems to be targeting a prefix of /usr
>
> Thanks for any links or suggestions.
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Python search path
I want to create RPM spec file that lets the user build the RPM with an
alternate prefix - e.g.
rpmbuild -D '_prefix /opt/whatever' -bb package.spec
That results in in the python files being placed in
/opt/whatever/lib/pythonN/site-packages and
/opt/whatever/%{_lib}/pythonN/site-packages
Those directories are outside of the default python search path.
I could leave it up to the user to add them, but its nice when
installing a package just works (hence why we can put files in
/etc/ld.so.conf.d for example) without the user needing to fuss too much.
When the user builds with a different prefix, there likely will be
several different packages that put python stuff in that prefix, so a
meta package they require that adds to the search path is what I am
thinking, that both adds to the python when installed and removes it
from the python search path when removed.
On 03/04/2017 09:31 AM, Andrew Holway wrote:
So you want to build something independent of the system python? Is
virtualenv and / or anaconda interesting here?
On 4 March 2017 at 17:36, Alice Wonder wrote:
Hello,
Working on a project to create clean spec files for libbitcoin for CentOS
7 (and eventually I want them to work in Fedora 25+ too)
These spec files must work with the user defines an alternate %{_prefix}
before building them.
This means that python components would be installed in /opt/libbitcoin
(or whatever) instead of in /usr so %{python2_sitelib} and
%{python2_sitearch} no longer would apply.
sys.path.append looks like the way to tell python about a new path to look
for stuff, but I'm guessing there are guidelines somewhere for how that is
suppose to properly done from within spec files.
Unfortunately I can't find them, and search engines are getting harder and
harder to use to find technical related information, always changing my
query and showing me completely unrelated results.
Anyway I didn't see anything in the Fedora packaging guidelines for
python, that seems to be targeting a prefix of /usr
Thanks for any links or suggestions.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Python search path
Found solution, it was rather easy - just put a .pth in the "official"
site-packages containing the full path to the directory being added.
On 03/04/2017 09:55 AM, Alice Wonder wrote:
I want to create RPM spec file that lets the user build the RPM with an
alternate prefix - e.g.
rpmbuild -D '_prefix /opt/whatever' -bb package.spec
That results in in the python files being placed in
/opt/whatever/lib/pythonN/site-packages and
/opt/whatever/%{_lib}/pythonN/site-packages
Those directories are outside of the default python search path.
I could leave it up to the user to add them, but its nice when
installing a package just works (hence why we can put files in
/etc/ld.so.conf.d for example) without the user needing to fuss too much.
When the user builds with a different prefix, there likely will be
several different packages that put python stuff in that prefix, so a
meta package they require that adds to the search path is what I am
thinking, that both adds to the python when installed and removes it
from the python search path when removed.
On 03/04/2017 09:31 AM, Andrew Holway wrote:
So you want to build something independent of the system python? Is
virtualenv and / or anaconda interesting here?
On 4 March 2017 at 17:36, Alice Wonder wrote:
Hello,
Working on a project to create clean spec files for libbitcoin for
CentOS
7 (and eventually I want them to work in Fedora 25+ too)
These spec files must work with the user defines an alternate %{_prefix}
before building them.
This means that python components would be installed in /opt/libbitcoin
(or whatever) instead of in /usr so %{python2_sitelib} and
%{python2_sitearch} no longer would apply.
sys.path.append looks like the way to tell python about a new path to
look
for stuff, but I'm guessing there are guidelines somewhere for how
that is
suppose to properly done from within spec files.
Unfortunately I can't find them, and search engines are getting
harder and
harder to use to find technical related information, always changing my
query and showing me completely unrelated results.
Anyway I didn't see anything in the Fedora packaging guidelines for
python, that seems to be targeting a prefix of /usr
Thanks for any links or suggestions.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
