Bug#884142: package-contains-compiled-glib-schema may be in error

2018-01-09 Thread Chris Lamb
found 884142 2.5.67 thanks > I think it might be best to specifically check for shipping > "/usr/share/glib-2.0/schemas/gschemas.compiled" On it. Re-opening… Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-

Bug#884142: package-contains-compiled-glib-schema may be in error

2018-01-09 Thread Jonathan Carter (highvoltage)
Hi Chris On 09/01/2018 12:12, Chris Lamb wrote: > Ah, did not know that. Is there a way Lintian could tell the difference > between ones that should be compiled and which not? For the gnome-shell-extensions, they should be quite easy since they are usually located under the

Bug#884142: package-contains-compiled-glib-schema may be in error

2018-01-09 Thread Chris Lamb
Hi Jonathan, > Currently though, these are often built for gnome shell extensions at > package build time, which is a completely valid way of building these > binaries and there's really no benefit in recompiling these on the > end-user machine every time the package is installed/updated. Ah,

Bug#884142: package-contains-compiled-glib-schema may be in error

2018-01-09 Thread Jonathan Carter (highvoltage)
Hi I believe that package-contains-compiled-glib-schema may be in error. The topic of the original bug report states "test for packages shipping /usr/share/glib-2.0/schemas/gschemas.compiled", which is good, nothing should ever ship that. However, the actual lintian test checks for any file