4:15 p.m.
I have found directories in /usr that are named after architectures. So
something has changed; is it ok to delete these? One is "x86_64",
something and one is another architecture. Are these for the system
installing? They were not in f36.
B
4:31 p.m.
On 12/27/22 14:15, Bill Cunningham wrote:
I have found directories in /usr that are named after architectures.
So
something has changed; is it ok to delete these? One is "x86_64",
something and one is another architecture. Are these for the system
installing? They were not in f36.
If they are installed by the package manager, you shouldn't be deleting
them.
Do you mean "x86_64-w64-mingw32" and "i686-w64-mingw32"?
Did you install wine?
4:58 p.m.
On Tue, 27 Dec 2022 14:31:16 -0800, Samuel Sieb wrote:
If they are installed by the package manager, you shouldn't be
deleting
them.
Do you mean "x86_64-w64-mingw32" and "i686-w64-mingw32"?
Did you install wine?
Those files and directories are related to mingw not wine.
And there are tons of files/dirs in there, which get created without
belonging to any RPM package. Which is a packaging mistake somewhere.
Run "rpm -qf" on a file in those dirs to check whether it belongs into an
RPM package.
Example:
$ rpm -qf
/usr/x86_64-w64-mingw32/sys-root/mingw/share/locale/en_GB/LC_MESSAGES/gtk-vnc.mo
gvnc-1.3.0-5.fc37.x86_64
gvncpulse-1.3.0-5.fc37.x86_64
$ rpm -qf /usr/x86_64-w64-mingw32/sys-root/mingw/share/locale/en_GB/LC_MESSAGES
file /usr/x86_64-w64-mingw32/sys-root/mingw/share/locale/en_GB/LC_MESSAGES
is not owned by any package
3:30 p.m.
Thanks for the hint on "rpm -qf"! I only ever used `dnf provides`, which takes a
longer while.
4:59 p.m.
On 12/27/2022 5:31 PM, Samuel Sieb wrote:
On 12/27/22 14:15, Bill Cunningham wrote:
> I have found directories in /usr that are named after architectures.
> So something has changed; is it ok to delete these? One is "x86_64",
> something and one is another architecture. Are these for the system
> installing? They were not in f36.
If they are installed by the package manager, you shouldn't be
deleting them.
Do you mean "x86_64-w64-mingw32" and "i686-w64-mingw32"?
Did you install wine?
No. I never install a gui. Nor wine at all. I did click minimal install,
the emulator option (maybe that's it) and C development tools.
B
5:39 p.m.
On 12/27/22 14:59, Bill Cunningham wrote:
On 12/27/2022 5:31 PM, Samuel Sieb wrote:
> On 12/27/22 14:15, Bill Cunningham wrote:
>> I have found directories in /usr that are named after architectures.
>> So something has changed; is it ok to delete these? One is "x86_64",
>> something and one is another architecture. Are these for the system
>> installing? They were not in f36.
>
> If they are installed by the package manager, you shouldn't be
> deleting them.
> Do you mean "x86_64-w64-mingw32" and "i686-w64-mingw32"?
> Did you install wine?
>
No. I never install a gui. Nor wine at all. I did click minimal install,
the emulator option (maybe that's it) and C development tools.
I can't find anything like an "emulator" entry in the list of options.
The C development tools might have brought it in.
Or maybe you mean virtualization? That would likely bring in something
that uses that directory.
Actually, looking at it more, it looks like it's mostly localization
info getting packaged for mingw as well as the main localization
directory. I can't say whether or not that's a packaging bug.
5:44 p.m.
On 12/27/2022 6:39 PM, Samuel Sieb wrote:
On 12/27/22 14:59, Bill Cunningham wrote:
>
> On 12/27/2022 5:31 PM, Samuel Sieb wrote:
>> On 12/27/22 14:15, Bill Cunningham wrote:
>>> I have found directories in /usr that are named after
>>> architectures. So something has changed; is it ok to delete these?
>>> One is "x86_64", something and one is another architecture. Are
>>> these for the system installing? They were not in f36.
>>
>> If they are installed by the package manager, you shouldn't be
>> deleting them.
>> Do you mean "x86_64-w64-mingw32" and "i686-w64-mingw32"?
>> Did you install wine?
>>
> No. I never install a gui. Nor wine at all. I did click minimal
> install, the emulator option (maybe that's it) and C development tools.
I can't find anything like an "emulator" entry in the list of options.
The C development tools might have brought it in.
Or maybe you mean virtualization? That would likely bring in
something that uses that directory.
Actually, looking at it more, it looks like it's mostly localization
info getting packaged for mingw as well as the main localization
directory. I can't say whether or not that's a packaging bug.
Yes, virtualization tools. And the option for standard add on or
something like that. That is the only additional options to minimal
install I add. If I need guis I usually run of a USB stick the
Workstation ISO.
4:56 p.m.
On 27 Dec 2022, at 22:15, Bill Cunningham
<bill.cu1234(a)gmail.com> wrote:
I have found directories in /usr that are named after architectures. So something has
changed; is it ok to delete these? One is "x86_64", something and one is another
architecture. Are these for the system installing? They were not in f36.
Is it ok? No. You are likely to break something you have installed.
I would use rpm -f <filename> on some of the files in those folders
to find out what package they come from.
Then if you do not need that package see if dnf remove can safely remove it.
Barry
B
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
5 p.m.
On 12/27/2022 5:56 PM, Barry wrote:
> On 27 Dec 2022, at 22:15, Bill Cunningham <bill.cu1234(a)gmail.com> wrote:
>
> I have found directories in /usr that are named after architectures. So something
has changed; is it ok to delete these? One is "x86_64", something and one is
another architecture. Are these for the system installing? They were not in f36.
Is it ok? No. You are likely to break something you have installed.
I would use rpm -f <filename> on some of the files in those folders
to find out what package they come from.
Then if you do not need that package see if dnf remove can safely remove it.
Barry
> B
>
I didn't see any files in those directories.
5:07 p.m.
On 12/27/2022 6:00 PM, Bill Cunningham wrote:
On 12/27/2022 5:56 PM, Barry wrote:
>
>> On 27 Dec 2022, at 22:15, Bill Cunningham <bill.cu1234(a)gmail.com>
>> wrote:
>>
>> I have found directories in /usr that are named after
>> architectures. So something has changed; is it ok to delete these?
>> One is "x86_64", something and one is another architecture. Are
>> these for the system installing? They were not in f36.
> Is it ok? No. You are likely to break something you have installed.
>
> I would use rpm -f <filename> on some of the files in those folders
> to find out what package they come from.
>
> Then if you do not need that package see if dnf remove can safely
> remove it.
>
> Barry
>
>> B
>>
I didn't see any files in those directories.
Maybe it was the "C development tools". I do not use mingw or clang.
Occasionally gcc.
5:16 p.m.
On Tue, 2022-12-27 at 18:00 -0500, Bill Cunningham wrote:
On 12/27/2022 5:56 PM, Barry wrote:
>
> > On 27 Dec 2022, at 22:15, Bill Cunningham <bill.cu1234(a)gmail.com>
> > wrote:
> >
> > I have found directories in /usr that are named after
> > architectures. So something has changed; is it ok to delete
> > these? One is "x86_64", something and one is another
> > architecture. Are these for the system installing? They were not
> > in f36.
> Is it ok? No. You are likely to break something you have installed.
>
> I would use rpm -f <filename> on some of the files in those folders
> to find out what package they come from.
>
> Then if you do not need that package see if dnf remove can safely
> remove it.
>
> Barry
>
> > B
> >
I didn't see any files in those directories.
You can still use "rpm -qf <directory" to see what package installed
them.
poc
483
days inactive
486
days old
10 comments
6 participants
participants (6)
-
Barry -
Bill Cunningham -
Christian Stadelmann -
Michael Schwendt -
Patrick O'Callaghan -
Samuel Sieb