Martin Stransky kirjoitti 6.6.2022 klo 11.48:
You can get exact info by running Firefox with
MOZ_LOG="PlatformDecoderModule:5"
env variable.
Thank you, this is a good thing to know.
However, te problem was resolved by ffmpeg-free update,
so I do not need to delve into the output this
Dominik 'Rathann' Mierzejewski kirjoitti 6.6.2022 klo 11.54:
On Saturday, 04 June 2022 at 00:05, Otto Urpelainen wrote:
I have discovered that installing the ffmpeg-free package degrades Firefox
video support. Without any kind of ffmpeg installed, Firefox is able to play
all the videos I want
Michael Catanzaro kirjoitti 5.6.2022 klo 16.08:
On Sat, Jun 4 2022 at 01:05:58 AM +0300, Otto Urpelainen
wrote:
It seems clear that there is a bug somewhere, but I cannot decide,
where, hence this post to devel. Should Fedora's Firefox actually have
media.ffmpeg.enabled set to false by default
Vitaly Zaitsev via devel kirjoitti 4.6.2022 klo 14.04:
On 04/06/2022 00:05, Otto Urpelainen wrote:
It seems clear that there is a bug somewhere, but I cannot decide,
where, hence this post to devel. Should Fedora's Firefox actually have
media.ffmpeg.enabled set to false by default, because
Ben Cotton kirjoitti 2.6.2022 klo 22.27:
* Policies and guidelines:
** The Fedora packaging policy will be updated to require that new
flags added to redhat-rpm-config come with their own RPM macro.
By the proposal owners, I presume? The guidelines should also be updated
to present the new
I have discovered that installing the ffmpeg-free package degrades
Firefox video support. Without any kind of ffmpeg installed, Firefox is
able to play all the videos I want to watch. Installing RPM Fusion's
ffmpeg package does not change this. But, installing ffmpeg-free from
Fedora
Benson Muite kirjoitti 28.5.2022 klo 22.00:
Hi,
Would like to unretire ufo2ft[1][2]. The package is useful for building
font packages from source, which the Fedora font packaging policy
encourages.
That should be fine, because the it seems that back in the day, the
package was retired
Neal Gompa kirjoitti 25.5.2022 klo 16.49:
On Wed, May 25, 2022 at 9:34 AM Daniel P. Berrangé wrote:
On Wed, May 25, 2022 at 09:25:01AM -0400, Neal Gompa wrote:
On Wed, May 25, 2022 at 8:40 AM Daniel P. Berrangé wrote:
On Wed, May 25, 2022 at 10:49:15AM +0200, Miroslav Suchý wrote:
Dne
Ben Cotton kirjoitti 18.5.2022 klo 20.03:
We currently have three candidates for five open seats. This math does
not work out. You may nominate yourself (or someone else, with their
permission) before 2359 UTC on Wednesday 25 May.
On Wed, May 11, 2022 at 9:05 AM Ben Cotton wrote:
Now through
Rijul Gulati kirjoitti 15.5.2022 klo 21.05:
Hello Fedora,
My name is Rijul Gulati. I am a Software Developer from India.
I have been using Linux for a couple of years now, and would like to contribute
to the fedora project.
Welcome Rijul! Contributions are much appreciated.
I would like
Neal Gompa kirjoitti 18.5.2022 klo 19.40:
On Wed, May 18, 2022 at 12:27 PM Vít Ondruch wrote:
Dne 18. 05. 22 v 15:51 David Cantrell napsal(a):
On Wed, May 18, 2022 at 02:51:33PM +0200, Miro Hrončok wrote:
On 17. 05. 22 21:49, Miro Hrončok wrote:
On 17. 05. 22 17:06, Miroslav Suchý wrote:
Neal Gompa kirjoitti 10.5.2022 klo 2.10:
On Mon, May 9, 2022 at 7:00 PM Kevin Fenzi wrote:
On Mon, May 09, 2022 at 01:21:53PM -0400, Neal Gompa wrote:
On Mon, May 9, 2022 at 1:13 PM Kevin Fenzi wrote:
On Wed, May 04, 2022 at 09:45:55PM +0300, Otto Urpelainen wrote:
Ondrej Nosek kirjoitti
Sérgio Basto kirjoitti 8.5.2022 klo 7.52:
On Wed, 2022-05-04 at 21:45 +0300, Otto Urpelainen wrote:
Author of the patch under discussion here.
The premise was that "specfile sources" equal "sources file sources".
Since there is a request like this, that is apparently not a
Ondrej Nosek kirjoitti 4.5.2022 klo 18.01:
Hi all,
A few months ago fedpkg introduced a change which avoids downloading source
files (from dist-git) that are not used in the specfile and therefore
downloading them would be wasting of resources and time.
The original request was opened here [1]
26. huhtikuuta 2022 10.23.23 GMT+03:00 Michal Josef Spacek
kirjoitti:
>Hi all,
>
>We have asterisk FTBFS for long time
>(https://bugzilla.redhat.com/show_bug.cgi?id=1977579)
>And we have asterisk not upgraded for long time.
>We have many of CVEs in bugzilla (mostly fixed in upstream).
>
>I
Mark Bidewell kirjoitti 16.4.2022 klo 16.23:
I hope this is the right mailing list since this is about Fedora 36. I
upgraded from Fedora 35 to the Fedora 36 Alpha (at the time).
Just to clarify, there are no Alpha releases in Fedora anymore.
A new release starts out as Branched, then becomes
Germano Massullo kirjoitti 13.4.2022 klo 20.08:
Hello, in my opinion we should add to Fedora Packaging Guidelines, a
paragraph concerning GCC Toolset usage.
I recently experienced some problems in building darktable for
epel8/epel8-next due bad configuration of gcc-toolset-11 in the spec
3. huhtikuuta 2022 20.38.52 GMT+03:00 "Garry T. Williams"
kirjoitti:
>After upgrading to f36, a dnf upgrade resulted in 156 packages to
>upgrade, including swtpm. This resulted in the following errors:
>
>...
>Upgrading: swtpm-0.7.2-1.20220307git21c90c1.fc36.x86_64
>159/315
Panu Matilainen kirjoitti 1.4.2022 klo 16.26:
On 3/31/22 14:10, Daniel Walsh wrote:
On 3/31/22 02:35, Carmelo Sarta wrote:
Hello there!
I've never seen this error before
`error: Plugin selinux: hook fsm_file_prepare failed`
but I would try
`dnf reinstall container-selinux`
and maybe
`dnf
Ankur Sinha kirjoitti 31.3.2022 klo 12.51:
On Thu, Mar 31, 2022 12:16:43 +0300, Otto Urpelainen wrote:
Otto Urpelainen kirjoitti 31.3.2022 klo 11.22:
Nathanael D. Noblet kirjoitti 31.3.2022 klo 5.26:
Hello,
Just wondering if this is a bug and what to report against. I
upgraded from F35
Otto Urpelainen kirjoitti 31.3.2022 klo 11.22:
Nathanael D. Noblet kirjoitti 31.3.2022 klo 5.26:
Hello,
Just wondering if this is a bug and what to report against. I
upgraded from F35 to F36Beta last night. Today I ran `sudo dnf update`
and saw some odd output. Not sure if its a bug
Nathanael D. Noblet kirjoitti 31.3.2022 klo 5.26:
Hello,
Just wondering if this is a bug and what to report against. I
upgraded from F35 to F36Beta last night. Today I ran `sudo dnf update`
and saw some odd output. Not sure if its a bug with dnf or selinux or
the packages being installed.
Fedora-review [1] is very widely used in package review. I do not think
I have ever seen a package review where fedora-review was not used. The
last release is 0.7.6, released on 2020-11-11, i.e. more than a year
ago. Since then, there have been multiple improvements.
Would it be possible to
Michal Schorm kirjoitti 22.3.2022 klo 18.23:
Hello,
I'm trying to answer this question:
"Under which license are the contributions done to Fedora Project,
unless license is specified - and how make this clear to the
contributors (or whether we make this clear enough)".
The answer is _probably_
py0xc3 kirjoitti 13.3.2022 klo 22.12:
Hi all,
I'm Chris, I'm currently mostly active in ask.fedora and since some time
in the Docs. I just started to check out the mailing list to find out if
I can support here or at testing as well :)
I just recognized that the package nextcloud-client
Leigh Scott kirjoitti 9.3.2022 klo 18.15:
Sérgio Basto kirjoitti 7.3.2022 klo 18.17:
Crossfire and freedroidrpg are games, so "is it needed?" and
"does it
have a replacement?" are not good questions to ask. A better question
would be "does anybody want to play it?". Games do not really ever
Sérgio Basto kirjoitti 7.3.2022 klo 18.17:
Hi,
In resume glib still required for 20 packages [1],
apart of the sweet memories that some package bring to us , any of
these packages is needed ? or haven't replacement ?
Depending packages (rawhide) (20): crossfire crossfire-client crossfire-maps
Kevin Kofler via devel kirjoitti 3.3.2022 klo 0.48:
Matthew Miller wrote:
I put #introductions in the default for "watching first post" because ...
I think seeing and welcoming new people joining our community is a good
default.
Frankly, I think most existing maintainers will not be
Vít Ondruch kirjoitti 25.2.2022 klo 21.08:
Is that intentional that i get some random notifications from Discourse
or what is going on? In past month, I was notified about following topics:
* Join us for the EPEL office hours every month [Fedora] epel
* It's #FedoraShareYourScreen week
Kevin Fenzi kirjoitti 17.1.2022 klo 22.05:
On Mon, Jan 10, 2022 at 10:47:13AM -0800, Kevin Fenzi wrote:
On Mon, Jan 10, 2022 at 11:07:33AM +0100, Vít Ondruch wrote:
Just FTR, I don't think that as a sponsor, I can close the ticket and that
is a bit discouraging.
There's no way to tell
I have changed the License field of dosbox-staging from GPLv2+ to
GPLv3+. That has been the correct license from start, but previously,
licenses of this package's many bundled dependencies were not
considered. Most of the licenses are permissive or public domain-like,
but one is GPLv3+, which
Igor Raits kirjoitti 9.1.2022 klo 13.24:
Hello,
I'm interested to hear if there are any users of the `starship'
application here in Fedora that consume it from the repositories.
Please speak up if you do!
I use it, too.
___
devel mailing list --
Kevin Fenzi kirjoitti 8.1.2022 klo 1.23:
On Fri, Jan 07, 2022 at 11:43:15PM +0200, Otto Urpelainen wrote:
I can give a couple of reasons why just using the packager-sponsors tracker
always would be better. This is from the point of view of somebody who had
to find a sponsor. I am not a sponsor
Troy Dawson kirjoitti 7.1.2022 klo 16.46:
On Fri, Jan 7, 2022 at 12:20 AM Otto Urpelainen wrote:
I am the maintainer of rubygem-liquid package in Fedora. Every now and
then is receive notification that this package has been built and
updated for eln, for example [1,2].
I have been trying
Kevin Fenzi kirjoitti 7.1.2022 klo 22.05:
On Thu, Jan 06, 2022 at 10:25:50PM +, Inglis, Malcolm via devel wrote:
Well, turns out https://pagure.io/packager-sponsors isn't allowing PRs.
I've pushed to a branch here with updates and dead-link-fixes for the README:
I am the maintainer of rubygem-liquid package in Fedora. Every now and
then is receive notification that this package has been built and
updated for eln, for example [1,2].
I have been trying to understand why this package is included in eln. As
far as I can understand, it should be somehow
Vitaly Zaitsev via devel kirjoitti 6.12.2021 klo 11.01:
On 06/12/2021 03:39, Bernie Innocenti via devel wrote:
What are the current Fedora packaging guideline regarding ABI
stability of shared libraries?
The package maintainer should ask upstream to bump the soversion field
and if it is
Jerry James kirjoitti 19.11.2021 klo 23.49:
To help those who may be new to packaging, I have started documenting some
of my workflows. I have a set of web pages rooted here:
https://jamezone.org/pleasure/software/Fedora/packager/
Those pages contain walk-throughs and examples illustrating
Nico Kadel-Garcia kirjoitti 5.12.2021 klo 5.07:
I've been trying to bundle the current ansible-5.0.1 release as an RPM
for Fedora and EPEL use. Leaving aside the peculiar decisions to
replace the pypi.org "ansible" tarball with a tarball of roughly 150
modules from the "ansiblee-collections"
Blaise Pabon kirjoitti 29.11.2021 klo 18.38:
Hi Otto
On Sat, Nov 27, 2021 at 7:17 AM Otto Urpelainen wrote:
The first link is about other docs than the Package Maintainer Docs,
with some critical comments from you about the use of Antora in
docs.fp.o. The latter two are about Pagure. So
Ken Dreyer kirjoitti 30.11.2021 klo 20.56:
On Sun, Oct 10, 2021 at 2:33 PM Dan Čermák
wrote:
Maybe we can make a VM image (for KVM/qemu + VirtualBox) with a small
set of Fedora infra, including Koji+Bodhi.
How about a vagrant box or a docker-compose file :)
However, I'm a little worried
Sergio Belkin kirjoitti 29.11.2021 klo 3.32:
Hi,
I've been playing a bit with toolbox, what is it intended for?
I understand that was intended primarily for immutable OS. But
documentation says that it can be used on the Workstation edition too.
AFAIK it's only useful if you don't want to mess
Blaise Pabon kirjoitti 26.11.2021 klo 18.01:
Hi Otto,
On Thu, Nov 25, 2021 at 2:27 AM Otto Urpelainen wrote:
Blaise Pabon kirjoitti 25.11.2021 klo 5.43:
When the docs were migrated, the intent was, of course, to make them
better, not worse. If things have regressed in some way, I would
Blaise Pabon kirjoitti 25.11.2021 klo 5.43:
I appreciate all the constructive suggestions, particularly those that
acknowledge the, uh , inconsistencies in the documentation.
(snip)
Regarding the docs, yes the older ones are more useful.
IMHO, it would be better for the new docs to paint a
Ben Beasley kirjoitti 24.11.2021 klo 4.18:
For reference, the process for a stalled review in which the reviewer is
not responding can be found at
https://docs.fedoraproject.org/en-US/fesco/Package_review_policy/#reviewer_not_responding.
Also, I *think* that if you set the Bugzilla needinfo
Maxwell G via devel kirjoitti 24.11.2021 klo 2.11:
Hi,
On Tuesday, November 23, 2021 1:37:36 PM CST Steve Grubb wrote:
Hello,
I am preparing to migate a F35 system to new hardware and was sanity checking
the whole system. One thing I found was that there are a number of system
directories
Matthew Miller kirjoitti 21.11.2021 klo 20.45:
On Sun, Nov 21, 2021 at 04:27:18PM +, Tom Hughes wrote:
That page seems substantially (if not completely?) identical to the current
doc at
https://docs.fedoraproject.org/en-US/package-maintainers/How_to_Get_Sponsored_into_the_Packager_Group/
Matthew Miller kirjoitti 21.11.2021 klo 18.18:
On Sun, Nov 21, 2021 at 08:11:19AM -0500, Stephen Snow wrote:
So I am back here to ask again if I can take a package on that is
currently orphaned as per
Hello Blaise,
I am not familiar with this particular package, but about becoming a
packager and unorphaning packages in general:
Blaise Pabon kirjoitti 18.11.2021 klo 16.35:
This is my first fedora package.
(I have tried before, but not made it this far.)
Good luck, I hope you make it this
Jan K kirjoitti 13.11.2021 klo 8.55:
My name is Jan Kuparinen
I work as a DevOps engineer. In the past I have made rpm packages of a private
project, so I have some idea of packaging progress. I have also made some
contributions to various Fedora projects.
I took a look at the orphaned
Michael J. Baars kirjoitti 9.11.2021 klo 17.56:
On Tue, 2021-11-09 at 15:31 +0100, Vitaly Zaitsev via devel wrote:
On 09/11/2021 14:18, Michael J. Baars wrote:
Nothing with 'sudo dnf upgrade --advisory=FEDORA-2021-4ce970eca6' either. It keeps
saying: "Nothing to do"???
sudo dnf upgrade
Ankur Sinha kirjoitti 22.10.2021 klo 17.56:
Hi folks,
I just updated two F35 systems with updates-testing enabled and then
`klist` etc. stopped working for me. Some investigation seems to
indicate that the sssd-2.6.0 update may be involved---downgrading back
to 2.5.2 immediately fixes the issue
Maxwell G via devel kirjoitti 12.10.2021 klo 6.44:
Hi everyone,
I am Maxwell G or @gotmax23 on FAS and Github. I am relatively new to
Linux but after trying different distros, I settled on Fedora. I don't
have a lot of time between school and having chronic pain, but I'd like
to give back and
Otto Urpelainen kirjoitti 11.10.2021 klo 21.45:
Kevin Fenzi kirjoitti 10.10.2021 klo 23.49:
On Sun, Oct 10, 2021 at 02:14:06PM +0300, Otto Urpelainen wrote:
Hello,
Package Maintainer Docs currently recommend joining the package-announce
mailing list in two places [1,2], describing
Kevin Fenzi kirjoitti 10.10.2021 klo 23.49:
On Sun, Oct 10, 2021 at 02:14:06PM +0300, Otto Urpelainen wrote:
Hello,
Package Maintainer Docs currently recommend joining the package-announce
mailing list in two places [1,2], describing it as follows:
You should also consider joining
Hello,
Package Maintainer Docs currently recommend joining the package-announce
mailing list in two places [1,2], describing it as follows:
> You should also consider joining the package-announce mailing list —
> The commits mailing list gets notifications on all commits in any
> package in
Vít Ondruch kirjoitti 6.10.2021 klo 10.51:
Dne 06. 10. 21 v 7:35 Otto Urpelainen napsal(a):
Stephen Snow kirjoitti 5.10.2021 klo 15.39:
we were initially discussing that it could be useful to have some
package one can experiment with without being too much worried about
the
result.
However
Stephen Snow kirjoitti 5.10.2021 klo 15.39:
we were initially discussing that it could be useful to have some
package one can experiment with without being too much worried about
the
result.
However, discussing this back and forth, we figured that it might
also
where new coming package
Robert-André Mauchin kirjoitti 2.10.2021 klo 19.02:
On 7/19/21 18:17, Ben Cotton wrote:
https://fedoraproject.org/wiki/Changes/WirePlumber
== Summary == PipeWire currently uses a simple example session
manager. This proposal is to move to the more powerful WirePlumber
session manager.
==
Ben Cotton kirjoitti 29.9.2021 klo 23.41:
On Fri, Sep 17, 2021 at 11:05 AM Miro Hrončok wrote:
What bothers me as well is that this appears to have been communicated trough
internal channels only.
The manager of that team told me that future announcements will be
sent to the
I logged an issue about this for the Package Maintainer Docs [1].
Similarly to all other other issues in that list,
I intend to do something about this at some point,
unless somebody else beats me to it.
[1]: https://pagure.io/fedora-docs/package-maintainer-docs/issue/33
Otto
Miro Hrončok
Vít Ondruch kirjoitti 24.9.2021 klo 11.13:
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_Guide/#multiple_packages
Shouldn't it be somehow aligned with this ^^ chapter? Maybe the chapter
should be referenced at least, because it explains how to request the
side tag.
Steve Grubb kirjoitti 23.9.2021 klo 18.15:
On Wednesday, September 22, 2021 5:34:17 PM EDT Miro Hrončok wrote:
From all the scan that we've done on fullish installs in the past,
there's
only 2 others that you might run across: application/x-elc (lisp) and
application/x-java-applet.
Maybe you
Jonathan Schleifer kirjoitti 20.9.2021 klo 19.16:
Am 20.09.21 um 13:31 schrieb Miro Hrončok:
0ad ignatenkobrain, orphan, pwalter 1
weeks ago
Also, how is the flatpak package handled? I know how it works for RPM,
but flatpak's all new to me and I see there's
Vít Ondruch kirjoitti 17.9.2021 klo 13.11:
Dne 16. 09. 21 v 16:01 Michal Schorm napsal(a):
Hello,
I seek a clarification on the "Users and Groups Guidelines" [1]
chapter of the "Fedora Packaging Guidelines" [2]
Please note I want such case to be clear to newcomers too.
While I am an
Benjamin Beasley kirjoitti 8.9.2021 klo 22.07:
The license for the mpir package has been simplified from “LGPLv3+ and LGPLv2+
and (LGPLv3+ or GPLv2+) and BSD” back to the effective license of “LGPLv3+”.
See also
Solomon Peachy kirjoitti 7.9.2021 klo 23.25:
On 07.09.2021 18:14, Miroslav Suchý wrote:
System 7 (Special Snowflake Fedora 33 server)
This one is really bad, with pretty much anything relying on PHP
breaking. (Problem 1 is a local site package that just needs rebuilding
for F35's
Miroslav Suchý kirjoitti 7.9.2021 klo 19.14:
sudo dnf --releasever=35 --setopt=module_platform_id=platform:f35 \
--enablerepo=updates-testing --enablerepo=updates-testing-modular \
distro-sync
Error:
Problem 1: package arduino-core-1:1.8.13-5.fc34.noarch requires
mvn(org.ow2.asm:asm-all),
Vít Ondruch kirjoitti 31.8.2021 klo 11.43:
Dne 31. 08. 21 v 7:39 Otto Urpelainen napsal(a):
Greetings,
Some months ago, I announced [0] that I will move the package
maintainer docs from wiki to docs.fedoraproject.org.
Thx a lot.
All changes to the documentation is intended to happen
Greetings,
Some months ago, I announced [0] that I will move the package maintainer
docs from wiki to docs.fedoraproject.org. I am happy to announce that
this task is complete and the docs are public in their new location now
[1]. Hopefully, this will allow existing and new packagers to find
Hello,
New releases of rpkg and fedpkg are now in testing [1]. There are many
improvements included, of which I would like to point out "Add config
option for writing dist-git build results to a subdirectory" [2] because
it is not enabled by default, at least not yet.
The new feature is
Ankur Sinha kirjoitti 21.8.2021 klo 11.56:
For some time already, I have all of the package maintainer docs already
rewritten and improved at package-maintainer-docs [1], with the intent to
keep improving them. They remain unpublished because, despite my pleas, the
main docs page maintainers
Kevin Fenzi kirjoitti 20.8.2021 klo 22.32:
On Thu, Aug 19, 2021 at 11:03:27PM +0200, Iago Rubio wrote:
On Wed, 2021-08-18 at 08:56 -0700, Kevin Fenzi wrote:
On Wed, Aug 18, 2021 at 08:15:36PM +0700, Didik Supriadi wrote:
I think ppl now can go to
Iago Rubio kirjoitti 20.8.2021 klo 0.03:
[iago@rawhide]$ dnf repoquery --releasever rawhide --whatrequires
"rarian*"
Last metadata expiration check: 0:00:26 ago on Thu 19 Aug 2021 10:34:56
PM CEST.
alleyoop-0:0.9.8-18.fc35.x86_64
etherape-0:0.9.18-8.fc35.x86_64
Zbigniew Jędrzejewski-Szmek kirjoitti 18.8.2021 klo 12.06:
On Wed, Aug 18, 2021 at 08:57:39AM +0300, Otto Urpelainen wrote:
I have problems interpreting the following check from fedora-review:
[ ]: Description and summary sections in the package spec file
contains translations for supported
Kevin Fenzi kirjoitti 18.8.2021 klo 18.52:
On Wed, Aug 18, 2021 at 09:20:46AM -0400, Ben Beasley wrote:
It looks like the project changed version schemes at some point. The 4.02.3
release was in 2015, before 0.9.0; a long list of 4.x and 3.x releases preceded
it.
I don’t see where it got
Iago Rubio kirjoitti 18.8.2021 klo 14.32:
Hi all,
Following my messages on the "The Death of Java Packages" thread on
this list(1), Ankur Shina suggested to me to give a go at being a
package maintainer and let the mailing list know how it goes.
I hope this to be a constructive and helful way
I have problems interpreting the following check from fedora-review:
> [ ]: Description and summary sections in the package spec file
contains translations for supported Non-English languages, if available.
In one of the first package reviews I made, I recall suggesting copying
such
Sérgio Basto kirjoitti 15.8.2021 klo 3.12:
Hi,
I'm seeing the same problem, for a quick fix, we need update
/etc/mock/templates/fedora-rawhide.tpl line 12 with
config_opts['releasever'] = '36', as reference [1] ...
We need a new mock-core-configs package with configurations for "Fedora
35
Björn Persson kirjoitti 6.8.2021 klo 2.44:
Petr Menšík wrote:
No, that is the reason why I proposed it. Guidelines already state
*-filesystem packages does not have to be depended on [1]. Just one,
probably systemd or systemd-libs, should depend on it to get it
installed. All other can then
Peter Oliver kirjoitti 19.7.2021 klo 10.53:
On Mon, 19 Jul 2021, 08:08 Otto Urpelainen, wrote:
However, copr seems to understand rpmautospec.
Not really. The release will always be 1. When a package builds again,
end users won't receive the updated version.
https://pagure.io/fedora
Dan Čermák kirjoitti 18.7.2021 klo 23.38:
Otto Urpelainen writes:
Dan Čermák kirjoitti 17.7.2021 klo 23.10:
Robert-André Mauchin writes:
What is the situation wrt new packages? Should we enforce the use of
rpmautospec during reviews or is it completely optional?
I think we should
Christopher Engelhard kirjoitti 16.7.2021 klo 11.39:
Hi all,
I finally found some time to unbundle all the 3rdparty PHP/composer
libraries from the nextcloud package.
The bad news is that due to their various dependency trees, I now have a
total of 24 new packages that need reviewing.
The good
Dan Čermák kirjoitti 17.7.2021 klo 23.10:
Robert-André Mauchin writes:
What is the situation wrt new packages? Should we enforce the use of
rpmautospec during reviews or is it completely optional?
I think we should encourage the usage of rpmautospec for new packages,
provided that the
17. heinäkuuta 2021 10.23.34 GMT+03:00 Christopher Engelhard
kirjoitti:
>On 17.07.21 00:59, Miro Hrončok wrote:
>> On 16. 07. 21 19:58, Robert-André Mauchin wrote:
>>> On 6/16/21 6:03 PM, Nils Philippsen wrote:
Hi everybody,
we've scheduled the rpmautospec plugin to be deployed
Miro Hrončok kirjoitti 12.7.2021 klo 14.30:
Hello,
I happen to maintain some applications in Fedora where I am strongly
confident our users would prefer "latest and greatest" over 100 %
"stability" of the user interface and/or results.
For some of them, I've been more or less silently
Jakub Kadlcik kirjoitti 12.7.2021 klo 3.36:
Hello,
I am happy to announce that I deployed this little site
https://docs.pagure.org/fedora-sponsors/
Thank you for doing this. Finding a sponsor if one of the difficult
steps in the onboarding process, making is easier is very valuable.
Hangbin Liu kirjoitti 2.7.2021 klo 6.47:
Hi,
The dropwatch package[1] was retired as Neil Horman left RedHat[2]. But the
upstream status is still active[3]. Since this is still an useful feature
(dump the dropped packets from kernel) for networking debugging. And there
is no replace yet
Ben Cotton kirjoitti 28.6.2021 klo 19.57:
https://fedoraproject.org/wiki/Changes/LLVM-13
== Summary ==
Update all llvm sub-projects in Fedora to version 13.
== Scope ==
* Proposal owners:
** When the upstream LLVM project releases version 12.0.0-rc1 (Late
July 2021), package this and build it
Ewoud Kohl van Wijngaarden kirjoitti 21.6.2021 klo 14.50:
On Thu, Jun 17, 2021 at 09:02:12PM +0300, Otto Urpelainen wrote:
I am a bit confused about this discussion. My fedpkg does not care
about the 'sources' file or the lookaside cache at all on 'fedpkg
mockbuild'. It simply looks up
Ken Dreyer kirjoitti 17.6.2021 klo 19.04:
On Thu, Jun 17, 2021 at 8:33 AM Richard Shaw wrote:
On Thu, Jun 17, 2021 at 7:22 AM Ewoud Kohl van Wijngaarden
wrote:
To be clear: I don't want to fiddle with the sources file, hence this
email. However, I would like to at least complete a local
przemek klosowski via devel kirjoitti 17.6.2021 klo 6.21:
On 6/16/21 6:26 PM, Kevin Kofler via devel wrote:
Otto Urpelainen wrote:
Also, if the intent is to get rid of the package completely, should not
adding it to fedora-obsolete-packages be required as well?
Why? Adding working packages
Kevin Fenzi kirjoitti 16.6.2021 klo 19.57:
On Wed, Jun 16, 2021 at 03:05:59PM +0200, Ewoud Kohl van Wijngaarden wrote:
It would be my recommendation to add a third "URL" to it and that's the
fedpkg command to clone.
Yeah, might be a reasonable idea indeed. Can you file a issue at
Miro Hrončok kirjoitti 14.6.2021 klo 22.05:
On 14. 06. 21 19:50, Kevin Fenzi wrote:
It might be somehow 'fedpkg retire' doesn't handle this case?
While the wiki probably predates this feature, `fedpkg retire` will
refuse to retire a package on a stable Fedora branch and it does not
appear
Hello,
As part of the effort to move the Package Maintainer docs to
docs.fedoraproject.org [1], I have been reviewing the existing wiki
documentation. I would like to ask for insight on the following item:
Page _How to remove a package at end of life_ [2] first says that
retirement is done
I took the recently orphaned rubygem-term-ansicolor. It was behind on
releases, so I updated it from 1.4.0 to 1.7.1, the latest. In the
meantime, upstream has changed the license from GPLv2 to ASL 2.0.
___
devel mailing list --
Hans de Goede kirjoitti 1.6.2021 klo 21.02:
Hi,
On 6/1/21 6:20 PM, Vitaly Zaitsev via devel wrote:
Hello all.
doxbox-staging is trying to overwrite the regular dosbox package:
Installing:
dosbox-staging x86_64 0.76.0-2.fc34 fedora
1.4 M
replacing
Zbigniew Jędrzejewski-Szmek kirjoitti 30.5.2021 klo 12.59:
On Sat, May 29, 2021 at 09:38:46PM -0500, Brendan Early wrote:
Hi all,
Fedora Packages Static is intended to replace the old Fedora
Packages app and is now available for testing at
https://packages.stg.fedoraproject.org. Any feedback
Tim Jackson kirjoitti 25.5.2021 klo 0.58:
Since upgrading from a fairly clean F33 (installed from scratch a few
months ago) to F34 I get regular (upon each desktop login, I believe)
SELinux denials on what appears to be a dbus socket from gnome-shell and
other components:
type=AVC
I asked this question a while ago on the packaging mailing list [0], but
did not receive any replies. Let me try again here on devel with more
subscribers:
During the package review of qvge [1], the following question came up:
Are the any requirements placed on the contents of AppStream
1 - 100 of 122 matches
Mail list logo
