Hello everybody,
I wrote a pull request for Package Maintainer Docs about adding a
simpler tutorial package than GNU Hello [1]. Since it is a larger change
and I have not received any reviews yet, I would like to announce this
work here, in hope of getting some feedback, before just merging
Kevin Kofler via devel kirjoitti 31.3.2024 klo 14.14:
Otto Liljalaakso wrote:
So, I would actually much prefer if package retirement automatically
added the package to fedora-obsolete-packages. Perhaps there are special
cases where that would not be a good idea - if there are some, `fedpkg
Otto Liljalaakso kirjoitti 30.3.2024 klo 13.41:
Kevin Kofler via devel kirjoitti 25.3.2024 klo 20.34:
Miroslav Suchý wrote:
I want to highlight that we have policy for removing policy
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#complete_removal
which
Kevin Kofler via devel kirjoitti 25.3.2024 klo 20.34:
Miroslav Suchý wrote:
I just upgraded my workstation to F40 and it surprised how many packages
were reported by `remove-retired-packages`. There was lots of orphaned
packages - there is nothing to do about them. But there was lot of
packages
27. maaliskuuta 2024 12.59.11 GMT+02:00 Petr Pisar
kirjoitti:
>V Tue, Mar 26, 2024 at 02:52:50PM +0100, Miroslav Suchý napsal(a):
>> I have no strong opinion how to process with the case of "MIT and BSD and
>> Bitstream Vera and OFL". I think that converting it to " MIT and BSD and
>>
I do not have the answers to your questions, but when figure out how to
properly do this, please submit an update for the docs. That section has always
looked very suspect to me.
20. maaliskuuta 2024 18.36.02 GMT+02:00 Mattia Verga via devel
kirjoitti:
>After I requested [1] Celestia project
Kevin Fenzi kirjoitti 22.2.2024 klo 1.43:
Greetings. After the outage that just completed, koji has been upgraded
to 1.34.0 plus a few patches from upstream. Some highlights:
* A patch has been added allowing us to set 'noarch_arches' on build
tags. This allows us to specify what arch builders
Miroslav Suchý kirjoitti 21.2.2024 klo 9.11:
dnf --releasever=40 --setopt=module_platform_id=platform:f40 \
--enablerepo=updates-testing \
$(rpm -q fedora-repos-modular >/dev/null && echo
--enablerepo=updates-testing-modular) \
--assumeno distro-sync
In addition to some problems that already
Dominique Martinet kirjoitti 21.2.2024 klo 15.13:
Miroslav Suchý wrote on Wed, Feb 21, 2024 at 08:11:49AM +0100:
dnf --releasever=40 --setopt=module_platform_id=platform:f40 \
--enablerepo=updates-testing \
$(rpm -q fedora-repos-modular >/dev/null && echo
--enablerepo=updates-testing-modular)
Adam Williamson kirjoitti 14.10.2023 klo 21.28:
Hey folks! I mentioned this in the blocker status summary email I just
sent, but figured it also deserved its own thread just to make sure
folks are aware of it. I've sent a ticket to FESCo:
https://pagure.io/fesco/issue/3082
proposing we bump
15. lokakuuta 2023 1.47.49 GMT+03:00 Priscila Gutierres
kirjoitti:
>Hello,
>
>I'm trying to patch pymemcache/test-requirements.txt to unpin all the build
>requirements.
>
>I created this patch using git format-patch:
>https://paste.centos.org/view/46800819
>But when trying to create a mockbuild,
Stephen Smoogen kirjoitti 7.10.2023 klo 18.30:
On Sat, 7 Oct 2023 at 10:50, stan via devel
wrote:
On Fri, 06 Oct 2023 16:05:25 -
"Michael Dawson" wrote:
> I'm trying to build
> https://gitlab.com/redhat/centos-stream/rpms/nodejs using
centpkg but
> am running
I am retiring Zim from EPEL. As specified by the retirement policy [0],
I sent notification to epel-devel already two months ago [1]. To
continue using Zim, probably the best way is to use the flatpak from
Flathub [2].
[0]:
Sandro kirjoitti 20.7.2023 klo 12.42:
On 19-07-2023 23:11, Otto Liljalaakso wrote:
Robin Lee kirjoitti 14.7.2023 klo 17.53:
I've orphaned the Zim package. It fails to build with Python 3.12 in
Rawhide.
Users can move to the flatpak on Flathub, which is also packaged by me.
Thank you
Recently, I adopted the orphaned Zim package for Fedora. The previous
maintainer had added the package to EPEL, while I am not involved with
EPEL at all. Consequently, I will not maintain the EPEL branches anymore.
From going through the EPEC documentation, it looks like the Retirement
Robin Lee kirjoitti 14.7.2023 klo 17.53:
I've orphaned the Zim package. It fails to build with Python 3.12 in Rawhide.
Users can move to the flatpak on Flathub, which is also packaged by me.
Thank you for maintaining the Zim package until now. I took it. The
build failure was easy to fix by
Peter Boy kirjoitti 25.4.2023 klo 1.29:
The increase step looks very massive. And I wonder why we should make such a
change to make games of all things work out of the box. Are games the main use
case of Fedora?
I do not think there is *the* main use case for Fedora. But certainly,
games
Aurelien Bompard kirjoitti 24.4.2023 klo 16.04:
Hi folks!
The "FMN replacement" team has finished writing the new version of our
notification system, and we are ready to deploy!
You will thus still be able to access the current FMN, and it will
keep running until F39. Due to the difference
Jakub Kadlcik kirjoitti 17.4.2023 klo 18.53:
I want to thank you all for the feedback.
Everything was already mentioned in the discussion so I am not going
to dig into details again. Just a quick summary for anyone who wants
TL;DR for this thread:
- I am not going to implement the original
Benson Muite kirjoitti 4.4.2023 klo 10.43:
Response times to pull requests can vary. Most people who want to be
packagers are submitting something new. The above would work well for
SIGS which package related software. In particular, if a package can be
adopted by a SIG, then the person
Kalev Lember kirjoitti 4.4.2023 klo 10.36:
On Tue, Apr 4, 2023 at 9:22 AM Vitaly Zaitsev via devel <
devel@lists.fedoraproject.org> wrote:
On 04/04/2023 07:52, Otto Liljalaakso wrote:
Perhaps new package requests could more often be handled in a way where
an existing packager a
Benson Muite kirjoitti 4.4.2023 klo 7.02:
May
also want to automatically track unofficial reviews by prospective
packagers, perhaps even requiring a certain number of unofficial reviews
for the sponsorship process to start.
Yes, I think that the sponsorship process should be made more rigid,
Benson Muite kirjoitti 4.4.2023 klo 7.02:
Thanks for this initiative Jakub. Automated builds on copr of packages
proposed for review has been very helpful.
I completely agree. Great work!
Benson Muite kirjoitti 4.4.2023 klo 7.02:
On 4/4/23 03:59, Jakub Kadlcik wrote:
From this thread I
Jason Tibbitts kirjoitti 3.4.2023 klo 20.09:
Miroslav Suchý writes:
In any case, what I wrote was the procedure I documented it when I set
it up. If all of that documentation was lost, then I don't know what to
say but that's not what was intended.
I drove the change that made this happen.
Miro Hrončok kirjoitti 9.3.2023 klo 13.17:
On 09. 03. 23 10:05, Otto Liljalaakso wrote:
Miro Hrončok kirjoitti 8.3.2023 klo 17.29:
However, maybe it does not work as I expected?
[python-setuptools (bundles %)]$ fedpkg prep
Not downloading already downloaded setuptools-65.5.1.tar.gz
Could
Kenneth Goldman kirjoitti 10.3.2023 klo 15.51:
Here's another "surprise for the new user" that I suggest being added.
What does the % character mean?
Sometimes it's the beginning of a section. Sometimes it's a macro.
I see now that the web page color codes the two differently,
but that's not
Kenneth Goldman kirjoitti 8.3.2023 klo 0.58:
-Original Message-
From: Jason Tibbitts
Sent: Wednesday, March 1, 2023 6:51 PM
To: Kenneth Goldman
Cc: Development discussions related to Fedora
Subject: [EXTERNAL] Re: Package Tutorial bug - missing BuildRequires gcc
Kenneth Goldman
Miro Hrončok kirjoitti 8.3.2023 klo 17.29:
On 08. 03. 23 9:29, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Mar 08, 2023 at 08:13:57AM +0100, Ondrej Nosek wrote:
Changelog (web documentation):
https://docs.pagure.org/rpkg/releases/1.66.html
https://docs.pagure.org/fedpkg/releases/1.44.html
Zbigniew Jędrzejewski-Szmek kirjoitti 8.3.2023 klo 10.29:
On Wed, Mar 08, 2023 at 08:13:57AM +0100, Ondrej Nosek wrote:
Hi all,
a new version rpkg-1.66 together with fedpkg-1.44 are released containing
both features and bugfixes.
Currently, only Fedora 37 (and Rawhide) packages are present in
Petr Pisar kirjoitti 7.3.2023 klo 16.48:
V Tue, Mar 07, 2023 at 02:19:11PM -, Betty Liu napsal(a):
I'm using CentOS stream 8 and I've downloaded the source code of yellow. In the
same directory, I've made the spec file, but after I run
fedpkg --release f28 mockbuild
I worry that f28 is
Kenneth Goldman kirjoitti 1.3.2023 klo 22.35:
https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_
GNU_Hello/
The tutorial says:
Lines which are not needed (e.g. BuildRequires and Requires) can be
commented out with the hash # for now.
However, I believe that this line
Omair Majid kirjoitti 1.3.2023 klo 5.13:
Hi,
Miroslav Suchý writes:
The list of packages needed to be converted is again here:
https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-final.txt
List by package maintainers is here
Gordon Messmer kirjoitti 23.2.2023 klo 7.34:
In case it helps: I started with the filelist in the "fedora" repo, and
a list of all of the deps printed by dnf repoquery that ended with
'()(64bit)', which should be a list of all of the ELF dependencies that
don't have versioned symbols. I
Otto Liljalaakso kirjoitti 21.2.2023 klo 11.45:
Kenneth Goldman kirjoitti 14.2.2023 klo 21.19:
https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_
GNU_Hello/
Working through the basic tutorial there:
fedpkg --release f37 mockbuild
fails with
Failed to get repository
Vít Ondruch kirjoitti 15.2.2023 klo 12.21:
Dne 14. 02. 23 v 20:19 Kenneth Goldman napsal(a):
https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_
GNU_Hello/
I wish this was update to suggest to create git repository right from
start.
BTW I think that fedpkg
Kenneth Goldman kirjoitti 14.2.2023 klo 21.19:
https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_
GNU_Hello/
Working through the basic tutorial there:
fedpkg --release f37 mockbuild
fails with
Failed to get repository name from Git url or pushurl
Failed to get ns
Kevin Fenzi kirjoitti 3.2.2023 klo 19.57:
On Fri, Feb 03, 2023 at 06:32:20PM +0100, Fabio Valentini wrote:
It's a 1:1 copy of the update "notes" from bodhi (except re-flowed to
fit into however many columns plain-text emails support).
So it's "markdown", not "awful", but sometimes it's hard to
Otto Liljalaakso kirjoitti 16.1.2023 klo 23.31:
Miro Hrončok kirjoitti 16.1.2023 klo 16.05:
On 16. 01. 23 14:57, Richard Shaw wrote:
Since `fedpkg scratch-build` bombs out with an error if you've made
local changes I propose a slight modification:
If no changes are made then it does
Vít Ondruch kirjoitti 17.1.2023 klo 13.34:
Dne 16. 01. 23 v 21:59 Otto Liljalaakso napsal(a):
Vít Ondruch kirjoitti 16.1.2023 klo 16.50:
I don't oppose to change of the defaults.
However, I am also using `fedpkg scratch-build --srpm some.rpm`. So
how would the proposed change influence
Miro Hrončok kirjoitti 16.1.2023 klo 16.05:
On 16. 01. 23 14:57, Richard Shaw wrote:
Since `fedpkg scratch-build` bombs out with an error if you've made
local changes I propose a slight modification:
If no changes are made then it does a normal scratch build for the
"does this still build
Michael J Gruber kirjoitti 16.1.2023 klo 14.46:
`--srpm` is named misleadingly, by the way, because it names the "transport of the
source" when indeed it implies a potentially different source version. That's
another reasons why removing it (the name) and making it the mode of operation for
Vít Ondruch kirjoitti 16.1.2023 klo 16.50:
I don't oppose to change of the defaults.
However, I am also using `fedpkg scratch-build --srpm some.rpm`. So how
would the proposed change influence this command?
I do not intend to change that behavior in any way.
Hello everybody,
I would like to gather different use cases for the 'fedpkg
scratch-build' command.
Currently, this is exactly the same as 'fedpkg build --scratch', meaning
that is performs a scratch build of the pushed head of the current
branch. At least in my workflow, I only do scratch
Richard Shaw kirjoitti 10.1.2023 klo 15.08:
On Tue, Jan 10, 2023 at 5:26 AM Michal Konecny wrote:
Hi everyone,
this automation is now in place and new SCM requests will be processed
automatically. If you find any issue with the automation, please report it
to toddlers issue tracker [0].
On
Neal Gompa kirjoitti 4.1.2023 klo 18.02:
On Wed, Jan 4, 2023 at 10:51 AM Rahul Sundaram wrote:
On Wed, Jan 4, 2023 at 10:38 AM Neal Gompa wrote:
On Wed, Jan 4, 2023 at 10:25 AM Chuck Anderson wrote:
Perhaps this can be modified to create a layout that matches dist-git?
Probably not,
Dan Horák kirjoitti 3.1.2023 klo 15.23:
On Tue, 3 Jan 2023 08:14:04 -0500
Stephen Smoogen wrote:
Could you please elucidate why the command that people have used for nearly
30 years and is the most documented on how to build rpms is broken? And how
people should use instead when they may be
Kalev Lember kirjoitti 3.1.2023 klo 11.19:
On Tue, Jan 3, 2023 at 10:13 AM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:
On Tue, Jan 03, 2023 at 09:32:58AM +0100, Vitaly Zaitsev via devel wrote:
On 02/01/2023 21:44, Zbigniew Jędrzejewski-Szmek wrote:
- fedpkg mockbuild
But it
Zbigniew Jędrzejewski-Szmek kirjoitti 2.1.2023 klo 22.44:
On Sun, Jan 01, 2023 at 03:10:22PM +0100, Florian Weimer wrote:
* Vitaly Zaitsev via devel:
On 30/12/2022 20:01, Ben Cotton wrote:
This document represents a proposed Change. As part of the Changes
process, proposals are publicly
Sandro kirjoitti 12.11.2022 klo 20.16:
I recently updated brewtarget to 3.0.3. In koji the build fails[1] only
for rawhide i686 arch with the following error:
/usr/bin/ld: /lib/libsndfile.so.1: undefined reference to
`mpg123_open_handle_64'
/usr/bin/ld: /lib/libsndfile.so.1: undefined
Kevin Fenzi kirjoitti 2.11.2022 klo 20.33:
On Wed, Nov 02, 2022 at 08:15:00PM +0200, Otto Liljalaakso wrote:
Would it be possible to update Koji's web UI so that it offers the signed
one for download? Is there anything going for the current behavior of
offering the unsigned one instead
Vít Ondruch kirjoitti 2.11.2022 klo 16.18:
Dne 01. 11. 22 v 18:59 Fabio Valentini napsal(a):
On Tue, Nov 1, 2022 at 6:53 PM Demi Marie Obenour
wrote:
Please push them out to testing immediately. Some, such as myself,
simply
refuse to install unsigned packages.
The packages are already
Zdenek Dohnal kirjoitti 10.10.2022 klo 11.17:
However the side tag:
f38-build-side-58658
got automatically deleted, even when it had builds connected to it
already. Documentation [1] does not mention any automatic side-tags
cleanup and its deadlines.
[1]
Miro Hrončok kirjoitti 6.10.2022 klo 2.33:
On 06. 10. 22 1:21, Otto Liljalaakso wrote:
Recently, I have run into some cases where file dependencies like
Requires: /usr/bin/foo are used.
In a recent thread on this mailing list [1],
it is mentioned that such Requires should be avoided,
because
Recently, I have run into some cases where file dependencies like
Requires: /usr/bin/foo are used.
In a recent thread on this mailing list [1],
it is mentioned that such Requires should be avoided,
because resolving file dependencies requires a large amount of memory.
On the other hand, if the
2. lokakuuta 2022 22.30.02 GMT+03:00 Till Hofmann
kirjoitti:
>I'm looking for reviews or review swaps for 3 nagios plugins:
>
>python-nagios-plugins-check_systemd
>https://bugzilla.redhat.com/show_bug.cgi?id=2082886
>
>nagios-plugins-check_ssl_cert
Alexander Ploumistos kirjoitti 28.9.2022 klo 22.13:
On Wed, Sep 28, 2022 at 8:35 PM Sébastien Le Roux
wrote:
However I wasn't able to understand how to provide a 'koji' build,
I can build the package using 'fedpkg' (local) but not sure how both
relate ...
It's in the "Scratch Builds"
Vít Ondruch kirjoitti 27.9.2022 klo 10.41:
Dne 27. 09. 22 v 9:21 Vít Ondruch napsal(a):
Dne 26. 09. 22 v 22:20 Otto Liljalaakso napsal(a):
On a different level, Sourcegraph is an effective way to query the
package sources. For instance, just querying for string 'rexml'
reveals
Robby Callicotte via devel kirjoitti 26.9.2022 klo 21.52:
I will also close https://bugzilla.redhat.com/show_bug.cgi?id=2129584 since
this is already in ruby. I simply did a search in src.fedoraproject.org and
did not see this package. Sorry bout that.
Querying the repositories can be a
Avi Alkalay kirjoitti 25.9.2022 klo 12.20:
Wow, that’s too much of a process to grasp.
Sorry if I was unclear, I did not mean that you should start the
Non-responsive package maintainer process right now. The purpose of the
process is to release the package in case its current maintainers
Avi Alkalay kirjoitti 24.9.2022 klo 14.31:
NextCloud is an amazing project that lets you run your own DropBox with
steroids.
Current F36 package is not performing well because it was not well
integrated with PHP-FPM.
I fixed it in my branch (
oli oli via devel kirjoitti 22.9.2022 klo 18.36:
Last metadata expiration check: 0:10:04 ago on Thu Sep 22 17:22:15 2022.
Error:
Problem 1: package mopidy-spotify-4.1.1-1.fc36.noarch requires
python3.10dist(mopidy) >= 3, but none of the providers can be installed
-
Ben Cotton kirjoitti 6.9.2022 klo 21.28:
https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5
== Summary ==
Make DNF5 the new default packaging tool. The change will replace DNF,
LIBDNF, and DNF-AUTOMATIC with the new DNF5 and new Libdnf5 library.
It is a second step after
18. syyskuuta 2022 13.31.24 GMT+03:00 zebo...@gmail.com kirjoitti:
>
>I haven't seen fpokorny active even when I started working on Go
>packages. Is there a way to reallocate all is Go packages to either the
>go-sig group or myself?
According to policy, they cannot be allocated to the SIG: "SIGs
18. syyskuuta 2022 1.53.45 GMT+03:00 Thomas Dickey kirjoitti:
>The release monitoring project for libXft
>(https://release-monitoring.org/project/1777/)
>doesn't appear to have noticed the release of 2.3.6 a week ago.
>Any clues on how to fix this?
When I open that link, it shows 2.3.6 as the
Tommy Nguyen kirjoitti 17.9.2022 klo 10.44:
On Sat, 2022-09-17 at 10:40 +0300, Otto Liljalaakso wrote:
Leigh Scott kirjoitti 17.9.2022 klo 10.27:
On Thu, 2022-09-15 at 22:42 +0300, Otto Liljalaakso wrote:
I found this:
https://bugzilla.rpmfusion.org/show_bug.cgi?id=6410#c1
Again, not a very
Leigh Scott kirjoitti 17.9.2022 klo 10.27:
On Thu, 2022-09-15 at 22:42 +0300, Otto Liljalaakso wrote:
I found this: https://bugzilla.rpmfusion.org/show_bug.cgi?id=6410#c1
Again, not a very friendly response. The short is that they are
currently in freeze so no action can be taken ATM.
I did
Ben Cotton kirjoitti 6.9.2022 klo 21.28:
== Summary ==
Make DNF5 the new default packaging tool. The change will replace DNF,
LIBDNF, and DNF-AUTOMATIC with the new DNF5 and new Libdnf5 library.
== Upgrade/compatibility impact ==
The new DNF5 will obsolete `dnf`, `yum`, `dnf-automatic`,
Tommy Nguyen kirjoitti 16.9.2022 klo 6.51:
On Thu, 2022-09-15 at 22:42 +0300, Otto Liljalaakso wrote:
RPM Fusion Fedora 37 repository seems to be all SHA256 already.
Thanks for doing the research. I plan on upgrading to the F37 beta
soon. Have you done so already and what are your results
Tommy Nguyen kirjoitti 15.9.2022 klo 17.40:
On Sep 15, 2022, at 10:26 AM, Otto Liljalaakso wrote:
So maybe it is just that, for Fedora 36 at least, RPM Fusion it not compatible
with the new crypto settings.
I also see the following key ids in the errors I reported in the original
message
Tommy Nguyen kirjoitti 15.9.2022 klo 16.28:
On Thu, 2022-09-15 at 16:18 +0300, Otto Liljalaakso wrote:
To test this, I did enable TEST-FEDORA39 on my system, first
installed
as Fedora 24, now running 36. For some rpm and dnf operations, I get
the
following kind of errors:
error
Ben Cotton kirjoitti 29.8.2022 klo 21.30:
https://fedoraproject.org/wiki/Changes/StrongCryptoSettings3Forewarning2
== Summary ==
Cryptographic policies will be tightened in Fedora ''38''-39,
SHA-1 signatures will no longer be trusted by default.
Fedora ''38'' will do a "jump scare",
9. syyskuuta 2022 15.58.26 GMT+03:00 Ron Olson
kirjoitti:
>
>Also, on a related note, what is the protocol for having one platform
>fail to build, while the others do? Is it okay to submit the
>Fedora/EPEL-9 builds to production, or is it more of a all-or-nothing
>kind of thing? I’ve been taking
Miro Hrončok kirjoitti 25.8.2022 klo 11.32:
Hello folks,
this is just a reminder that there is a Fedora Packager Dashboard that
you might not know about:
Go to https://packager-dashboard.fedoraproject.org/
I agree with others, this is a great and very useful service. In attempt
to make it
Jarek Prokop kirjoitti 26.8.2022 klo 17.50:
Hi,
Usually for Rawhide updates CLOSED RAWHIDE + add NVR into `fixed in
version`
if only Rawhide fixes that bug (e.g., a new software version), that
should be enough.
But it seems auto updates can take care of the tickets if you specify
the bugs
Sven Lankes kirjoitti 26.8.2022 klo 0.03:
Non-responsive maintainer policy [2]. This package has CVE bugs
open [3],
There was _one_ CVE bug and that was for the old version of xtrabackup
that is not shipped for fedora. I have just closed that bug.
The other CVEs are for EPEL builds - while
Fabio Valentini kirjoitti 25.8.2022 klo 16.01:
On Thu, Aug 25, 2022 at 2:49 PM Chris Adams wrote:
Once upon a time, Ali Erdinc Koroglu said:
Dear maintainers,
Python-sendgrid [1] will be retiring after F37, because since v6.4.1
it depends to starkbank-ecdsa [2] which we can't add to Fedora
Sandro kirjoitti 25.8.2022 klo 1.05:
On 8/24/22 23:43, Otto Liljalaakso wrote:
It looks like a commit was queuing in a pull request for a long time,
then merged after other things had happened in rawhide. Probably a more
correct Git date to use in %changelog would be the commit date instead
Sandro kirjoitti 24.8.2022 klo 23.50:
Yes, after I talked to him he became aware of the dependency between the
two packages and adopted flare as well.
AFAIK, both packages have been updated to the latest upstream release
now and built successfully. They should find their way into the
Sandro kirjoitti 24.8.2022 klo 14.33:
On 23-08-2022 16:00, Sandro wrote:
I am interested in adopting the orphaned flare package[1]. It doesn't
appear to have any complicated requirements. My local build on a recent
git clone succeeded without effort.
Hello Sandro,
Thank you for taking
Paul Wouters kirjoitti 23.8.2022 klo 3.07:
Hi,
I looked at fixing percona-xtrabackup and noticed it is staticly linking
to a bunch of libraries. These .a files are then removed in %install so
they are not shipped. It bundles a bunch of this stuff from its extra/ dir:
duktape googletest icu
Zbigniew Jędrzejewski-Szmek kirjoitti 6.8.2022 klo 20.19:
On Sat, Aug 06, 2022 at 06:29:25PM +0200, Miro Hrončok wrote:
On 06. 08. 22 16:10, Zbigniew Jędrzejewski-Szmek wrote:
Let's make %autorelease + %autochangelog the default approach in Fedora
packaging
I still haven't got around to
Welcome Jiri!
Jiri Hnidek kirjoitti 5.8.2022 klo 17.02:
I'm Red Hatter and I'm a member of the Candlepin team [1]. I develop mostly
client-tools in this project. It means that I contribute mostly to
subscription-manager [2] , virt-who [3] and other repositories related to
Red Hat Subscription
82 matches
Mail list logo
