bc: 1.07.1 to 3.2.7

1 members found this post helpful.

I see this:
Since rsync states that can't set the files permissions I would be asking myself firstly why it can't ? It should be able to do so IMHO. So first thing would be to check how those file permissions are set. After that I would be looking at differences in the binaries and source eventually. Same source rebuild on a same system can change its own code according to how the sources are set up.
I mean, if you ever built a source code with configure scritp, you know that you can enable or disable some features of the code.

I am not saying that is not rsync fault, but just to look also for other possibilities.

Actually there is an issue with the last rsync package in Slackware64-current. I came across it as the Slint repositories are hosted c/o https://slackware.uk which runs Slackware64-current in a VM and I had this issue there when tryng to rsync. I tchat-ed about that with Tadgy and he ended up reverting to the previous rsync package (that he also hosts in /cumulative) which indeed solved the issue.

PS What happened is that most if not all files where chmod-ed 0600 by the rsync server.

explain then why when I copy the PRE REBUILD binary back in place from backup server - it works! the same with mariadb

they are same versions not later, not older, the problem only occurs since the rebuilds Jan 22 I dont know how I can make that any clearer, I just want to know if anyone is actually doing any QA on these rebuilds by running these binaries as though they would in a production environment, clearly, nobody is, now some have said its ok on 64bit, maybe its 32 bit is the problem, I sure as hell are not going to destroy a business production network trying it out (I have no spare 64 bits to put into a dev env) when my 32bit dev environment fails, because there are a lot out there still running 32 bit, just not of -current it seems, so I seem to be only one making a noise, becasue nobody else on 32bit has gone down the same path.

Yes exactly! and the logs all get filled with error notices.

Thank you, I knew I wasnt going totally senile...
64 bit, wow, bit more serious problem than I thought.

I have rsync,good and mariadb.good binaries copied to restore to working state. dev box is at present only spare box, so if a production dies, it gets thrown online, so i keep it in a working state..... or try to

strangely, its just those two, nothing else seems to he affected - that I know of anyway.

@Ressy: The issue you have with MariaDB could be completely unrelated with the issue with rsync, which indeed didn't exist in the previous rsync package, see my previous post. This is indeed on 64-bit and I indeed checked the permissions of the files to be uploaded on my local repositories, there were all 0755 or 0644. And with the newest rsync packages on the server side I got many of these "Operation not supported (95)".

PS This post crossed your last one. *I* have the right to be senile, being 72 yo

I'm not really a gambler, but if I was a betting man, I'd be betting on them being related somehow.
and yes newest rsync running as --daemon screws up, with various current and older rsync clients all get the errors from master server. Master screws up on perms, but doesnt error with chowns

haha, no you don't, when you hit 80 you might but you got a few years to go

I can not explain you that, because I have not the time nor the possibility to work on that. I was just guessing that this is an
problem with permissions and not with rsync itself. But a guess is a guess and I would suggest you to check the source of rsync
on why is it changing file permissions.

Plasma 5.21 is released.

3 members found this post helpful.

vte-0.62.3
https://download.gnome.org/sources/v...-0.62.3.tar.xz

Already in -current.This has been fast.

PS. Accessibility of the new Kickoff menu will mean much for blind users. Demo. espeak-ng and speech-dispatcher being already there, looks like I am going to package Orca for -current.

1 members found this post helpful.

The likely cause is GLIBC now uses lchmod() and that is causing a lot of problems in multi distros
I am awating wordback on its the cause in mariadb as well.


like I said, this shit only started when Pat upgraded GLIBC

and as for you asking to check the source as to why rsync is changing perms ? W T F .. this shows you don't understand the program at all, so I'm done here with you, you are unable to contribute anything worthwhile.

I suggest virtualbox-5.2.8, virtualbox-kernel-5.2.8 and virtualbox-5.2.8-extension-pack , (OFC those would clash with the most recent packages), but having the older packages will allow some users to virtualize XP/ReactOS and run some difficult games/software which do not run even under Wine.