Opened 11 years ago

Closed 8 years ago

#10899 closed enhancement (fixed)

[HaikuDepot] add repository management functionality

Reported by: taos Owned by: stippi
Priority: normal Milestone:
Component: Applications/HaikuDepot Version:
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

Using hrev47311 x86_gcc2, updated from nightly hrev47259 via pkgman.

Due to removal of wget from haiku.hpkg in hrev47295, it's no longer possible to build Haiku (in this case hrev47313) because not all packages can be downloaded:

DownloadLocatedFile1 /GIT/haiku/generated.x86gcc2/download/openssl-1.0.0l-1-x86_gcc2.hpkg 
/bin/sh: line 6: wget: command not found

source="/GIT/haiku/generated.x86gcc2/objects/haiku/x86_gcc2/packaging/repositories/HaikuPorts-checksum"
if [ "0" = 1 ]; then
echo "ERROR: Would need to download http://packages.haiku-os.org/haikuports/master/repo/x86_gcc2/`cat $source`/packages/openssl-1.0.0l-1-x86_gcc2.hpkg, but HAIKU_NO_DOWNLOADS is set!"
exit 1
fi
wget -O "/GIT/haiku/generated.x86gcc2/download/openssl-1.0.0l-1-x86_gcc2.hpkg" http://packages.haiku-os.org/haikuports/master/repo/x86_gcc2/`cat $source`/packages/openssl-1.0.0l-1-x86_gcc2.hpkg || exit 1
touch "/GIT/haiku/generated.x86gcc2/download/openssl-1.0.0l-1-x86_gcc2.hpkg"

...failed DownloadLocatedFile1 /GIT/haiku/generated.x86gcc2/download/openssl-1.0.0l-1-x86_gcc2.hpkg ...

BUILD FAILURE:
...skipped 3 target(s)...
...updated 13 target(s)...

So far, I haven't been able to find a wget hpkg package in HaikuDepot.

Change History (14)

comment:1 by anevilyak, 11 years ago

The most likely cause there is that it's still going against the 47259 version of the repository. Does picking Tools -> Refresh Depots make a difference?

comment:2 by taos, 11 years ago

No, unfortunately not, that's the first thing I've tried. Is there a way to find out where HaikuDepot is looking for packages? I know that there is a wget package for hrev47311 available in http://packages.haiku-os.org/haikuports/master/repo/x86_gcc2/by_hrev/hrev47311/packages/.

Edit: pkgman list-repos gives "http://packages.haiku-os.org/haikuports/master/repo/x86_gcc2/5829ff2241f67813b48abcb7f514cba4834a18094827d715f0ef24b16d52f5b9"

Last edited 11 years ago by taos (previous) (diff)

comment:3 by umccullough, 11 years ago

Component: - GeneralBuild System
Owner: changed from nobody to bonefish

We should probably add wget to the default development profiles anyway...

comment:4 by umccullough, 11 years ago

Component: Build SystemKits/Package Kit

Nevermind, I see it was added to the jamfiles. Not sure what the right component is for this?

comment:5 by anevilyak, 11 years ago

I'm not sure if this would qualify as package kit or package daemon, it sounds as if the update process isn't also accordingly updating the target repository to the new revision, but I'm a bit less familiar with how that's actually handled on the back end.

comment:6 by bonefish, 11 years ago

I don't know whether HaikuDepot has any repository management functionality yet. pkgman, however, does. pkgman --help to get an overview, pkgman <command> --help for help on a specific command.

comment:7 by bonefish, 11 years ago

pkgman update does not change the configured repositories. Conversely, you should first update the repository URLs and then do the update/full-sync.

comment:8 by waddlesplash, 11 years ago

Try running:

pkgman drop-repo HaikuPorts
pkgman add-repo http://packages.haiku-os.org/haikuports/master/repo/x86_gcc2/current/

in reply to:  6 comment:9 by anevilyak, 11 years ago

Replying to bonefish:

I don't know whether HaikuDepot has any repository management functionality yet.

Currently the former's functionality is limited to being able to issue BRefreshRepositoryRequests for the list of repositories that are returned by the package roster, it doesn't yet implement any of the requisite back end to manipulate said list.

in reply to:  8 comment:10 by taos, 11 years ago

Replying to waddlesplash:

Try running:

pkgman drop-repo HaikuPorts
pkgman add-repo http://packages.haiku-os.org/haikuports/master/repo/x86_gcc2/current/

Wouldn't that mean always using the latest repository regardless of revision I'm actually using?

Instead of "current" I've added "by_hrev/hrev47313" (the revision I've upgraded to). pkgman update updates a number of packages that have been changed since the latest nightly (openssl for example).

[system] Applying changes ...
[system] Changes applied. Old activation state backed up in "state_2014-06-04_21:40:14"
[system] Cleaning up ...
[system] Done.

After system changes have been applied and, in HaikuDepot, depots have been refreshed a wget package can be found and installed.

Last edited 11 years ago by taos (previous) (diff)

comment:11 by luroh, 11 years ago

Component: Kits/Package KitApplications/HaikuDepot
Owner: changed from bonefish to stippi
Status: newassigned
Type: bugenhancement

comment:12 by waddlesplash, 11 years ago

Um, Luroh -- try rereading the ticket history please :)

comment:13 by luroh, 11 years ago

Summary: [HaikuDepot] no wget package available[HaikuDepot] add repository management functionality

waddlesplash: the ticket describes why taos was not able to find the wget package merely using HaikuDepot due to yet missing functionality. Granted, it could do with a better summary.

comment:14 by humdinger, 8 years ago

Resolution: fixed
Status: assignedclosed

There's now Brian's nice Repositories preferences. Also available from HaikuDepot's tools menu with "Manage repositories".

Note: See TracTickets for help on using tickets.