Re: F40 and breaking file command change

On 5/3/24 02:30, Jeffrey Walton wrote: On Fri, May 3, 2024 at 5:03 AM Michael Schwendt > wrote: On Wed, 1 May 2024 23:10:18 -0400, Jeffrey Walton wrote: > I was amazed the file project broke the command. The projects I contribute > to will move

Re: F40 and breaking file command change

On Fri, 3 May 2024 05:30:21 -0400, Jeffrey Walton wrote: > I thought the same thing about the file program. The change should have > caused a regression when running its self tests. The authors should have > known there was a problem with what they did. It's more likely that the file program's

Re: F40 and breaking file command change

On Fri, May 3, 2024 at 5:03 AM Michael Schwendt wrote: > On Wed, 1 May 2024 23:10:18 -0400, Jeffrey Walton wrote: > > > I was amazed the file project broke the command. The projects I > contribute > > to will move mountains to avoid breaking established behavior. We don't > > want to screw our

Re: F40 and breaking file command change

On Wed, 1 May 2024 23:10:18 -0400, Jeffrey Walton wrote: > I was amazed the file project broke the command. The projects I contribute > to will move mountains to avoid breaking established behavior. We don't > want to screw our users like that. In such a case, your script ought to apply some

Re: F40 and breaking file command change

George N. White III: > In some cases, "established behaviour" means text files using ASCII > character sets, which creates problems for the majority of the world, > and should be considered "broken".   In this day and age, we need to > pay attention to text encodings.   The notion of "plain

Re: F40 and breaking file command change

On Thu, May 2, 2024 at 12:11 AM Jeffrey Walton wrote: > > I was amazed the file project broke the command. The projects I contribute > to will move mountains to avoid breaking established behavior. We don't > want to screw our users like that. > In some cases, "established behaviour" means text

Re: F40 and breaking file command change

On Wed, May 01, 2024 at 11:10:18PM -0400, Jeffrey Walton wrote: ... I was amazed the file project broke the command. The projects I contribute to will move mountains to avoid breaking established behavior. We don't want to screw our users like that. As long as I've written scripts on *nix

Re: F40 and breaking file command change

On Wed, May 1, 2024 at 9:35 PM Jonathan Billings wrote: > On May 1, 2024, at 16:21, Samuel Sieb wrote: > > > > When you change software versions, it's up to you to check for any > changes. This is a really minor change. > > You’re right about that. I deal with this kind of thing each release,

Re: F40 and breaking file command change

On May 1, 2024, at 16:21, Samuel Sieb wrote: > > When you change software versions, it's up to you to check for any changes. > This is a really minor change. You’re right about that. I deal with this kind of thing each release, which is why I have a test environment that gets the alpha or

Re: F40 and breaking file command change

On 5/1/24 11:14, Jeffrey Walton wrote: The file command changed at F40, and it includes some breaking changes. One of my scripts stopped working as expected after the F40 upgrade. This part is now failing:     file "${file}.tmp" | grep -q 'CSV text' It appears the file command changed the

F40 and breaking file command change

Hi Everyone, The file command changed at F40, and it includes some breaking changes. One of my scripts stopped working as expected after the F40 upgrade. The script looks something like this: if wget -q -O "${file}.tmp" \ "${ftc_website}/DNC_Complaint_Numbers_${file}" && \ file