Opened 16 years ago
Closed 15 years ago
#3995 closed bug (fixed)
Nightly builds not working
| Reported by: | jahaiku | Owned by: | haiku-web |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Website | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
The last nightly build was on 2nd june.
Please can you reenable the builds and trigger a new one.
And there are no reiserfs and ntfs on the build images. Some time ago these fs where on the images. Can you please add them again?
Change History (8)
follow-up: 2 comment:1 by , 16 years ago
comment:2 by , 16 years ago
Replying to jahaiku:
Replying to jahaiku:
The last nightly build was on 2nd june.
Please can you reenable the builds and trigger a new one.
And there are no reiserfs and ntfs on the build images. Some time ago these fs where on the images. Can you please add them again?
Perhaps this is the problem:
AppendToContainerCopyFilesScript <HaikuImage>haiku.image-copy-files-dummy-optional/system/add-ons/input_server/methods
AddDirectoryToContainerCopyFilesScript <HaikuImage>system/data/licenses/-/data/system/data/licenses
InitScript1 generated/haiku.image-unzip-files
...skipped haiku.image for lack of <HaikuImage>haiku.image-copy-files...
...failed updating 1 target(s)...
...skipped 3 target(s)...
...updated 270 target(s)...
At this "jam" or "jam haiku-image" fails for me in a gcc4 linuxcrosscompile
Looks like the real problem is the failure of the ATI driver build (my other ticket) if compiled with "jam -q". So perhaps this ticket can be closed?
comment:3 by , 16 years ago
And there are no reiserfs and ntfs on the build images. Some time ago these fs where on the images. Can you please add them again? The images provided by Haiku should not contain these drivers.
follow-up: 5 comment:4 by , 16 years ago
Really? I thought those were part of the image since a long time.
comment:5 by , 16 years ago
Replying to stippi:
Really? I thought those were part of the image since a long time.
If they were, then that was a very bad mistake, since both of those filesystem drivers are GPLed, and as such we cannot enable them in a default build we distribute.
comment:6 by , 16 years ago
I don't think this is correct. First because the sources are available to anyone. Second because our license is GPL compatible anyway.
comment:7 by , 16 years ago
And third, even if the above was not true, Haiku does not depend on any of those to build/run.
comment:8 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Seems the nightly builds were fixed months ago, closing as fixed.
Replying to jahaiku:
Perhaps this is the problem:
AppendToContainerCopyFilesScript <HaikuImage>haiku.image-copy-files-dummy-optional/system/add-ons/input_server/methods
AddDirectoryToContainerCopyFilesScript <HaikuImage>system/data/licenses/-/data/system/data/licenses
InitScript1 generated/haiku.image-unzip-files
...skipped haiku.image for lack of <HaikuImage>haiku.image-copy-files...
...failed updating 1 target(s)...
...skipped 3 target(s)...
...updated 270 target(s)...
At this "jam" or "jam haiku-image" fails for me in a gcc4 linuxcrosscompile