.packit.yaml

@@ -17,7 +17,7 @@ upstream_tag_template: v{version}
 
 # The following allows us to not store our spec file in the upstream repo
 actions:
-    post-upstream-clone: "curl -LO https://src.fedoraproject.org/rpms/vagrant-sshfs/raw/main/f/vagrant-sshfs.spec"
+    post-upstream-clone: "curl -LO https://src.fedoraproject.org/rpms/vagrant-sshfs/raw/master/f/vagrant-sshfs.spec"
 
 # We are downloading (curl) to ./vagrant-sshfs.spec
 specfile_path: vagrant-sshfs.spec

README.md

@@ -5,9 +5,10 @@ You'll need a packit.yaml file created.
 ```
 $ cat <<EOF > ~/.config/packit.yaml
 debug: false
+dry_run: false
 authentication:
-#   github.com:
-#       token: XXX
+    github.com:
+        token: XXX
     pagure:
         token: XXX
         instance_url: "https://src.fedoraproject.org"
@@ -17,9 +18,9 @@ EOF
 The tokens come from:
 
 - https://src.fedoraproject.org/settings#nav-api-tab
-- https://github.com/settings/tokens (not needed for this)
+- https://github.com/settings/tokens
 
-Packit uses the `rawhide` branch. Make sure the `rawhide` branch
+Packit uses the `master` branch. Make sure the `master` branch
 in the local repo is up to date with latest upstream master. This
 can be tricky depending on if `master` tracks your fork or the
 upstream repo.
@@ -27,14 +28,14 @@ upstream repo.
 Then from this repo you can open a PR with:
 
 ```
-$ packit propose-downstream --dist-git-branch rawhide
+$ packit propose-update
 ```
 
 If that is not picking up the latest version for some reason you can
 specify the latest version with a syntax like:
 
 ```
-$ packit propose-downstream --dist-git-branch rawhide https://github.com/dustymabe/vagrant-sshfs.git 1.3.7
+$ packit propose-update https://github.com/dustymabe/vagrant-sshfs.git 1.3.4
 ```
 
 You can kick off a build with: 

vagrant-sshfs.spec

@@ -3,10 +3,9 @@
 
 Name: %{vagrant_plugin_name}
 Version: 1.3.7
-Release: 14%{?dist}
+Release: 4%{?dist}
 Summary: A Vagrant synced folder plugin that mounts folders via SSHFS
-# Automatically converted from old format: GPLv2 - review is highly recommended.
-License: GPL-2.0-only
+License: GPLv2
 URL: https://github.com/dustymabe/vagrant-sshfs
 Source0: https://rubygems.org/gems/%{vagrant_plugin_name}-%{version}.gem
 
@@ -72,36 +71,6 @@ cp -a .%{vagrant_plugin_dir}/* \
 %{vagrant_plugin_instdir}/vagrant-sshfs.gemspec
 
 %changelog
-* Fri Jul 17 2026 Fedora Release Engineering <releng@fedoraproject.org> - 1.3.7-14
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
-
-* Sat Jan 17 2026 Fedora Release Engineering <releng@fedoraproject.org> - 1.3.7-13
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_44_Mass_Rebuild
-
-* Fri Jul 25 2025 Fedora Release Engineering <releng@fedoraproject.org> - 1.3.7-12
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_43_Mass_Rebuild
-
-* Sun Jan 19 2025 Fedora Release Engineering <releng@fedoraproject.org> - 1.3.7-11
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild
-
-* Mon Jul 29 2024 Miroslav Suchý <msuchy@redhat.com> - 1.3.7-10
-- convert license to SPDX
-
-* Sat Jul 20 2024 Fedora Release Engineering <releng@fedoraproject.org> - 1.3.7-9
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_41_Mass_Rebuild
-
-* Sat Jan 27 2024 Fedora Release Engineering <releng@fedoraproject.org> - 1.3.7-8
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
-
-* Sat Jul 22 2023 Fedora Release Engineering <releng@fedoraproject.org> - 1.3.7-7
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
-
-* Sat Jan 21 2023 Fedora Release Engineering <releng@fedoraproject.org> - 1.3.7-6
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
-
-* Sat Jul 23 2022 Fedora Release Engineering <releng@fedoraproject.org> - 1.3.7-5
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
-
 * Tue Jun 21 2022 Dusty Mabe <dusty@dustymabe.com> - 1.3.7-4
 - version: bump to 1.3.7 (Dusty Mabe)
 - Gemfile: bump to latest versions of vagrant and vagrant-libvirt (Dusty Mabe)