#1797 Please tag libplist for build override
Closed: Fixed None Opened 14 years ago by pbrobinson.


F9 and F10 have been tagged. You didn't say why you needed it tagged, so I'm curious why it needs tagging for F11 so close to release.

F9 and F10 have been tagged. You didn't say why you needed it tagged, so I'm curious why it needs tagging for F11 so close to release.

Its a new dep for libiphone/ifuse which now have a proper release that isn't a git based snapshot. I can't do a chain build AFAICT on F-11 branch but only devel. So to be able to build the new libiphone/ifuse releases (whether they go into F-11 final or are pushed as updates afterwards) I believe the need to be tagged into override. The new libiphone/ifuse release fix quite a few bugs, add support for new devices etc.

Its a new dep for libiphone/ifuse which now have a proper release that isn't a git based snapshot. I can't do a chain build AFAICT on F-11 branch but only devel. So to be able to build the new libiphone/ifuse releases (whether they go into F-11 final or are pushed as updates afterwards) I believe the need to be tagged into override. The new libiphone/ifuse release fix quite a few bugs, add support for new devices etc.

Thanks for the update. F11 is now tagged too.

It will take about 30 min for the build roots to update.

Thanks for the update. F11 is now tagged too.

It will take about 30 min for the build roots to update.

This is now in testing so the build override can be removed id appropriate.

This is now in testing so the build override can be removed id appropriate.

This is now in testing so the build override can be removed if appropriate.

This is now in testing so the build override can be removed if appropriate.

These will get untagged when we do buildroot cleanups.

These will get untagged when we do buildroot cleanups.

Login to comment on this ticket.

Metadata