You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,8 +17,8 @@ If you need to change the llm provider and model, they are stored in the Goose c
17
17
18
18
## Build
19
19
20
-
`make build`
21
-
20
+
-`make build` This builds the goose image using an officially released goose binaries
21
+
-`make debug-build` This builds the goose image using a rebuild of goose from git. `*.patch` in `goose-container/` are applied to the git tree before building.
22
22
## Run Goose - interactively - with the MCP Atlassian server
23
23
24
24
To run goose interactively, don't be tempted to run `podman compose up` or similar, because input from your terminal might not be directed to the Goose container. Instead use:
title: "Find reverse dependencies of an RPM package"
3
-
description: "Find the reverse dependencies of the {{ package }} package. That is all packages that directly or transitively depend on the {{ package }} package."
3
+
description: "Find the reverse dependencies of the {{ package }} package for the architecture {{ arch }}. That is all packages that directly or transitively depend on the {{ package }} package on the architecture {{ arch }}."
4
4
5
5
instructions: |
6
-
A couple of rules that you must follow and useful information for you:
7
-
* Work only in a temporary directory that you can create with the mktemp tool.
8
-
* Run `dnf repoquery --whatdepends` to determine the direct reverse dependencies of a package.
9
-
* Download the RPM .repo files with curl and make sure to ignore certificates.
10
-
* Before executing any command, print the plan and the steps you want to take.
6
+
* Before starting, create a temporary directory via mktemp that will be your working directory.
7
+
* For clarity, always use full, absolute paths for file I/O.
8
+
* Run all steps in a single shell command, so they share an environment
11
9
12
10
parameters:
11
+
- key: arch
12
+
input_type: string
13
+
requirement: required
14
+
description: The architecture of the platform to look for dependencies in
13
15
- key: package
14
16
input_type: string
15
17
requirement: required
16
18
description: The package for which to find reverse dependencies.
17
19
18
20
prompt: |
19
-
You are an AI agent to list all direct and transitive reverse dependencies of a given RPM package. As input you will receive the name of the package. A reverse dependency package is one that depends on the input package. As output you must print one list for the direct reverse dependencies, and another list for the transitive reverse dependencies. Follow the below steps in the given order:
21
+
You are an AI agent to list direct and transitive reverse dependencies of a given RPM package. As input, receive the package name and target architecture. Output two files and print their contents: `{{ package }}-reverse-deps.txt` and `{{ package }}-all-reverse-deps.json`.
22
+
23
+
Steps:
24
+
25
+
1. Save the location of the `scripts/` directory for later use in an environment variable, and then create and enter a unique working directory:
description: Location of repos to query for dependencies
33
+
- key: dist_git_branch
34
+
input_type: string
35
+
requirement: required
36
+
description: Branch in the dist-git repository
37
+
- key: compose
38
+
input_type: string
39
+
requirement: required
40
+
description: Testing Farm compose to use
41
+
- key: max_results
42
+
input_type: string
43
+
requirement: optional
44
+
default: 50
45
+
description: Maximum number of reverse dependencies to fetch from repeated dnf queries
46
+
- key: number_of_requests
47
+
input_type: string
48
+
requirement: optional
49
+
default: 10
50
+
description: The number of testing farm requests to initiate
51
+
- key: change
52
+
input_type: string
53
+
requirement: optional
54
+
default: (no relevant changes)
55
+
description: A pertinent change to the package relevant to which dependent tests should run
56
+
57
+
prompt: |
58
+
You are an AI agent to find reverse dependencies of a given RPM package and test each source package. Please follow the following steps:
59
+
60
+
1. Query the first {{ max_results }} direct and indirect reverse dependencies as source packages along with their descriptions by running the helper script:
Read the source packages list from "$workingdir/{{ package }}-source-deps.txt" and read it back to me.
70
+
71
+
2. Select no more than {{ number_of_requests }} source packages from the list that would be good candidates for testing. Use your pre-existing knowledge of what the packages do, along with their provided descriptions, and how they relate to {{ package }} to make selections. Also, consider this relevant change to {{ package }} when deciding which dependents to test:
72
+
73
+
```text
74
+
{{ change }}
75
+
```
76
+
77
+
3. For each selected source package, submit a Testing Farm request using the git url {{ git_url }}/<source package>.git and the branch {{ dist_git_branch }} and the compose {{ compose }}.
78
+
79
+
4. Track the job IDs and write the results as JSON in a file called "$workingdir/jobs.json". The jobs should be of the form `[{ package: "<package-name>", jobId: "<uuid>" }, ... ]`. Use those object properties specifically and exactly, so it can be machine parsed later.
80
+
81
+
5. Finally, as a last step, Tell me where $workingdir is on the filesystem and read back "$workingdir/jobs.json" to me. Do not clean up the contents of $workingdir. They will be harvested as workflow artifacts.
0 commit comments