Opened 4 years ago

Closed 4 years ago

#15590 closed bug (fixed)

userguide stopped working on Haiku 64bit hrev53658

Reported by: fotisk Owned by: kallisti5
Priority: blocker Milestone: R1/beta2
Component: Build System Version: R1/Development
Keywords: userguide Cc: humdinger, PulkoMandy
Blocked By: Blocking: #15814
Platform: All

Description

Says could not find an application to load that kind of file (attached screenshot). Verified that was working in hrev53652. Seems like a very recent regression. Also, verified that html file type has WebPositive as prefered application in FileTypes. Tried to uninstall/reinstall but did not resolve the problem. It's about the English userguide version which is the only one I have installed.

Attachments (1)

screenshot2.png (1.5 MB ) - added by fotisk 4 years ago.

Download all attachments as: .zip

Change History (14)

by fotisk, 4 years ago

Attachment: screenshot2.png added

comment:1 by waddlesplash, 4 years ago

Cc: humdinger PulkoMandy added

comment:2 by humdinger, 4 years ago

I installed the 64bit beta1 release and updated to a current nightly. See the same thing.

In fact, it seems pure luck that past userguide packages worked:
The issue seems to be that the en/contents.html file in the userguide package has the type "localex-vnd.Be.locale-catalog.default" instead of "application/xhtml+xml". The filetypes of the files in the userguide are all over the place. Some have a BEOS:APP_VERSION attribute which seems to indicate to the system they were executables, though they don't have the x-bit set.

As we're read-only, the system can't correct the wrong/missing filetypes.

How to fix the build of userguide (and other, I suppose) packages to include files only after they're correctly typed?

comment:3 by waddlesplash, 4 years ago

Likely the best thing to do is to force a specific mimetype on those files during the build process, then. Or fix the mime-db so they are detected correctly, if you can.

comment:4 by diver, 4 years ago

Same here, would be nice to fix this before beta2.

comment:5 by pulkomandy, 4 years ago

Component: - GeneralBuild System
Milestone: UnscheduledR1/beta2
Owner: changed from nobody to bonefish

comment:6 by pulkomandy, 4 years ago

The rules to build the userguide do not set the mime type explicitly. I guess some sniffing is done at some point in creating the package then?

Version 0, edited 4 years ago by pulkomandy (next)

comment:7 by pulkomandy, 4 years ago

I tried mimeset on my Haiku system and it did the right thing (en/contents.html set to the correct MIME type). I looked for "locale/x-vnd.Be.locale-catalog.default" and found only one place where this is used, in DefaultCatalog.cpp. It isn't even in the MIME db source files. How does it end up being used then?

comment:8 by pulkomandy, 4 years ago

Priority: normalhigh

comment:9 by waddlesplash, 4 years ago

Priority: highblocker

comment:10 by pulkomandy, 4 years ago

Owner: changed from bonefish to kallisti5
Status: newassigned

So, the only way I see for this to happen is that there is a bug in the extended attributes emulation, and we end up using the attributes from other files when building these packages. I built the haiku_userguide_fr package locally on Haiku and I got the correct types.

What is the setup on the CI builders? Which filesystem? Is the generated directory cleaned up, including the attribute emulation storage?

comment:11 by pulkomandy, 4 years ago

From the CI build logs:

../haiku-git/configure: could not find setfattr, assuming host has no extended attributes

Can we fix that?

comment:12 by waddlesplash, 4 years ago

Blocking: 15814 added

comment:13 by waddlesplash, 4 years ago

Resolution: fixed
Status: assignedclosed

Buildbot is now fixed, so the next builds should have proper attributes.

Note: See TracTickets for help on using tickets.