File: README-fedora.md

package info (click to toggle)
sugarjar 2.0.1-3
  • links: PTS, VCS
  • area: main
  • in suites: sid, trixie
  • size: 548 kB
  • sloc: ruby: 2,035; sh: 94; makefile: 8
file content (104 lines) | stat: -rw-r--r-- 2,461 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
# Fedora Packaging Notes

This is mostly notes to myself.

## Refs

Some links and refs useful to keep handy

* [Sugar Jar dist-git](https://src.fedoraproject.org/rpms/rubygem-sugarjar)
* [Package Maintenance Guide](https://docs.fedoraproject.org/en-US/package-maintainers/Package_Maintenance_Guide/)
* [Machines you can use](https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers)

## Prep

Start the vagrant machine, ssh to it (`vagrant up; vagrant ssh`)

*NOTE*: When provisioning the node you have to do:

```shell
SSH_AUTH_SOCK= vagrant up
```

Since part of provisioning uses an RSA key that agents will refuse to use
to sign data.

If not already checked out, check out the dist-git:

```shell
fedpkg co rubygem-sugarjar
```

Make sure you start on the 'rawhide' branch.

If already checked out, do `fedpkg pull` to get the latest.

## Do work

Make whatever changes you want on rawhide.

If you're doing a version bump you'll need to grab both new sources and replace
the old ones. First follow the directions in the spec file to build the tarball
for the test files. Then wget the gem from the URL in the spec file. Then:

```shell
fedpkg new-sources rubygem-sugarjar-<version>-specs.tar sugarjar-<version>.gem
```

## Testing

You can do a local build (`fedpkg local`) or a mock build (`fedpkg mockbuild`).

You can, alternatively, submit a koji build:

```shell
# build a SRPM
fedpkg srpm
# make sure your krb-auth'd
krb
# Submit the koji build
koji build --scratch rawhide <srpm>
```

## Committing and pushing

First, commit your change:

```shell
fedpkg commit
```

You can push directly to master if you want (`fedpkg push`), or alternatively,
make a PR by adding your remote:

```shell
git remote add fork ssh://jaymzh@pkgs.fedoraproject.org/forks/jaymzh/rpms/rubygem-sugarjar.git
```

And push to that instead (`git push fork`), and click the link to make a PR.

Once it's pushed/merged, you can create a build:

```shell
fedpkg build
```

For Rawhide, if the build succeeds, you're done.

To build for other distros, switch branches with:

```shell
fedpkg switch-branch <f35,f36,etc.>
```

And you can just merge in rawhide (`git merge rawhide`), then build.

For non-rawhide branches, after the `build`, submit the update:

```shell
fedpkg update
```

That will push it to testing. Autokarma should push it to stable after about
a week (though you can manually push it with
`bodhi updates request <update_id> stable`).