By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 2217

Summary:	[stdout/stderr] Warning: using regular magic file
Product:	TDE	Reporter:	Darrell <darrella>
Component:	other (any)	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bugwatch, darrella, kb9vqf, slavek.banko
Priority:	P5
Version:	R14.0.0 [Trinity]
Hardware:	Other
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Bug Depends on:
Bug Blocks:	2540

Description Darrell 2014-11-27 18:18:37 CST

Since the recent updates, I always see the following in xsession-errors:

/opt/trinity/share/config/magic/kolf.magic, 3: Warning: using regular magic file `/opt/trinity/share/config/magic/drgeo.magic'

/opt/trinity/share/config/magic/drgeo.magic, 2: Warning: using regular magic file `/opt/trinity/share/config/magic/cabri.magic'

Lots of noise in the log because of these messages.

Comment 1 Darrell 2014-11-27 18:22:14 CST

And this:

/opt/trinity/share/config/magic/drgeo.magic, 2: Warning: using regular magic file `/opt/trinity/share/config/magic/kolf.magic'

Comment 2 Timothy Pearson 2014-11-27 19:56:36 CST

They all come from libmagic; I'll have to look to see if there is a way to make it shut up about the (perfectly valid) TDE magic files.

Comment 3 Timothy Pearson 2014-11-27 20:14:49 CST

(In reply to Timothy Pearson from comment #2)
> They all come from libmagic; I'll have to look to see if there is a way to
> make it shut up about the (perfectly valid) TDE magic files.

It looks like iibmagic will continue printing the warnings as long as it is using uncompiled magic files.  While it would be simple enough to compile the magic files before installation (file -C -m <magic_file>) this would require a change to the common admin and cmake modules and is therefore not an option for R14.

After R14 release functions should be added to admin and cmake to compile and subsequently install the compiled magic files.

Comment 4 Darrell 2014-11-28 14:42:42 CST

Is there a proposed patch for this fix?

Is there a way to tag this big for R14.0.1/R14.1.1?

Comment 5 Timothy Pearson 2014-11-28 16:42:41 CST

(In reply to Darrell from comment #4)
> Is there a proposed patch for this fix?

Not yet.  Should be simple enough but as it involves changing the common admin/cmake folders it can't be part of R14.0.0.

> Is there a way to tag this big for R14.0.1/R14.1.1?

I assume you mean "bug". ;-)  I think our meta-bug idea (e.g. Bug 2014 for R14.0.0) is workable here as well; we should create another meta-bug for bugs blocking R14.0.1.

Comment 6 Darrell 2014-11-28 16:56:53 CST

If you create a global common patch I can test here. I have my build scripts configured to test global patches. The bug clutters my xsession log like crazy.

An R14.0.1 meta bug report would be nice to have before the final official packages are available.

Comment 7 Timothy Pearson 2014-11-28 17:20:31 CST

(In reply to Darrell from comment #6)
> If you create a global common patch I can test here. I have my build scripts
> configured to test global patches. The bug clutters my xsession log like
> crazy.
> 
> An R14.0.1 meta bug report would be nice to have before the final official
> packages are available.

I'll see what I can do; right now I've got my plate full with a mysterious TWin bug that just *had* to show up right after the RC2 merge window closed. :-P

Comment 8 Slávek Banko 2016-01-12 13:35:08 CST

Because magic files are only in a small number of packages, instead of solving in the common admin and cmake module, I made solutions for individual packages.