8:02 a.m.
I need some help/guidance on how to re-build a (normally) distributed
package (net-snmp) using the latest Fedora spec file, but using the
latest (upstream git head) version of the source; or alternatively,
the current Fedora version _with my_ fix applied.
You see, it may be some time before upstream 'officially' releases
the next version, let alone when Fedora (RHEL, SUSE, etc.) release
a new package too... but my production systems need the fixes now!
Who is the net-snmp package maintainer?
TIA
Fulko
8:08 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed 06 Mar 2013 09:02:36 AM EST, Fulko Hew wrote:
I need some help/guidance on how to re-build a (normally)
distributed package (net-snmp) using the latest Fedora spec file,
but using the latest (upstream git head) version of the source; or
alternatively, the current Fedora version _with my_ fix applied.
You see, it may be some time before upstream 'officially' releases
the next version, let alone when Fedora (RHEL, SUSE, etc.) release
a new package too... but my production systems need the fixes now!
Who is the net-snmp package maintainer?
Your best bet would be to open a Bugzilla ticket against the net-snmp
package with a pointer to the upstream patch that you want applied, as
well as reasoning why it's important to have it before the next
upstream release. Usually most packagers will apply the patch and
submit an update for Fedora.
If it's urgent for RHEL or SUSE, you should also contact your paid
support representative there and make a request that they release an
errata update.
That said, for applying a patch to the source locally, you probably
want to install the 'fedora-packager' package and then clone the
net-snmp build tree.
fedpkg clone net-snmp
Then you can modify the spec file in that directory, have it apply
your patch and then run
fedpkg local
which will build the package locally.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlE3TcgACgkQeiVVYja6o6PfxwCgoMiVpk/YbjN0pnKkbyK1RY+o
2+kAoKbucC2eE8M0dRj+jWsndiStIAMh
=GCSE
-----END PGP SIGNATURE-----
10:07 a.m.
On Wed, Mar 6, 2013 at 3:08 PM, Stephen Gallagher <sgallagh(a)redhat.com>wrote:
That said, for applying a patch to the source locally, you probably
want to install the 'fedora-packager' package and then clone the
net-snmp build tree.
fedpkg clone net-snmp
Then you can modify the spec file in that directory, have it apply
your patch and then run
fedpkg local
which will build the package locally.
I just tried fedpkg and failed duo to permissions, so I just want to
mention that you can get the SRPM from koji at
http://koji.fedoraproject.org/koji/buildinfo?buildID=386408
/Palle
10:38 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/06/2013 11:07 AM, Palle Ravn wrote:
On Wed, Mar 6, 2013 at 3:08 PM, Stephen Gallagher
<sgallagh(a)redhat.com <mailto:sgallagh@redhat.com>> wrote:
That said, for applying a patch to the source locally, you
probably want to install the 'fedora-packager' package and then
clone the net-snmp build tree.
fedpkg clone net-snmp
Then you can modify the spec file in that directory, have it apply
your patch and then run
fedpkg local
which will build the package locally.
I just tried fedpkg and failed duo to permissions, so I just want
to mention that you can get the SRPM from koji at
http://koji.fedoraproject.org/koji/buildinfo?buildID=386408
/Palle
Try
fedpkg clone --anonymous net-snmp
That's the read-only clone.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlE3cPkACgkQeiVVYja6o6Mf5gCfcz1GzT5elRHtNui1evOcj2bm
+vgAnRPZUw/OhvLPJ6AC9RN/aMnvF2kf
=Ofp9
-----END PGP SIGNATURE-----
9:26 p.m.
On 06/03/13 08:38 AM, Stephen Gallagher wrote:
> I just tried fedpkg and failed duo to permissions, so I just
want
> to mention that you can get the SRPM from koji at
> http://koji.fedoraproject.org/koji/buildinfo?buildID=386408
>
> /Palle
Try
fedpkg clone --anonymous net-snmp
To avoid going through the whole discussion we had last week _again_ -
as fedpkg is primarily a tool intended for and used by Fedora packagers,
it defaults to trying to do an authenticated check out, so you can also
commit changes to the package. People sometimes suggest making the
--anonymous option the default so it doesn't fail if you're not actually
a packager, but that would be optimising for the corner case, in this
particular situation.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
1:03 p.m.
[Sorry for the late reply; catching up on old bookmarked posts.]
On Thu, 07 Mar, 2013 at 03:26:15 GMT, Adam Williamson wrote:
To avoid going through the whole discussion we had last week _again_
-
as fedpkg is primarily a tool intended for and used by Fedora packagers,
it defaults to trying to do an authenticated check out, so you can also
commit changes to the package. People sometimes suggest making the
--anonymous option the default so it doesn't fail if you're not actually
a packager, but that would be optimising for the corner case, in this
particular situation.
fedpkg could clone anonymously and add a remote.origin.pushurl config to
the authenticated version. This is usually a plus all around since
git:// is faster than ssh:// when fetching.
See this RFE[1].
--Ben
[1]https://fedorahosted.org/fedpkg/ticket/5
4031
days inactive
4062
days old
5 comments
5 participants
participants (5)
-
Adam Williamson -
Ben Boeckel -
Fulko Hew -
Palle Ravn -
Stephen Gallagher