public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/virtualbox-guest-additions] alext-upd-to-7.2.12: Update Virtualbox Guest Additions to 5.2.20, bugfix version
Date: Sun, 12 Jul 2026 20:57:45 GMT	[thread overview]
Message-ID: <178388986578.1.4327954695601821228.rpms-virtualbox-guest-additions-abda8245715e@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/virtualbox-guest-additions
Branch : alext-upd-to-7.2.12
Commit : abda8245715e3de7edac47595ab14a1a6cd78f8d
Author : Sérgio M. Basto <sergio@serjux.com>
Date   : 2018-10-20T17:19:19+01:00
Stats  : +13/-6 in 4 file(s)
URL    : https://src.fedoraproject.org/rpms/virtualbox-guest-additions/c/abda8245715e3de7edac47595ab14a1a6cd78f8d?branch=alext-upd-to-7.2.12

Log:
Update Virtualbox Guest Additions to 5.2.20, bugfix version

---
diff --git a/.gitignore b/.gitignore
index 3a2743f..5fce6d5 100644
--- a/.gitignore
+++ b/.gitignore
@@ -5,3 +5,4 @@
 /VirtualBox-5.2.14.tar.bz2
 /VirtualBox-5.2.16.tar.bz2
 /VirtualBox-5.2.18.tar.bz2
+/VirtualBox-5.2.20.tar.bz2

diff --git a/sources b/sources
index bab1776..e445f83 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (VirtualBox-5.2.18.tar.bz2) = f67c17cdd39e699e6c80af82a2c2d0c5dab073ddba2b55393740e605debb973030c48ce736ae753fc1e680845f0b62209c0f8951db08b665e9cdd83c52d5be20
+SHA512 (VirtualBox-5.2.20.tar.bz2) = ff039e487c43b584c5c5959df1622151d82f6c39101af869262f800d07e68a68005ed442112e36ebe249ed79de34c0b974bbd43e7889a5d40df2ebe7dec77a15

diff --git a/update_vbox.sh b/update_vbox.sh
index d2ed052..7bb3c0e 100755
--- a/update_vbox.sh
+++ b/update_vbox.sh
@@ -1,11 +1,14 @@
-VERSION=5.2.18
+VERSION=5.2.20
 REL=1
+RAWHIDE=30
 
 git pull
-rpmdev-bumpspec -n $VERSION -c "Update Virtualbox Guest Additions to $VERSION" virtualbox-guest-additions.spec
+rpmdev-bumpspec -n $VERSION -c "Update Virtualbox Guest Additions to $VERSION, bugfix version" virtualbox-guest-additions.spec
 spectool -g virtualbox-guest-additions.spec
-fedpkg new-sources ./VirtualBox-$VERSION.tar.bz2 && fedpkg ci -c
-git show
+fedpkg new-sources ./VirtualBox-$VERSION.tar.bz2
+fedpkg srpm && copr-cli build sergiomb/vboxfor23 virtualbox-guest-additions-$VERSION-$REL.fc$RAWHIDE.src.rpm
+echo Press enter to continue; read dummy;
+fedpkg ci -c && git show
 echo Press enter to continue; read dummy;
 fedpkg push && fedpkg build --nowait
 echo Press enter to continue; read dummy;

diff --git a/virtualbox-guest-additions.spec b/virtualbox-guest-additions.spec
index aaa1be1..f566118 100644
--- a/virtualbox-guest-additions.spec
+++ b/virtualbox-guest-additions.spec
@@ -1,7 +1,7 @@
 %global __provides_exclude_from %{_libdir}/VBoxGuestAdditions
 
 Name:       virtualbox-guest-additions
-Version:    5.2.18
+Version:    5.2.20
 Release:    1%{?dist}
 Summary:    VirtualBox Guest Additions
 License:    GPLv2 or (GPLv2 and CDDL)
@@ -198,6 +198,9 @@ getent passwd vboxadd >/dev/null || \
 
 
 %changelog
+* Sat Oct 20 2018 Sérgio Basto <sergio@serjux.com> - 5.2.20-1
+- Update Virtualbox Guest Additions to 5.2.20, bugfix version
+
 * Thu Aug 30 2018 Sérgio Basto <sergio@serjux.com> - 5.2.18-1
 - Update Virtualbox Guest Additions to 5.2.18
 

                 reply	other threads:[~2026-07-12 20:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178388986578.1.4327954695601821228.rpms-virtualbox-guest-additions-abda8245715e@fedoraproject.org \
    --to=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox