Opened 6 years ago

Closed 6 years ago

#10211 closed bug (fixed)

problem 1: nothing provides haiku>=r1~alpha4_pm_hrev46279-1 needed by which-2.20-1

Reported by: tqh Owned by: bonefish
Priority: normal Milestone: R1
Component: Build System Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Getting

Resolving package dependencies ...
Encountered problems:
problem 1: nothing provides haiku>=r1~alpha4_pm_hrev46279-1 needed by which-2.20-1
  solution 1:
    - allow deinstallation of which-2.20-1

when trying to do x86 build from my github tree. I guess it is because the github tree lacks tags. Tree is at b7416a2dae69a797b70cc5252f84c79854c0d41e which corresponds to hrev46375.

Any suggestions for me to get past this until it is fixed?

Attachments (1)

tag_cache.diff (1.2 KB ) - added by augiedoggie 6 years ago.
Crude attempt at remote tags

Download all attachments as: .zip

Change History (3)

by augiedoggie, 6 years ago

Attachment: tag_cache.diff added

Crude attempt at remote tags

comment:1 by augiedoggie, 6 years ago

I use the tag_cache.diff in my own tree, but it's far from perfect. It works well enough for what I do so I haven't spent any time improving it. It should be pretty easy to add a while loop that walks backwards in the history and checks the hash of each parent until it finds a match in the cache file. This would solve most of the issues with it.

Also, it is possible to add the main haiku repository as another remote in your clone and pull from it. That will download the tags into your clone. I think git might try to push those tags to your github tree the next time though.

Last edited 6 years ago by augiedoggie (previous) (diff)

comment:2 by bonefish, 6 years ago

Resolution: fixed
Status: newclosed

Addressed in hrev46396 by introducing the HAIKU_REVISION build variable.

Note: See TracTickets for help on using tickets.