Re: [CentOS] vault.centos.org down
> On Tue, 1 Mar 2022 16:36:55 -0700 > Nels Lindquist wrote: > >> I've been unable to access it at all for the past couple of days, either >> through a browser or yum. > > https://downforeveryoneorjustme.com/vault.centos.org Doesn't help here because downforeveryoneorjustme.com is not working currently: Error 520 Ray ID: 6ae04324820783 • 2022-03-02 07:23:20 UTC Web server is returning an unknown error You Browser Working Frankfurt Cloudflare Working downforeveryoneorjustme.com Host Error Nice new world, clouds everywhere, how can they fail :) Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Need fstab-decode for CentOS 8
On 3/1/22 15:36, Robert Nichols wrote:
"${cmdline[@]}"
The problem there is that the last line is going to get interpreted by
a shell before anything is executed, so you now have to escape
characters that are special to the shell within a quoted string. This
is unlike the compiled fstab-decode program that invokes the execvp()
library call and avoids further shell parsing.
Does it, though?
$ bash fstab-decode.sh echo '$PATH'
$PATH
$ bash fstab-decode.sh ls '*'
ls: cannot access '*': No such file or directory
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] vault.centos.org down
On 2/03/22 12:36 pm, Nels Lindquist wrote: On 2022/03/01 10:35 a.m., Simon Matter wrote: On 2/28/22 23:46, Simon Matter wrote: Yes, also mostly down for me. Some requests were answered but unable to really use the site. Is it just overloaded? I've seen a few examples recently of people building CentOS 8 containers by building repo definitions that reference vault. Naturally, I asked them to stop doing that... If overload is the problem, I'd suggest that making the site *less* reliable might eventually fix the problem. In particular, dropping requests for repomd.xml would probably shed a lot of load while still giving human users access to package files. In my case I was just trying with firefox to get some files and browsing wasn't possible at all. Suddenly some pages were shown and then connection was stuck again. However, currently it works fine for me. I've been unable to access it at all for the past couple of days, either through a browser or yum. There are working mirrors you can use: https://mirror.rackspace.com/centos-vault/ Peter ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] vault.centos.org down
On Tue, 1 Mar 2022 16:36:55 -0700 Nels Lindquist wrote: > I've been unable to access it at all for the past couple of days, either > through a browser or yum. https://downforeveryoneorjustme.com/vault.centos.org -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] vault.centos.org down
On 2022/03/01 10:35 a.m., Simon Matter wrote: On 2/28/22 23:46, Simon Matter wrote: Yes, also mostly down for me. Some requests were answered but unable to really use the site. Is it just overloaded? I've seen a few examples recently of people building CentOS 8 containers by building repo definitions that reference vault. Naturally, I asked them to stop doing that... If overload is the problem, I'd suggest that making the site *less* reliable might eventually fix the problem. In particular, dropping requests for repomd.xml would probably shed a lot of load while still giving human users access to package files. In my case I was just trying with firefox to get some files and browsing wasn't possible at all. Suddenly some pages were shown and then connection was stuck again. However, currently it works fine for me. I've been unable to access it at all for the past couple of days, either through a browser or yum. Nels Lindquist ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Need fstab-decode for CentOS 8
On 3/1/22 3:46 PM, Gordon Messmer wrote:
On 3/1/22 10:29, Gordon Messmer wrote:
Chris Schanzle mentioned off-list that a tab character had been replaced with spaces (I *knew* that should have been an attached file, shame on me). He also suggested an improvement that removes the tab character, so here's a second try.
Or not? Last try.
#!/bin/sh
declare -a cmdline
tab=$'\t'
eol=$'\n'
for arg in "$@"
do
arg="${arg//\\011/$tab}"
arg="${arg//\\012/$eol}"
arg="${arg//\\040/ }"
arg="${arg//\\134/\\}"
arg="${arg///\\}"
cmdline+=("$arg")
done
"${cmdline[@]}"
The problem there is that the last line is going to get interpreted by a shell
before anything is executed, so you now have to escape characters that are
special to the shell within a quoted string. This is unlike the compiled
fstab-decode program that invokes the execvp() library call and avoids further
shell parsing.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Need fstab-decode for CentOS 8
On 3/1/22 10:29, Gordon Messmer wrote:
Chris Schanzle mentioned off-list that a tab character had been
replaced with spaces (I *knew* that should have been an attached file,
shame on me). He also suggested an improvement that removes the tab
character, so here's a second try.
Or not? Last try.
#!/bin/sh
declare -a cmdline
tab=$'\t'
eol=$'\n'
for arg in "$@"
do
arg="${arg//\\011/$tab}"
arg="${arg//\\012/$eol}"
arg="${arg//\\040/ }"
arg="${arg//\\134/\\}"
arg="${arg///\\}"
cmdline+=("$arg")
done
"${cmdline[@]}"
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS-docs] CentOS/Fedora docs meeting
The agenda for the CentOS/Fedora Docs meeting tomorrow (Wednesday 2 March at 1830 UTC) is at https://discussion.fedoraproject.org/t/docs-meeting-agenda-2022-03-02/37304 We'll see you in #meeting-1 on chat.fedoraproject.org (#fedora-meeting-1 on Libera) -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS] Need fstab-decode for CentOS 8
On 3/1/22 08:52, Gordon Messmer wrote: If you prefer a version that you don't need a C compiler to use, here's a pure bash implementation: Chris Schanzle mentioned off-list that a tab character had been replaced with spaces (I *knew* that should have been an attached file, shame on me). He also suggested an improvement that removes the tab character, so here's a second try. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] vault.centos.org down
> On 2/28/22 23:46, Simon Matter wrote: >> Yes, also mostly down for me. Some requests were answered but unable to >> really use the site. > > > Is it just overloaded? I've seen a few examples recently of people > building CentOS 8 containers by building repo definitions that reference > vault. Naturally, I asked them to stop doing that... > > If overload is the problem, I'd suggest that making the site *less* > reliable might eventually fix the problem. In particular, dropping > requests for repomd.xml would probably shed a lot of load while still > giving human users access to package files. In my case I was just trying with firefox to get some files and browsing wasn't possible at all. Suddenly some pages were shown and then connection was stuck again. However, currently it works fine for me. Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] vault.centos.org down
On 2/28/22 23:46, Simon Matter wrote: Yes, also mostly down for me. Some requests were answered but unable to really use the site. Is it just overloaded? I've seen a few examples recently of people building CentOS 8 containers by building repo definitions that reference vault. Naturally, I asked them to stop doing that... If overload is the problem, I'd suggest that making the site *less* reliable might eventually fix the problem. In particular, dropping requests for repomd.xml would probably shed a lot of load while still giving human users access to package files. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Need fstab-decode for CentOS 8
On 3/1/22 05:53, Robert Nichols wrote:
It turns out that particular wheel is best resurrected from the
fstab-decode.c file in an old initscripts source package. The encoding
is nonstandard, and the above perl code would not handle it correctly.
It's pretty close. It won't handle double backslash, and its use of
xargs is incorrect.
If you prefer a version that you don't need a C compiler to use, here's
a pure bash implementation:
#!/bin/sh
declare -a cmdline
eol=$'\n'
for arg in "$@"
do
arg="${arg//\011/ }"
arg="${arg//\012/$eol}"
arg="${arg//\040/ }"
arg="${arg//\134/\\}"
arg="${arg//\\/\\}"
cmdline+=("$arg")
done
"${cmdline[@]}"
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] mock gimmicks - experts?
On 3/1/22 06:02, lejeczek via CentOS wrote:
On 28/02/2022 21:48, Johnny Hughes wrote:
On 2/28/22 08:49, lejeczek via CentOS wrote:
Hi guys.
I'm trying something I believe is trivial, on centOS 9 with mock
version 2.16
-> $ mock -r centos-stream-8-x86_64 --rootdir=~/mock
--localrepo=/00.STORAGE/1/var/www/repos --continue --chain
./mpfr-4.1.0-7.el9.src.rpm ./libmpc-1.2.1-4.el9.src.rpm
...
CentOS Stream 8 - PowerTools 14 kB/s | 4.4 kB 00:00
Error:
Problem: cannot install the best update candidate for package
libmpc-1.1.0-9.1.el8.x86_64
- problem with installed package libmpc-1.1.0-9.1.el8.x86_64
- package libmpc-1.1.0-9.1.el8.x86_64 requires
libmpfr.so.4()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package
mpfr-3.1.6-1.el8.x86_64
- cannot install both mpfr-4.1.0-7.el8.x86_64 and
mpfr-3.1.6-1.el8.x86_64
- cannot install both mpfr-3.1.6-1.el8.x86_64 and
mpfr-4.1.0-7.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or
'--nobest' to use not only best candidate packages)
ERROR: Exception(./libmpc-1.2.1-4.el9.src.rpm)
Config(centos-stream-8-x86_64) 0 minutes 6 seconds
INFO: Results and/or logs in:
/00.STORAGE/1/var/www/repos/results/centos-stream-8-x86_64/libmpc-1.2.1-4.el9
ERROR: Command failed:
...
Why would it end up asking for 'mpfr-3.1.6' if 'libmpc-1.2.1'
requires ver. >4.x and..
why would 'ibmpc-1.1.0-9.1' even show up there I cannot wrap my head
around it.
I've only started using 'mock' but this weird stuff have not seen
until now.
Rather than passing in both SRPMS .. I would try with just one at a time.
You are first trying to build mpfr and after that, you are trying to
build libmpc.
If I am correct, the newer version of libmpc is required for mpfr. So,
first try building libmpc .. and look at what is necessary to build
that. Once you have that built, put it in your local repo and rebuild
tehmetadata and thentry to build mpfr by itself.
All '--chain' does is retry all failed builds if something actually
builds.
As to why the older version of libmpc or mpfr is trying to load ..
look at your root.log and it will tell you.
That was how I started first, each separately.
-> $ mock -r centos-stream-8-x86_64 --rootdir=~/mock
--resultdir=/00.STORAGE/1/var/www/repos/results/"{{root}}"/libmpc
libmpc-1.2.1-4.el9.src.rpm
...
Package gcc-8.5.0-10.el8.x86_64 is already installed.
Package make-1:4.2.1-11.el8.x86_64 is already installed.
No matching package to install: 'mpfr-devel >= 4.1.0'
Not all dependencies satisfied
'--chain' I believed was some way to "loop" and if one pkg might depend
on another it will (with perhaps of addition of '--continue') that would
be better alternative to "solve" those dependencies, anyway.
Having 'mpfr' ver. 4.x built and in repo, following fails the same way:
-> $ mock -r centos-stream-8-x86_64 --rootdir=~/mock
--resultdir=/00.STORAGE/1/var/www/repos/results/"{{root}}"/libmpc
libmpc-1.2.1-4.el9.src.rpm
--addrepo=http://10.3.1.100/centos-stream-8-x86_64
...
CentOS Stream 8 - PowerTools 113 kB/s | 4.4 kB 00:00
Error:
Problem: cannot install the best update candidate for package
libmpc-1.1.0-9.1.el8.x86_64
- problem with installed package libmpc-1.1.0-9.1.el8.x86_64
- package libmpc-1.1.0-9.1.el8.x86_64 requires libmpfr.so.4()(64bit),
but none of the providers can be installed
- cannot install the best update candidate for package
mpfr-3.1.6-1.el8.x86_64
- cannot install both mpfr-4.1.0-7.el8.x86_64 and
mpfr-3.1.6-1.el8.x86_64
- cannot install both mpfr-3.1.6-1.el8.x86_64 and
mpfr-4.1.0-7.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest'
to use not only best candidate packages)
'root.log' does not reveal anything, certainly not an explanation or...
I've gone blind.
My guess - because that would be such a "test" case where 'mock' fails
to tell, to explain what/how so I must only guess - is that something
else down the chain of dependencies, depends on those "older" versions
of 'mpfr' and/or 'libmpc', but..
if that theorem is true then, again, how to...
I also fiddled with 'best=' but to no avail.
https://koji.mbox.centos.org/pkgs/packages/libmpc/1.1.0/9.1.el8/data/logs/aarch64/root.log
libmpc.aarch64 is installed in the 'minimal' buildroot for all packages
built in mock. So you will have to build a newer first. (The minimum
build root contains the files starting with:
DEBUG util.py:439: bash aarch64 4.4.19-12.el8
build 1.5 M
and going to
DEBUG util.py:439: xz aarch64 5.2.4-3.el8
build 151 k
in the below file .. it pulls in all the deps listed below that .. so from:
DEBUG util.py:439: annobinaarch64 9.35-1.el8
build 103 k
to
DEBUG util.py:439: zstd aarch64 1.4.4-1.el8
build 302
Re: [CentOS] Need fstab-decode for CentOS 8
On 2/28/22 8:46 AM, Robert Nichols wrote:
On 2/28/22 1:22 AM, cen...@niob.at wrote:
Am 28.02.22 um 05:45 schrieb Robert Nichols:
On 2/27/22 12:26 PM, cen...@niob.at wrote:
Am 27.02.22 um 04:33 schrieb Robert Nichols:
Does anything for CentOS 8 provide the function of the fstab-decode utility?
Entries in /proc/mounts and /etc/fstab can have escape sequences for certain special characters, and I need to decode that.
Preface: Never heard of fstab-decode before. Researching the command made me really wonder why it
was invented. Especially since I have never seen an /etc/fstab with "escape sequences" or
"special characters" since at least 1990 (If I am wrong: Please show me such a fstab
file).
So why not just use:
umount $(awk '$3 == "vfat" {print $2}' /etc/fstab)
instead of the seemingly canonical use of fstab-decode
fstab-decode umount $(awk '$3 == "vfat" { print $2 }' /etc/fstab)
Those samples break if the mount point directory name contains spaces, tabs, or
whatever other characters I don't know about that also get represented by
escape sequences. I'm not actually using it with /etc/fstab, but with
/proc/mounts which uses the same convention. I can control /etc/fstab and avoid
the problem, but I cannot control how some auto-mounted foreign filesystem
might be named. I have a script that needs to be robust in the face of such
names.
Get creative! Unix administration is a creative job. Having said this:
Using white space within mount points is asking for trouble anyway. If you
really want this in the most generic way, then do the unquoting with something
like this:
awk '$3 == "vfat" {print $2}' /etc/fstab | perl -pl000 -e
's/\\([0-7]{3})/chr(oct($1))/eg' | xargs -0 -n 1 -r umount
This seems to be the unixy way to do this.
Yes, white space in mount points is asking for trouble, but if someone automounts a USB flash drive
filesystem which has a label that includes white space (e.g.: "USB DISK", like the VFAT
preformat on some that I have bought) or other "funny" characters, that label gets used
as the mount point directory.
Indeed, I can re-invent the wheel if that wheel is lost in the sands of time.
It turns out that particular wheel is best resurrected from the fstab-decode.c file in an
old initscripts source package. The encoding is nonstandard, and the above perl code
would not handle it correctly. Handling the unlikely oddball case seems like severe
paranoia, but this could turn out to be, "That line of code you thought would never
be executed just might save the day that one time when it _does_ get executed."
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] mock gimmicks - experts?
On 28/02/2022 21:48, Johnny Hughes wrote:
On 2/28/22 08:49, lejeczek via CentOS wrote:
Hi guys.
I'm trying something I believe is trivial, on centOS 9 with mock
version 2.16
-> $ mock -r centos-stream-8-x86_64 --rootdir=~/mock
--localrepo=/00.STORAGE/1/var/www/repos --continue --chain
./mpfr-4.1.0-7.el9.src.rpm ./libmpc-1.2.1-4.el9.src.rpm
...
CentOS Stream 8 - PowerTools 14 kB/s | 4.4 kB 00:00
Error:
Problem: cannot install the best update candidate for package
libmpc-1.1.0-9.1.el8.x86_64
- problem with installed package libmpc-1.1.0-9.1.el8.x86_64
- package libmpc-1.1.0-9.1.el8.x86_64 requires
libmpfr.so.4()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package
mpfr-3.1.6-1.el8.x86_64
- cannot install both mpfr-4.1.0-7.el8.x86_64 and
mpfr-3.1.6-1.el8.x86_64
- cannot install both mpfr-3.1.6-1.el8.x86_64 and
mpfr-4.1.0-7.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or
'--nobest' to use not only best candidate packages)
ERROR: Exception(./libmpc-1.2.1-4.el9.src.rpm)
Config(centos-stream-8-x86_64) 0 minutes 6 seconds
INFO: Results and/or logs in:
/00.STORAGE/1/var/www/repos/results/centos-stream-8-x86_64/libmpc-1.2.1-4.el9
ERROR: Command failed:
...
Why would it end up asking for 'mpfr-3.1.6' if 'libmpc-1.2.1'
requires ver. >4.x and..
why would 'ibmpc-1.1.0-9.1' even show up there I cannot wrap my head
around it.
I've only started using 'mock' but this weird stuff have not seen
until now.
Rather than passing in both SRPMS .. I would try with just one at a time.
You are first trying to build mpfr and after that, you are trying to
build libmpc.
If I am correct, the newer version of libmpc is required for mpfr.
So, first try building libmpc .. and look at what is necessary to
build that. Once you have that built, put it in your local repo and
rebuild tehmetadata and thentry to build mpfr by itself.
All '--chain' does is retry all failed builds if something actually
builds.
As to why the older version of libmpc or mpfr is trying to load ..
look at your root.log and it will tell you.
That was how I started first, each separately.
-> $ mock -r centos-stream-8-x86_64 --rootdir=~/mock
--resultdir=/00.STORAGE/1/var/www/repos/results/"{{root}}"/libmpc
libmpc-1.2.1-4.el9.src.rpm
...
Package gcc-8.5.0-10.el8.x86_64 is already installed.
Package make-1:4.2.1-11.el8.x86_64 is already installed.
No matching package to install: 'mpfr-devel >= 4.1.0'
Not all dependencies satisfied
'--chain' I believed was some way to "loop" and if one pkg might depend
on another it will (with perhaps of addition of '--continue') that would
be better alternative to "solve" those dependencies, anyway.
Having 'mpfr' ver. 4.x built and in repo, following fails the same way:
-> $ mock -r centos-stream-8-x86_64 --rootdir=~/mock
--resultdir=/00.STORAGE/1/var/www/repos/results/"{{root}}"/libmpc
libmpc-1.2.1-4.el9.src.rpm
--addrepo=http://10.3.1.100/centos-stream-8-x86_64
...
CentOS Stream 8 - PowerTools 113 kB/s | 4.4 kB 00:00
Error:
Problem: cannot install the best update candidate for package
libmpc-1.1.0-9.1.el8.x86_64
- problem with installed package libmpc-1.1.0-9.1.el8.x86_64
- package libmpc-1.1.0-9.1.el8.x86_64 requires libmpfr.so.4()(64bit),
but none of the providers can be installed
- cannot install the best update candidate for package
mpfr-3.1.6-1.el8.x86_64
- cannot install both mpfr-4.1.0-7.el8.x86_64 and mpfr-3.1.6-1.el8.x86_64
- cannot install both mpfr-3.1.6-1.el8.x86_64 and mpfr-4.1.0-7.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest'
to use not only best candidate packages)
'root.log' does not reveal anything, certainly not an explanation or...
I've gone blind.
My guess - because that would be such a "test" case where 'mock' fails
to tell, to explain what/how so I must only guess - is that something
else down the chain of dependencies, depends on those "older" versions
of 'mpfr' and/or 'libmpc', but..
if that theorem is true then, again, how to...
I also fiddled with 'best=' but to no avail.
many thanks, L.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
