Thanks for the tool, I have never found dnf repoquery to be user
friendly. I will keep it in mind next time I need to query the
repositories.
Very nice that you included man pages and tab completion!
Jonny
--
___
devel mailing list --
Steve Cossette wrote:
> But to be fair as well, that doesn't exist on Windows (Windows can
> reopen the programs you are working on but it doesn't save what you were
> doing)
And even that, it does not do automatically, it is an application feature to
request this through the registry.
Marc Deop i Argemí wrote:
> We are not banning nor deleting anything. We are not _supporting_ it.
You (folks) deleted the subpackages and filed a FESCo ticket requesting that
they be banned from (re)entering Fedora as separately-built packages
maintained by others.
Kevin Kofler
--
Marc Deop i Argemí wrote:
> To make it clear about this particular package:
>
> - we have _forgotten_ indeed to notify the maintainers on occasions.
> - why did we forget? because the KDE collection is close to 400 packages
> and despite our automation, we are humans and this kind of thing
This was approved at the last EPEL Steering Committee meeting.
You may go ahead with your plan.
Thank you for following the procedure.
On Mon, Jan 29, 2024 at 6:33 AM David Trudgian via epel-devel <
epel-devel@lists.fedoraproject.org> wrote:
> Dear all,
>
> Following advice from Neal elsewhere
On 2024-02-06 8:20 a.m., Roberto Ragusa wrote:
On 2/3/24 22:11, pgnd wrote:
Is there a way to see what gaps remain, which ones are being worked
on, and which ones
will be declared "not a gap - won't fix"?
I have a list of things I'm tracking. I've been reluctant to publish
it because people
On 2024-02-07 7:21 a.m., Peter Boy wrote:
I don't really want to get involved in this discussion. I don't use KDE, I
don't even use Fedora Desktop anymore. But there is one argument resp. strategy
that triggers me:
Am 07.02.2024 um 10:44 schrieb Michel Lind :
- KDE SIG likely also want
Hi everyone,
On 2/11/23 23:31, Maxwell G via devel wrote:
I've been working on a repoquerying tool called fedrq [1] that I'd
like to share with you. Here's the elevator pitch: fedrq provides a
friendly interface to query the Fedora repositories. It makes it
really easy to query across Fedora
Hi, I am in the process of updating libvpx from 1.13.1 to 1.14.0 in rawhide. This comes with a soname bump, but I am including a livpx8 compat package providing the old soname to not break the world while the rebuilds are in progress, so no rawhide breakage is expected. Some of the affected
Hi all,
the pipewalker package [0] has been updated to the latest release, v1.0. [1]
This release includes a re-licensing of the code from GPL-3.0-or-later to MIT.
pipewalker is a leaf package, so this shouldn't affect anyone.
A.FI.
[0] https://src.fedoraproject.org/rpms/pipewalker
[1]
libextractor 1.13 is coming to rawhide, which fixes the FTBFS and brings exiv2
compatibility. It also bumps the soname, but as there seem to be no Fedora
consumers, it shouldn't be an eventful update.
--
Gwyn Ciesla
she/her/hers
in your fear,
In order to preserve my energy as I maintain hugo and its multitude of
Go dependencies, I have decided to deactivate Hugo's deploy feature.
This means I can drop the need for golang-gocloud, which I will also
orphan.
The golang-gocloud package has been hard to maintain for some time. It
relies on
On Wed, 7 Feb 2024 at 09:25, Major Hayden wrote:
> On 2/7/24 07:36, Petr Menšík wrote:
> > I am interested why two DHCP clients are required inside a single tool.
> > Why it could not use NetworkManager in both times, but with some
> > different settings? Maybe alternative service? If there is
On Wednesday, 7 February 2024 13:21:15 CET Peter Boy wrote:
> If KDE Sig wants to attract users to Wayland, then the only good strategy is
> to make Wayland better than the previous way (i.e. Xorg) and promote that
> fact actively.
Does something make you think that we do not?
> Simply banning
On Sunday, 4 February 2024 03:55:42 CET Kevin Kofler via devel wrote:
> We (the KDE SIG and me) stopped being Friends when you (the KDE SIG)
> unilaterally decided to ban me from all your communication channels, a ban
> that has still not been lifted years after the alleged misconduct (on IRC
>
Oh, I see!
Well, let me get the hang of RPM Fusion right now, then I'll try to figure
out how that's done :)
I'm just trying to help the mixxx project having it working on the Fedora
ecosystem as the former packager has resigned.
On Wed, 7 Feb 2024 at 14:46, Dominik 'Rathann' Mierzejewski <
> Am 07.02.2024 um 14:40 schrieb Solomon Peachy via devel
> :
>
> you just conflated volunteer Free Software package
> maintainers with literal genocidal rapists and murders.
I am not arguing about the characteristics of maintainers or people and
actions, but about the fundamental
On Friday, 2 February 2024 00:38:56 CET Kevin Kofler via devel wrote:
> To make it clear about the situation of that particular package: The KDE SIG
> never notifies me in advance about kdepim bumps.
To make it clear about this particular package:
- we have _forgotten_ indeed to notify the
On Wednesday, 07 February 2024 at 15:31, Luis Correia wrote:
> The package already exists, under RPM Fusion free (most updated is a beta
> version)
>
> I'll at least keep it up to date with new releases
We know it exists. Neal is saying you should move it from RPM Fusion to
Fedora.
As far as I
The package already exists, under RPM Fusion free (most updated is a beta
version)
I'll at least keep it up to date with new releases
On Wed, 7 Feb 2024 at 14:25, Neal Gompa wrote:
> On Sun, Feb 4, 2024 at 6:08 PM Luis Correia
> wrote:
> >
> > Hi, I'm a long time Fedora user and used to help
On Friday, 2 February 2024 00:49:19 CET Kevin Kofler via devel wrote:
> This can be solved with communication.
>
That is dealing with the situation your packages would cause, not solving it.
( I don't mean ill will, it just a statement)
> That said, if the KDE SIG does not want to have to
On Sun, Feb 4, 2024 at 6:08 PM Luis Correia wrote:
>
> Hi, I'm a long time Fedora user and used to help develop the Ralink Wireless
> driver (rt2x00) that's been present in the kernel for a long time.
>
> I'm now entering the process of helping maintain the mixxx package over at
> rpmfusion.
>
On 2/7/24 07:36, Petr Menšík wrote:
I am interested why two DHCP clients are required inside a single tool.
Why it could not use NetworkManager in both times, but with some
different settings? Maybe alternative service? If there is missing
ability to change behaviour, it may make sense to fix
Thank you.
Leslie Satenstein
On Sunday, February 4, 2024 at 06:08:37 p.m. EST, Luis Correia
wrote:
Hi, I'm a long time Fedora user and used to help develop the Ralink Wireless
driver (rt2x00) that's been present in the kernel for a long time.
I'm now entering the process of
On Wed, 7 Feb 2024 at 14:13, Jonathan Wright via devel <
devel@lists.fedoraproject.org> wrote:
> I think you sent this to the wrong list ;)
>
> On Wed, Feb 7, 2024 at 8:03 AM Luis Correia
> wrote:
>
>> Hi,
>>
>> please excuse my probable clumsiness but I'm having issues while trying
>> to get
On Wednesday, 7 February 2024 05:07:28 CET Garry T. Williams wrote:
> I went to compose an E-mail message using kmail and its composer
> window and noticed it was broken.[*] I couldn't even find a bug
> report about this. I fear it's because many others just ignored the
> various bugs and went
I think you sent this to the wrong list ;)
On Wed, Feb 7, 2024 at 8:03 AM Luis Correia
wrote:
> Hi,
>
> please excuse my probable clumsiness but I'm having issues while trying to
> get ssh access to a package I'm now co-maintaining on RPM Fusion Free.
>
> I have followed all steps in
>
On Saturday, 3 February 2024 17:52:42 CET Adam Williamson wrote:
> Why? This is the part I don't understand. Can you explain it in more
> detail? Thanks.
If we update plasma-workspace and kwin we are likely gonna break binary
compatibility with the proposed packages.
They will need to be
Hi,
please excuse my probable clumsiness but I'm having issues while trying to
get ssh access to a package I'm now co-maintaining on RPM Fusion Free.
I have followed all steps in
https://rpmfusion.org/Contributors#Co-maintaining_an_existing_package, and
am pretty sure my ssh key was uploaded
On Wed, 2024-01-24 at 17:56 +0100, Lumír Balhar wrote:
> Hello.
>
> Today I found out an interesting difference between Koji and COPR.
> autowrap package has this in its specfile:
>
> Requires: python%{python3_pkgversion}-Cython%{?_isa}
>
> Which is incorrect for noarch package but hold on.
On Wed, Feb 07, 2024 at 01:21:15PM +0100, Peter Boy wrote:
> Unfortunately, some Fedora maintainers seem to take their cue from the
> missionaries and conquistadors of the 16th and 17th centuries and try
> fire and sword and coercion. A bad strategy in a free world.
Congratulations, you just
I am dhcpcd maintainer and okay, dhcpcd is not bad choice. But its
maintenance might fall into our team in RHEL.
I am interested why two DHCP clients are required inside a single tool.
Why it could not use NetworkManager in both times, but with some
different settings? Maybe alternative
I don't really want to get involved in this discussion. I don't use KDE, I
don't even use Fedora Desktop anymore. But there is one argument resp. strategy
that triggers me:
> Am 07.02.2024 um 10:44 schrieb Michel Lind :
>
>
> - KDE SIG likely also want people to test Wayland, so defaulting to
Hi,
I have orphaned rubygem-rest-client. It used to be dependency of Vagrant
up until version 2.2.11. Nothing depends on it now, therefore I orphaned
the package. There are not know issues with the package (except flaky
test suite) and the upstream is a bit stalled.
Vít
That’s just kmail though. I have a similar issue, but kmail is just plain
broken in plasma 6 right now.
On Tue, Feb 6, 2024 at 11:08 PM Garry T. Williams
wrote:
> On Tuesday, 30 January 2024 08:07:25 EST Richard W.M. Jones wrote:
> > On Tue, Jan 30, 2024 at 12:47:44PM +, Sérgio Basto wrote:
Michel Lind wrote:
> - KDE SIG wants to obsolete X11 packages on upgrade just once
> - Apart from the impact of that, this is actually standard packaging
> practice when subpackages are no longer offered otherwise the upgrade
> will break
> - If the obsolete indicates the NEVRA of the -x11
OLD: Fedora-Rawhide-20240206.n.0
NEW: Fedora-Rawhide-20240207.n.0
= SUMMARY =
Added images:1
Dropped images: 12
Added packages: 6
Dropped packages:1
Upgraded packages: 168
Downgraded packages: 0
Size of added packages: 424.22 KiB
Size of dropped packages
On Fri, Feb 02, 2024 at 12:58:27AM +0100, Kevin Kofler via devel wrote:
> Daniel P. Berrangé wrote:
> > The approved KDE change
> > https://fedoraproject.org/wiki/Changes/KDE_Plasma_6 indicates the intent
> > for existing Plasma X11 installs to switch to Wayland during the upgrade
> > process.
> >
Announcing the creation of a new nightly release validation test event
for Fedora 40 Rawhide 20240207.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki
Garry T. Williams wrote:
> I hope my report can be resolved before I am forced to use Wayland.
You will not be forced to use Wayland. Stay tuned.
Kevin Kofler
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an
* David Abdurachmanov:
> On Thu, Feb 1, 2024 at 3:24 PM Florian Weimer wrote:
>> Please try this:
>>
>> diff --git a/glibc.spec b/glibc.spec
>> index 6116752..e4d5e44 100644
>> --- a/glibc.spec
>> +++ b/glibc.spec
>> @@ -1571,6 +1571,10 @@ for lib in lib lib64; do
>> set +x
>>
On Thu, Feb 1, 2024 at 3:24 PM Florian Weimer wrote:
> Please try this:
>
> diff --git a/glibc.spec b/glibc.spec
> index 6116752..e4d5e44 100644
> --- a/glibc.spec
> +++ b/glibc.spec
> @@ -1571,6 +1571,10 @@ for lib in lib lib64; do
> set +x
> slbase=$(basename
42 matches
Mail list logo
