Re: Rebuilding tesseract dependents in F42 for soversion change

2024-10-01 Thread Ron Yorston
Sandro Mani wrote: >This is most likely due to the fact that mingw-crt-12.0.0 for the >mingw32 and mingw64 variants was initially built with the incorrect >default msvcrt. This has since been fixed, but mingw-gcc also needs to >be rebuilt. I'm taking care of this now. Is it also necessary to r

Re: What happened to umask?

2022-05-21 Thread Ron Yorston
Owen, Thanks for explaining the situation with umask. I'd noticed the discrepancy between login/non-login shells and wondered what was going on. >It seems like we need to do one of two things: > > - Go back to the old behavior, maybe by using the usergroups option to >pam_umask and removing the

Re: F37 Change: MinGW UCRT target (Self-Contained Change proposal)

2022-02-07 Thread Ron Yorston
Marc-André Lureau wrote: >FYI, UCRT can be installed on various Windows: >https://support.microsoft.com/en-us/topic/update-for-universal-c-runtime-in-windows-c0514201-7fe6-95a3-b0a5-287930f3560c Sure, it *can* be. But that doesn't mean I can rely on my end users to be able to do that. Currently

Re: F37 Change: MinGW UCRT target (Self-Contained Change proposal)

2022-01-31 Thread Ron Yorston
Tomasz Torcz wrote: >On Mon, Jan 31, 2022 at 05:17:29PM +0100, Kevin Kofler via devel wrote: >> >> But yes, for Windows releases ≥ 95 OSR 2 and < 10 (and no, Windows version >> numbers are not anywhere near monotonic ;-) ), MSVCRT is included out of the >> box, UCRT is not. Is it really a good

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

2019-02-13 Thread Ron Yorston
Emmanuel Seyman wrote: >* Ron Yorston [13/02/2019 08:45] : >> If so, why would they do that? Why would they *not* want their package >> to be available as a regular package? It seems counterproductive for >> them to downgrade their package to this second-class status. >

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

2019-02-13 Thread Ron Yorston
Neal Gompa wrote: >Ron Yorston wrote: >> What is a "module-only" package? > >These are packages that move from the main Fedora distribution into >the addon "fedora-modular" repo that is enabled by default on Fedora >systems. What causes a package

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

2019-02-12 Thread Ron Yorston
Fabio Valentini wrote: >In the past few weeks, it has come up regularly that future >"module-only" packages are orphaned (and hence will soon be retired), >and nobody stepped up to fix this issue - especially for non-leaf >packages. I don't think fedora as a project has a solution for this >yet. W

Re: Headsup: dbus 1.12.10-1.fc29 is missing systemd dbus.service file, breaking almost everything

2018-09-03 Thread Ron Yorston
Adam Williamson wrote: >On Sun, 2018-09-02 at 08:58 -0700, stan wrote: >> On Sun, 2 Sep 2018 09:33:39 +0200 >> Andreas Tunek wrote: >> >> > There is no root acoount on a default F29 installation. Also, you >> > can't see the boot menu and I haven't been able to trigger it. >> >> Whoa! I'm not s

Re: Intent to retire: zerofree

2018-02-19 Thread Ron Yorston
Rich, Thanks for packaging zerofree. It's been great to be able to install my own software without having to build it. Richard W.M. Jones wrote: >zerofree is a package that can take an ext2 (only?) filesystem, work >out what parts of the filesystem are not used, and either zero them or >sparsify

Re: Intent to package GNOME Shell frippery

2011-06-01 Thread Ron Yorston
Hans de Goede wrote: >I plan to use 1 subpackage per extension of the frippery >extension collection, so that people can install only those >which they want without automatically getting all of >them. I'd prefer them to be in one package: they are intended to work together. I understand that mana