[CentOS] CentOS-announce Digest, Vol 179, Issue 1

[centos-announce-request]

Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. CESA-2020:0086 Critical CentOS 6 firefox Security Update
  (Johnny Hughes)


--

Message: 1
Date: Tue, 14 Jan 2020 17:25:32 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2020:0086 Critical CentOS 6 firefox
SecurityUpdate
Message-ID: <20200114172532.ga16...@bstore1.rdu2.centos.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2020:0086 Critical

Upstream details at : https://access.redhat.com/errata/RHSA-2020:0086

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
779b010362374979244a758804f47018e5bd87c5bce89c2f19e038dbe22bdf18  
firefox-68.4.1-1.el6.centos.i686.rpm

x86_64:
779b010362374979244a758804f47018e5bd87c5bce89c2f19e038dbe22bdf18  
firefox-68.4.1-1.el6.centos.i686.rpm
271e9cc23da6f431ca2aaf101c991b99bdee8d4668cb1cf3078e72f5db54d7e5  
firefox-68.4.1-1.el6.centos.x86_64.rpm

Source:
4d07eed77a70bcc4ed1526f5cc36240325b2323f1269e69e8d522e54c0a713cf  
firefox-68.4.1-1.el6.centos.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS



--

Subject: Digest Footer

___
CentOS-announce mailing list
centos-annou...@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce


--

End of CentOS-announce Digest, Vol 179, Issue 1
***
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Limiting what devices can pair over Bluetooth?

[James Pearson]

Phil Perry wrote:



What is the threat you're trying to mitigate, specifically?  I don't see
how pairing a tablet would allow file transfers.  An unauthorized device
can't unilaterally pair with your system.

If you enable Bluetooth on a workstation (by starting the 'bluetooth'
service), then a normal user on the workstation can (for example)
transfer files to/from a mobile phone - which is something we don't allow

Users don't have to have any special perms to do this - users can pair
with any Bluetooth devices they want

i.e. it isn't possible to control what a user can and can't do with
Bluetooth - so it isn't possible to allow pairing with just particular
(or classes of) Bluetooth devices


Is it possible to control behaviour with udev rules?


No idea - I haven't found anything that allows you to 'control' 
Bluetooth - including any mention of udev rules


I have no idea if udev could be used in this way - nor where to start in 
creating possible udev rules :-)


I asked my original question on the linux-bluetooth email list - and the 
only suggestion was hacking the Bluetooth kernel modules to 'filter 
connection requests at the PSM level' ...


Thanks

James Pearson
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] [semi-OT] C7 Possible bug but I can't determine what tool has the problem

[Alessandro Baggi]

Hi all,

I'm writing a script that uses rsync to sync 2 dirs on C7.
I noticed a strange behaviour.

I have 2 dir: src and dest. In src dir I generate a testfile with "dd 
if=/dev/zero of=testfile bs=1M count=100" and when I run "du -h 
testfile" I get the correct result.
Then I sync src/ to dest/ using "rsync -avS  src/ dest/", all ok but 
when I run "du -h dest/testfile" I get 0 and if I run "du -b 
dest/testfile" I get the correct size in bytes.


I made several test to see what happens and noticed that removing -S 
(--sparse) from rsync command problem does not occour.
In another test, thinking about a problem on 0ed file, I tried file 
generation using /dev/urandom then /dev/zero and running rsync -avS the 
problem is disappeared.


This not seems to be a CentOS 7 related problem. I tried also on Fedora 
31 and get the same problem.



I wrote a simple bash script to replicate the  problem:

#!/bin/bash
mkdir src
mkdir dest
cd src
#dd if=/dev/urandom of=testfile bs=1M count=100
dd if=/dev/zero of=testfile bs=1M count=100
echo "src/testfile size:"
du -h testfile
du -b testfile
cd ..
rsync -avS  src/ dest/ > /dev/null
echo "dest/testfile size after rsync --sparse:"
du -h dest/testfile
du -b dest/testfile
rm -f dest/testfile
echo "dest/testfile size after rsync:"
rsync -av  src/ dest/ > /dev/null
du -h dest/testfile
du -b dest/testfile

There is a bug in rsync or in du or something else?

Thanks in advance.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [semi-OT] C7 Possible bug but I can't determine what tool has the problem

[Jon Pruente]

On Wed, Jan 15, 2020 at 11:38 AM Alessandro Baggi <
alessandro.ba...@gmail.com> wrote:

> Hi Jon,
> I wrote in the first mail the script with the current order of command
> that I used. Try to run in a bash script and you will see the result.
>
> If not my sequence is:
>
> dd if=/dev/zero of=src/testfile bs=1M count=100
> rsync -avS src/ dest/
> du -h dest/testfile
> du -b dest/testfile
>
> for urandom:
>
> dd if=/dev/urandom of=src/testfile bs=1M count=100
> rsync -avS src/ dest/
> du -h dest/testfile
> du -b dest/testfile
>
> without --sparse the same as first sequence without -S option.
>
> But why du reports 0M when with -b reports correct bytes and why this
> happens only with zeroed file?
>
>
Ah, I misunderstood what you meant. I had thought you might have created a
file with urandom first and then overwrote it with zeros. This is behaving
as expected with sparse files. You can create a sparse file with dd by
using seek:
https://www.thegeekdiary.com/how-to-create-sparse-files-in-linux-using-dd-command/
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [semi-OT] C7 Possible bug but I can't determine what tool has the problem

[Jon Pruente]

On Wed, Jan 15, 2020 at 10:18 AM Alessandro Baggi <
alessandro.ba...@gmail.com> wrote:

> I made several test to see what happens and noticed that removing -S
> (--sparse) from rsync command problem does not occour.
> In another test, thinking about a problem on 0ed file, I tried file
> generation using /dev/urandom then /dev/zero and running rsync -avS the
> problem is disappeared.
>

https://wiki.archlinux.org/index.php/Sparse_file#Creating_sparse_files

In short, rsync is being told to create sparse files with the -S flag, so
it does.  Could you share what you did with the urandom then zero test you
mentioned? I'm curious what exact sequence of commands you used.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [semi-OT] C7 Possible bug but I can't determine what tool has the problem

[Alessandro Baggi]

Il 15/01/20 17:51, Jon Pruente ha scritto:

On Wed, Jan 15, 2020 at 10:18 AM Alessandro Baggi <
alessandro.ba...@gmail.com> wrote:


I made several test to see what happens and noticed that removing -S
(--sparse) from rsync command problem does not occour.
In another test, thinking about a problem on 0ed file, I tried file
generation using /dev/urandom then /dev/zero and running rsync -avS the
problem is disappeared.


https://wiki.archlinux.org/index.php/Sparse_file#Creating_sparse_files

In short, rsync is being told to create sparse files with the -S flag, so
it does.  Could you share what you did with the urandom then zero test you
mentioned? I'm curious what exact sequence of commands you used.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Hi Jon,
I wrote in the first mail the script with the current order of command 
that I used. Try to run in a bash script and you will see the result.


If not my sequence is:

dd if=/dev/zero of=src/testfile bs=1M count=100
rsync -avS src/ dest/
du -h dest/testfile
du -b dest/testfile

for urandom:

dd if=/dev/urandom of=src/testfile bs=1M count=100
rsync -avS src/ dest/
du -h dest/testfile
du -b dest/testfile

without --sparse the same as first sequence without -S option.

But why du reports 0M when with -b reports correct bytes and why this 
happens only with zeroed file?





I don't know if in the original post mail script

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [semi-OT] C7 Possible bug but I can't determine what tool has the problem

[Alessandro Baggi]

Il 15/01/20 18:54, Jon Pruente ha scritto:

On Wed, Jan 15, 2020 at 11:38 AM Alessandro Baggi <
alessandro.ba...@gmail.com> wrote:


Hi Jon,
I wrote in the first mail the script with the current order of command
that I used. Try to run in a bash script and you will see the result.

If not my sequence is:

dd if=/dev/zero of=src/testfile bs=1M count=100
rsync -avS src/ dest/
du -h dest/testfile
du -b dest/testfile

for urandom:

dd if=/dev/urandom of=src/testfile bs=1M count=100
rsync -avS src/ dest/
du -h dest/testfile
du -b dest/testfile

without --sparse the same as first sequence without -S option.

But why du reports 0M when with -b reports correct bytes and why this
happens only with zeroed file?



Ah, I misunderstood what you meant. I had thought you might have created a
file with urandom first and then overwrote it with zeros. This is behaving
as expected with sparse files. You can create a sparse file with dd by
using seek:
https://www.thegeekdiary.com/how-to-create-sparse-files-in-linux-using-dd-command/
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Thank you for the suggestion. I meant -S of rsync to use disk space 
efficiently but this is a (great) misunderstood. Now I read again rsync 
man page (and your link) and this means "treat sparse files efficiently 
to save space on disk".
My question is: is rsync capable to detect sparse files from "regular" 
files? If -S is invoked and no sparse files are not in dataset, it 
treats those files as sparse files or "regular" files?


Why I get different behaviour using urandom and /dev/zero? This is 
casual/accidental?


Thank you again for your help.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [semi-OT] C7 Possible bug but I can't determine what tool has the problem

[Alessandro Baggi]

Il 16/01/20 02:21, Gordon Messmer ha scritto:

On 1/15/20 8:18 AM, Alessandro Baggi wrote:
Then I sync src/ to dest/ using "rsync -avS  src/ dest/", all ok but 
when I run "du -h dest/testfile" I get 0 and if I run "du -b 
dest/testfile" I get the correct size in bytes. 



That's not a bug, that's what sparse files are.

In POSIX systems, it's possible to treat a regular file like memory, 
and one of the things you might do with such a feature is use a file 
to keep track of the last time a user logged in.  The simplest way to 
so that is to save the time value at the offset of the user's UID.  My 
uid is 55665, so if the file weren't sparse, that one entry would 
create an enormous file, but with sparse files, the system only needs 
to allocate one block to store that value.  If a process reads that 
file, it will get all zeros from the OS until it reaches the date 
stored at my uid offset.


Applications can't tell whether a given set of zeros in a file are 
actual zeros on disk, or if they're simply parts of the file that 
haven't been written to, so when you tell rsync to create sparse 
files, it will do its best to identify blocks that are all zeros and 
simply not write to those on the destination.  Thus, if you use 
/dev/zero to create a file on the source and then rsync it with -S, 
the destination file will use zero blocks of storage. Naturally, that 
can only be true with files whose contents are null bytes, as you get 
from /dev/zero.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Thank you for your answer. I appreciated it.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8: several packages have unresolved dependencies after "dnf update all "

[David Hrbáč]

Philippe,

What's the output with '--allowerasing' switch?

We are experiencing a similar issue, dnf update:
...
 Problem 53: problem with installed package
perl-Encode-devel-4:2.97-3.el8.x86_64
  - package perl-Encode-devel-4:2.97-3.el8.x86_64 requires
perl-Encode(x86-64) = 4:2.97-3.el8, but none of the providers can be
installed

  - package perl-Encode-4:2.97-3.el8.x86_64 requires
libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both
perl-libs-4:5.24.4-398.module_el8.0.0+50+c3b345cd.x86_64 and
perl-libs-4:5.26.3-416.el8.x86_64
  - cannot install both perl-libs-4:5.26.3-416.el8.x86_64 and
perl-libs-4:5.24.4-398.module_el8.0.0+50+c3b345cd.x86_64
  - package
perl-Text-Tabs+Wrap-2013.0523-395.module_el8.0.0+50+c3b345cd.noarch
requires perl(:MODULE_COMPAT_5.24.4), but none of the providers can be
installed

  - cannot install the best update candidate for package
perl-Text-Tabs+Wrap-2013.0523-395.el8.noarch
  - package perl-libs-4:5.24.4-404.module_el8.1.0+229+cd132df8.x86_64 is
excluded
 Problem 54: problem with installed package
perl-IO-Compress-2.081-1.el8.noarch


  - package perl-IO-Compress-2.081-1.el8.noarch requires
perl(Compress::Raw::Zlib) >= 2.081, but none of the providers can be
installed
  - package perl-Compress-Raw-Zlib-2.081-1.el8.x86_64 requires
libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both
perl-libs-4:5.24.4-398.module_el8.0.0+50+c3b345cd.x86_64 and
perl-libs-4:5.26.3-416.el8.x86_64
  - cannot install both perl-libs-4:5.26.3-416.el8.x86_64 and
perl-libs-4:5.24.4-398.module_el8.0.0+50+c3b345cd.x86_64


  - package perl-Thread-Queue-3.13-1.module_el8.0.0+50+c3b345cd.noarch
requires perl(:MODULE_COMPAT_5.24.4), but none of the providers can be
installed

  - cannot install the best update candidate for package
perl-Thread-Queue-3.13-1.el8.noarch
  - package perl-libs-4:5.24.4-404.module_el8.1.0+229+cd132df8.x86_64 is
excluded
 Problem 55: problem with installed package perl-Git-2.18.1-3.el8.noarch
  - package perl-Git-2.18.2-1.el8_1.noarch requires git = 2.18.2-1.el8_1,
but none of the providers can be installed
  - package git-2.18.2-1.el8_1.x86_64 requires perl(Term::ReadKey), but
none of the providers can be installed
  - package perl-TermReadKey-2.37-7.el8.x86_64 requires
libperl.so.5.26()(64bit), but none of the providers can be installed
  - package perl-Git-2.18.1-3.el8.noarch requires git = 2.18.1-3.el8, but
none of the providers can be installed


  - package perl-Git-2.18.1-4.el8.noarch requires git = 2.18.1-4.el8, but
none of the providers can be installed


  - cannot install both
perl-libs-4:5.24.4-398.module_el8.0.0+50+c3b345cd.x86_64 and
perl-libs-4:5.26.3-416.el8.x86_64
  - cannot install both perl-libs-4:5.26.3-416.el8.x86_64 and
perl-libs-4:5.24.4-398.module_el8.0.0+50+c3b345cd.x86_64
  - package git-2.18.1-3.el8.x86_64 requires git-core-doc = 2.18.1-3.el8,
but none of the providers can be installed
  - package git-2.18.1-4.el8.x86_64 requires git-core-doc = 2.18.1-4.el8,
but none of the providers can be installed
  - package perl-Time-Local-1:1.280-1.module_el8.0.0+50+c3b345cd.noarch
requires perl(:MODULE_COMPAT_5.24.4), but none of the providers can be
installed

  - cannot install both git-core-doc-2.18.2-1.el8_1.noarch and
git-core-doc-2.18.1-3.el8.noarch
  - cannot install both git-core-doc-2.18.1-4.el8.noarch and
git-core-doc-2.18.2-1.el8_1.noarch


  - cannot install the best update candidate for package
perl-Time-Local-1:1.280-1.el8.noarch
  - cannot install the best update candidate for package
git-core-doc-2.18.1-3.el8.noarch
  - package perl-libs-4:5.24.4-404.module_el8.1.0+229+cd132df8.x86_64 is
excluded
 Problem 56: problem with installed package logwatch-7.4.3-9.el8.noarch
  - package logwatch-7.4.3-9.el8.noarch requires perl(Sys::CPU), but none
of the providers can be installed
  - perl-Sys-CPU-0.61-14.el8.i686 has inferior architecture
  - package perl-Sys-CPU-0.61-14.el8.x86_64 requires
libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both
perl-libs-4:5.24.4-398.module_el8.0.0+50+c3b345cd.x86_64 and
perl-libs-4:5.26.3-416.el8.x86_64


  - cannot install both perl-libs-4:5.26.3-416.el8.x86_64 and
perl-libs-4:5.24.4-398.module_el8.0.0+50+c3b345cd.x86_64
  - package
perl-Unicode-Normalize-1.25-1000.module_el8.0.0+50+c3b345cd.x86_64 requires
perl(:MODULE_COMPAT_5.24.4), but none of the providers can be installed


  - package
perl-Unicode-Normalize-1.25-1000.module_el8.0.0+50+c3b345cd.x86_64 requires
libperl.so.5.24()(64bit), but none of the providers can be installed


  - cannot install the best update candidate for package
perl-Unicode-Normalize-1.25-396.el8.x86_64
  - package perl-libs-4:5.24.4-404.module_el8.1.0+229+cd132df8.x86_64 is
excluded

Help dnf update --allowerasing, but all the perl packages will be removed.

Regards,
DH


čt 16. 1. 2020 v 5:33 odesílatel Philippe Piot  napsal:

> Just as a followup even g++ is broken:
>
> 

[CentOS] CentOS 8: several packages have unresolved dependencies after "dnf update all "

[Philippe Piot]

All,
  While updating my package using dnf update all I allow dnf to clean some
package with unresolved dependencies.
  I would like to reinstall some of them but got an error message "but none
of the providers can be installed" during the install process as dnf is
trying to install the dependencies.
.
  This happens for some critical package like boost-openmpi-devel (see
below for error). In fact the following package were removed and cannot be
installed:
  annobin-8.64-1.el8.x86_64
glibc-headers-2.28-42.el8.1.x86_64
  libdrm-devel-2.4.96-2.el8.x86_64
 boost-devel-1.66.0-6.el8.x86_64
  boost-openmpi-devel-1.66.0-6.el8.x86_64
boost-static-1.66.0-6.el8.x86_64
  gcc-8.2.1-3.5.el8.x86_64
 gcc-c++-8.2.1-3.5.el8.x86_64
  gcc-gdb-plugin-8.2.1-3.5.el8.x86_64
gcc-gfortran-8.2.1-3.5.el8.x86_64
  glibc-devel-2.28-42.el8.1.x86_64
 hdf5-devel-1.10.5-4.el8.x86_64
  hdf5-openmpi-devel-1.10.5-4.el8.x86_64
 hdf5-openmpi-static-1.10.5-4.el8.x86_64
  hdf5-static-1.10.5-4.el8.x86_64
libquadmath-devel-8.2.1-3.5.el8.x86_64
  libtool-2.4.6-25.el8.x86_64
libxcrypt-devel-4.1.1-4.el8.x86_64
  mesa-libEGL-devel-18.3.1-5.el8_0.x86_64
mesa-libGL-devel-18.3.1-5.el8_0.x86_64
  openmpi-devel-3.1.2-5.el8.x86_64
 poppler-qt5-devel-0.66.0-11.el8_0.12.x86_64
  qscintilla-qt5-devel-2.11.2-6.el8.x86_64
 qt5-doctools-5.11.1-5.el8.x86_64
  qt5-qtbase-devel-5.11.1-5.el8.x86_64
 qt5-qtscript-devel-5.11.1-2.el8.x86_64
  qt5-qttools-devel-5.11.1-5.el8.x86_64
qt5-qttools-static-5.11.1-5.el8.x86_64
  qt5-rpm-macros-5.11.1-2.el8.noarch
 systemtap-4.0-7.el8.x86_64
  systemtap-devel-4.0-7.el8.x86_64

Thank you for any suggestions.  -- Philippe.


ERROR MESSAGE WHEN TRYING TO INSTALL ONE OF THESE PACKAGES:
--
[piot@paris ~]$ sudo dnf install boost-openmpi-devel
[sudo] password for piot:
Last metadata expiration check: 0:13:02 ago on Wed 15 Jan 2020 10:05:29 PM
CST.
Error:
 Problem: package libquadmath-devel-8.3.1-4.5.el8.x86_64 requires gcc =
8.3.1-4.5.el8, but none of the providers can be installed
  - package gcc-8.3.1-4.5.el8.x86_64 requires glibc-devel >= 2.2.90-12, but
none of the providers can be installed
  - package boost-devel-1.66.0-6.el8.x86_64 requires
libquadmath-devel(x86-64), but none of the providers can be installed
  - package glibc-devel-2.28-72.el8.i686 requires glibc-headers, but none
of the providers can be installed
  - package glibc-devel-2.28-72.el8.i686 requires glibc-headers =
2.28-72.el8, but none of the providers can be installed
  - package glibc-devel-2.28-72.el8.x86_64 requires glibc-headers, but none
of the providers can be installed
  - package glibc-devel-2.28-72.el8.x86_64 requires glibc-headers =
2.28-72.el8, but none of the providers can be installed
  - package boost-openmpi-devel-1.66.0-6.el8.x86_64 requires
boost-devel(x86-64) = 1.66.0-6.el8, but none of the providers can be
installed
  - package glibc-headers-2.28-72.el8.i686 requires kernel-headers, but
none of the providers can be installed
  - package glibc-headers-2.28-72.el8.i686 requires kernel-headers >=
2.2.1, but none of the providers can be installed
  - package glibc-headers-2.28-72.el8.x86_64 requires kernel-headers, but
none of the providers can be installed
  - package glibc-headers-2.28-72.el8.x86_64 requires kernel-headers >=
2.2.1, but none of the providers can be installed
  - cannot install the best candidate for the job
  - package kernel-headers-4.18.0-147.0.3.el8_1.x86_64 is excluded
  - package kernel-headers-4.18.0-147.3.1.el8_1.x86_64 is excluded
  - package kernel-headers-4.18.0-147.el8.x86_64 is excluded


Philippe Piot,
https://www.niu.edu/advanced-accelerator-randd/

Northern Illinois University, Dept of Physics and
Northern Illinois Center for Accelerator & Detector Development
DeKalb, IL 60115, USA
Tel: 815 753 6473, Web:  http://www.physics.niu.edu/physics/

Argonne National Laboratory, Advanced Photon Source
Accelerator System Division
Lemont, IL 60439, USA
Tel: 630 252 2415, Web:
https://www.aps.anl.gov/Accelerator-Systems-Division
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8: several packages have unresolved dependencies after "dnf update all "

[Philippe Piot]

Just as a followup even g++ is broken:

[piot@paris ~]$ g++
bash: g++: command not found...
Install package 'gcc-c++' to provide command 'g++'? [N/y] y
 * Waiting in queue...
The following packages have to be downgraded:
 cpp-8.2.1-3.5.el8.x86_64 The C Preprocessor
 glibc-2.28-42.el8.1.i686 The GNU libc libraries
 glibc-2.28-42.el8.1.x86_64 The GNU libc libraries
 glibc-all-langpacks-2.28-42.el8.1.x86_64 All language packs for glibc.
 glibc-common-2.28-42.el8.1.x86_64 Common binaries and locale data for glibc
 glibc-langpack-en-2.28-42.el8.1.x86_64 Locale data for en
 libgomp-8.2.1-3.5.el8.x86_64 GCC OpenMP v4.5 shared support library
 libstdc++-8.2.1-3.5.el8.x86_64 GNU Standard C++ Library
 libstdc++-devel-8.2.1-3.5.el8.x86_64 Header files and libraries for C++
development
The following packages have to be installed:
 annobin-8.64-1.el8.x86_64 Binary annotation plugin for GCC
 gcc-8.2.1-3.5.el8.x86_64 Various compilers (C, C++, Objective-C, ...)
 gcc-c++-8.2.1-3.5.el8.x86_64 C++ support for GCC
 glibc-devel-2.28-42.el8.1.x86_64 Object files for development using
standard C libraries.
 glibc-headers-2.28-42.el8.1.x86_64 Header files for development using
standard C libraries.
 kernel-headers-4.18.0-80.11.2.el8_0.x86_64 Header files for the Linux
kernel for use by glibc
 libxcrypt-devel-4.1.1-4.el8.x86_64 Development files for libxcryp

On Wed, Jan 15, 2020 at 10:26 PM Philippe Piot 
wrote:

> All,
>   While updating my package using dnf update all I allow dnf to clean some
> package with unresolved dependencies.
>   I would like to reinstall some of them but got an error message "but
> none of the providers can be installed" during the install process as dnf
> is trying to install the dependencies.
> .
>   This happens for some critical package like boost-openmpi-devel (see
> below for error). In fact the following package were removed and cannot be
> installed:
>   annobin-8.64-1.el8.x86_64
> glibc-headers-2.28-42.el8.1.x86_64
>   libdrm-devel-2.4.96-2.el8.x86_64
>  boost-devel-1.66.0-6.el8.x86_64
>   boost-openmpi-devel-1.66.0-6.el8.x86_64
> boost-static-1.66.0-6.el8.x86_64
>   gcc-8.2.1-3.5.el8.x86_64
>  gcc-c++-8.2.1-3.5.el8.x86_64
>   gcc-gdb-plugin-8.2.1-3.5.el8.x86_64
> gcc-gfortran-8.2.1-3.5.el8.x86_64
>   glibc-devel-2.28-42.el8.1.x86_64
>  hdf5-devel-1.10.5-4.el8.x86_64
>   hdf5-openmpi-devel-1.10.5-4.el8.x86_64
>  hdf5-openmpi-static-1.10.5-4.el8.x86_64
>   hdf5-static-1.10.5-4.el8.x86_64
> libquadmath-devel-8.2.1-3.5.el8.x86_64
>   libtool-2.4.6-25.el8.x86_64
> libxcrypt-devel-4.1.1-4.el8.x86_64
>   mesa-libEGL-devel-18.3.1-5.el8_0.x86_64
> mesa-libGL-devel-18.3.1-5.el8_0.x86_64
>   openmpi-devel-3.1.2-5.el8.x86_64
>  poppler-qt5-devel-0.66.0-11.el8_0.12.x86_64
>   qscintilla-qt5-devel-2.11.2-6.el8.x86_64
>  qt5-doctools-5.11.1-5.el8.x86_64
>   qt5-qtbase-devel-5.11.1-5.el8.x86_64
>  qt5-qtscript-devel-5.11.1-2.el8.x86_64
>   qt5-qttools-devel-5.11.1-5.el8.x86_64
> qt5-qttools-static-5.11.1-5.el8.x86_64
>   qt5-rpm-macros-5.11.1-2.el8.noarch
>  systemtap-4.0-7.el8.x86_64
>   systemtap-devel-4.0-7.el8.x86_64
>
> Thank you for any suggestions.  -- Philippe.
>
>
> ERROR MESSAGE WHEN TRYING TO INSTALL ONE OF THESE PACKAGES:
> --
> [piot@paris ~]$ sudo dnf install boost-openmpi-devel
> [sudo] password for piot:
> Last metadata expiration check: 0:13:02 ago on Wed 15 Jan 2020 10:05:29 PM
> CST.
> Error:
>  Problem: package libquadmath-devel-8.3.1-4.5.el8.x86_64 requires gcc =
> 8.3.1-4.5.el8, but none of the providers can be installed
>   - package gcc-8.3.1-4.5.el8.x86_64 requires glibc-devel >= 2.2.90-12,
> but none of the providers can be installed
>   - package boost-devel-1.66.0-6.el8.x86_64 requires
> libquadmath-devel(x86-64), but none of the providers can be installed
>   - package glibc-devel-2.28-72.el8.i686 requires glibc-headers, but none
> of the providers can be installed
>   - package glibc-devel-2.28-72.el8.i686 requires glibc-headers =
> 2.28-72.el8, but none of the providers can be installed
>   - package glibc-devel-2.28-72.el8.x86_64 requires glibc-headers, but
> none of the providers can be installed
>   - package glibc-devel-2.28-72.el8.x86_64 requires glibc-headers =
> 2.28-72.el8, but none of the providers can be installed
>   - package boost-openmpi-devel-1.66.0-6.el8.x86_64 requires
> boost-devel(x86-64) = 1.66.0-6.el8, but none of the providers can be
> installed
>   - package glibc-headers-2.28-72.el8.i686 requires kernel-headers, but
> none of the providers can be installed
>   - package glibc-headers-2.28-72.el8.i686 requires kernel-headers >=
> 2.2.1, but none of the providers can be installed
>   - package glibc-headers-2.28-72.el8.x86_64 requires kernel-headers, but
> none of the providers can be installed
>   - package glibc-headers-2.28-72.el8.x86_64 requires kernel-headers >=
> 2.2.1, but none of the providers can be installed
>   - cannot install the best candidate for the job
>   - package 

Re: [CentOS] [semi-OT] C7 Possible bug but I can't determine what tool has the problem

[Gordon Messmer]

On 1/15/20 8:18 AM, Alessandro Baggi wrote:
Then I sync src/ to dest/ using "rsync -avS  src/ dest/", all ok but 
when I run "du -h dest/testfile" I get 0 and if I run "du -b 
dest/testfile" I get the correct size in bytes. 



That's not a bug, that's what sparse files are.

In POSIX systems, it's possible to treat a regular file like memory, and 
one of the things you might do with such a feature is use a file to keep 
track of the last time a user logged in.  The simplest way to so that is 
to save the time value at the offset of the user's UID.  My uid is 
55665, so if the file weren't sparse, that one entry would create an 
enormous file, but with sparse files, the system only needs to allocate 
one block to store that value.  If a process reads that file, it will 
get all zeros from the OS until it reaches the date stored at my uid offset.


Applications can't tell whether a given set of zeros in a file are 
actual zeros on disk, or if they're simply parts of the file that 
haven't been written to, so when you tell rsync to create sparse files, 
it will do its best to identify blocks that are all zeros and simply not 
write to those on the destination.  Thus, if you use /dev/zero to create 
a file on the source and then rsync it with -S, the destination file 
will use zero blocks of storage. Naturally, that can only be true with 
files whose contents are null bytes, as you get from /dev/zero.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-docs] [centos/centos.org] branch master updated: Switched link for centos 8.1.1911 dvd iso

[git]

This is an automated email from the git hooks/post-receive script.

arrfab pushed a commit to branch master
in repository centos/centos.org.

The following commit(s) were added to refs/heads/master by this push:
 new 95fa1e7  Switched link for centos 8.1.1911 dvd iso
95fa1e7 is described below

commit 95fa1e724e40d7e85b13072f057d777f144e087d
Author: Fabian Arrotin 
AuthorDate: Wed Jan 15 15:58:57 2020 +0100

Switched link for centos 8.1.1911 dvd iso

Signed-off-by: Fabian Arrotin 
---
 content/download.haml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/download.haml b/content/download.haml
index 8379eff..39232de 100644
--- a/content/download.haml
+++ b/content/download.haml
@@ -17,7 +17,7 @@ title: Download CentOS
 .col-sm-12
   %p
 .downloadbutton
-  %a( 
href="http://isoredirect.centos.org/centos/8/isos/x86_64/CentOS-8-x86_64-1905-dvd1.iso;
 ) CentOS Linux DVD ISO
+  %a( 
href="http://isoredirect.centos.org/centos/8/isos/x86_64/CentOS-8.1.1911-x86_64-dvd1.iso;
 ) CentOS Linux DVD ISO
   %a( 
href="http://isoredirect.centos.org/centos/8-stream/isos/x86_64/CentOS-Stream-8-x86_64-20191219-dvd1.iso;
 ) CentOS Stream DVD ISO
   %p
 ISOs are also available

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

[CentOS-announce] Release for CentOS 8 (1911) on armhfp

[Pablo Sebastián Greco]

I am pleased to announce the general availability of CentOS 8 (1911) for 
armhfp. Effectively immediately, this is the current release for CentOS 
8 and is tagged as 1911, derived from Red Hat Enterprise Linux 8.1.


As always, read through the Release Notes at: 
https://wiki.centos.org/Manuals/ReleaseNotes/CentOS8.1911 - these notes 
contain important information about the release and details about some 
of the content inside the release from the CentOS QA team. These notes 
are updated constantly to include issues and incorporate feedback from 
the users.


--
Updates, Sources, and DebugInfos

Updates released since the upstream release are all posted. We strongly 
recommend every user apply all updates, including the content released 
today, on your existing CentOS 8 machine by just running 'yum update'.


As with all CentOS 8 components, this release was built from sources 
hosted at git.centos.org. In addition, SRPMs that are a byproduct of the 
build (and also considered critical in the code and buildsys process) 
are being published to match every binary RPM we release. Sources will 
be available from vault.centos.org in their own dedicated directories to 
match the corresponding binary RPMs. Since there is far less traffic to 
the CentOS source RPMs compared with the
binary RPMs, we are not putting this content on the main mirror network. 
If users wish to mirror this content they can do so using the reposync 
command available in the yum-utils package. All CentOS source RPMs are 
signed with the same key used to sign their binary counterparts. 
Developers and end users looking at inspecting and contributing patches 
to the CentOS distro will find the code hosted at git.centos.org far 
simpler to work against. Details on how to best consume those are 
documented along with a quick start at : http://wiki.centos.org/Sources


Debuginfo packages are also being signed and pushed. Yum configs shipped 
in the new release file will have all the context required for debuginfo 
to be available on every CentOS install.


Everything we ever release, is always available on the vault service for 
people still looking for and have a real need for it.


--
Special notes

For the release of CentOS 8.1905, we didn't make it in time with armhfp, 
but now we're on track, releasing all the arches on the same day. Thanks 
to everyone who has made this possible.
For CentOS 8, we don't have (yet) RaspberryPi specific kernels, we're 
working on a way to simplify the process, and to be able to move between 
kernels.
Also, we know that there are some rpms missing in our armhfp repos in 
relation to its x86_64 counterpart, we're working on releasing them as 
soon as possible.


--
Download

In order to conserve donor bandwidth, and to make it possible to get the 
mirror content sync'd out as soon as possible, we recommend using 
torrents to get your initial installer images:


Altarch images can be downloaded at :
http://mirror.centos.org/altarch/8/isos/

sha256sums for armhfp:
3978f364add87d829f0720a00564d09740f895764f91d6a8f5cf7f022be3a431
CentOS-Userland-8-armv7hl-generic-GNOME-1911-sda.raw.xz
397362cb30658b0fd1040f0bc1fef97be472ec265c0582fd17f080567ed613fe
CentOS-Userland-8-armv7hl-generic-Minimal-1911-sda.raw.xz


--
Getting Help

The CentOS ecosystem is sustained by community driven help and guidance.
The best place to start for new users is at
http://wiki.centos.org/GettingHelp

We are also on social media, you can find the project:
on Twitter at  : http://twitter.com/CentOSProject
on Facebook at : https://www.facebook.com/groups/centosproject/
on LinkedIn at : https://www.linkedin.com/groups/22405

And you will find the core team and a majority of the contributors on 
irc, on freenode.net in #centos and #centos-arm ; talking about the 
finer points of distribution engineering and platform enablement.
Also, please consider reading 
https://wiki.centos.org/SpecialInterestGroup/AltArch/armhfp since it has 
a lot of help specific to armhfp.


--
Contributors

This release was made possible due to the hard work of many people, 
foremost on that list are the Red Hat Engineers for producing a great 
distribution and the CentOS QA team, without them CentOS would look very 
different. Many of the team went further and beyond expectations to 
bring this release to you, and I would like to thank everyone for their 
help.


We are also looking for people to get involved with the QA process in 
CentOS, if you would like to join this please introduce yourself on the 
centos-devel list (http://lists.centos.org/mailman/listinfo/centos-devel ).


Finally, please join me in thanking the donors who all make this 
possible for us.


Enjoy the fresh new release!

--
Pablo Greco

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[CentOS-announce] CESA-2020:0085 Critical CentOS 7 firefox Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2020:0085 Critical

Upstream details at : https://access.redhat.com/errata/RHSA-2020:0085

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
fc806ebbeb3b502135e880fc87d32fe05c431e5dde8faa0d7bdcae60c177c131  
firefox-68.4.1-1.el7.centos.i686.rpm
f6af9cc40e6957387f1c1dc3917b80ae5a2d6f10d0fff3786fbc3f5c59d535a1  
firefox-68.4.1-1.el7.centos.x86_64.rpm

Source:
011b1af2042a53e1a91910dc58a030a13122a01de9bd51532b2da584a400fd5c  
firefox-68.4.1-1.el7.centos.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] Release for CentOS Linux 8 (1911)

[Brian Stinson]

Release for CentOS Linux 8 (1911)

We are pleased to announce the general availability of CentOS Linux 8.
Effectively immediately, this is the current release for CentOS Linux 8 and is 
tagged as 1911, derived
from Red Hat Enterprise Linux 8.1 Source Code.

As always, read through the Release Notes at :
http://wiki.centos.org/Manuals/ReleaseNotes/CentOS8.1911  - these notes
contain important information about the release and details about some
of the content inside the release from the CentOS QA team. These notes
are updated constantly to include issues and incorporate feedback from
the users.

--
Updates, Sources, and DebugInfos

Updates released since the upstream release are all posted, across all
architectures. We strongly recommend every user apply all updates,
including the content released today, on your existing CentOS Linux 8
machine by just running 'dnf update'.

As with all CentOS Linux 8 components, this release was built from
sources hosted at git.centos.org. In addition, SRPMs that are a
byproduct of the build (and also considered critical in the code and
buildsys process) are published to match every binary RPM we
release. Sources will be available from vault.centos.org in their own
dedicated directories to match the corresponding binary RPMs. Since
there is far less traffic to the CentOS source RPMs compared with the
binary RPMs, we are not putting this content on the main mirror
network. If users wish to mirror this content they can do so using the
reposync command available in the yum/dnf-utils package. All CentOS source
RPMs are signed with the same key used to sign their binary
counterparts. Developers and end users looking at inspecting and
contributing patches to the CentOS Linux distro will find the code
hosted at git.centos.org far simpler to work against. Details on how
to best consume those are documented along with a quick start at :
http://wiki.centos.org/Sources

Debuginfo packages have been signed and pushed. Yum configs
shipped in the new release file will have all the context required for
debuginfo to be available on every CentOS Linux install.

This release supersedes all previously released content for CentOS
Linux 8, and therefore we highly encourage all users to upgrade their
machines. Information on different upgrade strategies and how to
handle stale content is included in the Release Notes.

Note that older content, obsoleted by newer versions of the same
applications are trim'd off from repos like extras/ and centosplus/

--
Download

We produced the following installer images for CentOS Linux 8
# CentOS-8.1.1911-aarch64-boot.iso: 551677952 bytes
SHA256 (CentOS-8.1.1911-aarch64-boot.iso) = 
e693b670b841d0270a393ed27b97c7efc054dc791e9e0fd77fb813c9cf4b760b
# CentOS-8.1.1911-aarch64-dvd1.iso: 5449809920 bytes
SHA256 (CentOS-8.1.1911-aarch64-dvd1.iso) = 
357f34e86a28c86aaf1661462ef41ec4cf5f58c120f46e66e1985a9f71c246e3
# CentOS-8.1.1911-ppc64le-boot.iso: 597186560 bytes
SHA256 (CentOS-8.1.1911-ppc64le-boot.iso) = 
4de170f8f3673dc5cacbf250827f4c408f0e731cbc665eb98db31fec10ea01e7
# CentOS-8.1.1911-ppc64le-dvd1.iso: 6712031232 bytes
SHA256 (CentOS-8.1.1911-ppc64le-dvd1.iso) = 
eacb40e7c721517ee6ebd188f7bbd04db0bba373afe919d73639af10613f0a1d
# CentOS-8.1.1911-x86_64-boot.iso: 625999872 bytes
SHA256 (CentOS-8.1.1911-x86_64-boot.iso) = 
7fea13202bf2f26989df4175aace8fdc16e1137f7961c33512cbfad844008948
# CentOS-8.1.1911-x86_64-dvd1.iso: 7554990080 bytes
SHA256 (CentOS-8.1.1911-x86_64-dvd1.iso) = 
3ee3f4ea1538e026fff763e2b284a6f20b259d91d1ad5688f5783a67d279423b

Information for the torrent files and sums are available at
http://mirror.centos.org/centos/8/isos/


Additional Images

Vagrant and Generic Cloud images are available at:

http://cloud.centos.org/centos/8/

--
Getting Help

The CentOS ecosystem is sustained by community driven help and
guidance. The best place to start for new users is at
http://wiki.centos.org/GettingHelp

We are also on social media, you can find the project:
on Twitter at  :http://twitter.com/CentOSProject
on Facebook at :https://www.facebook.com/groups/centosproject/
on LinkedIn at :https://www.linkedin.com/groups/22405

And you will find the core team and a majority of the contributors on
irc, on freenode.net in #centos ; talking about the finer points of
distribution engineering and platform enablement.

--
Contributors

This release was made possible due to the hard work of many people,
foremost on that list are the Red Hat Engineers for producing a great
distribution and the CentOS QA team, without them CentOS Linux would
look very different. Many of the team went further and beyond
expectations to bring this release to you, and I would like to thank
everyone for their help.

We are also looking for people to get involved with the QA process in
CentOS, if you would like to join this please introduce yourself on
the centos-devel list
(http://lists.centos.org/mailman/listinfo/centos-devel  ).

Finally,