f multiple lists as CCd, then it is much more random/unpredictable
which list is fastest and thus arrives fast.
It seems this won't be a problem for the orphaned packages report
anymore, then. Since last December, they are only sent to devel-announce
which always has to be moderated m
On Wed, Aug 27, 2025 at 07:11:22AM +, Gary Buhrmaster wrote:
> On Tue, Aug 26, 2025 at 10:27 PM Maxwell G wrote:
>
> > Hi everyone,
> >
> > I don't use Gmail, but I've heard about this problem before, so it'd be
> > good to try and workaround it. Would it be helpful if I sent a separate
> > e
On Mon, Sep 01, 2025 at 03:07:33PM +0100, Richard W.M. Jones wrote:
> On Wed, Aug 27, 2025 at 07:11:22AM +, Gary Buhrmaster wrote:
> > On Tue, Aug 26, 2025 at 10:27 PM Maxwell G wrote:
> >
> > > Hi everyone,
> > >
> > > I don't use Gmail, but I've heard about this problem before, so it'd be
>
Thanks, that doesn't show if it's a hard dependency.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code
Dne 28. 08. 25 v 21:58 Leigh Scott napsal(a):
Seems I'm the almost the sole user.
https://www.pagure.io/fedora-comps/blob/main/f/comps-f44.xml.in#_487
leigh@leigh-pc:~$ dnf repoquery --whatrequires=gnome-screenshot
Updating and loading repositories:
Repositories loaded.
leigh@leigh-pc:~$ dnf
> On Thu, Aug 28, 2025 at 02:51:47PM +0200, Björn Persson wrote:
> > Anton Medvedev wrote:
> > > There was a bug so during mass branching branches for packages
> containing
> > > `+` in their names were not created.
> > > Here is the list
>
On Thu, Aug 28, 2025 at 02:51:47PM +0200, Björn Persson wrote:
> Anton Medvedev wrote:
> > There was a bug so during mass branching branches for packages containing
> > `+` in their names were not created.
> > Here is the list
> > <https://amedvede
Seems I'm the almost the sole user.
https://www.pagure.io/fedora-comps/blob/main/f/comps-f44.xml.in#_487
leigh@leigh-pc:~$ dnf repoquery --whatrequires=gnome-screenshot
Updating and loading repositories:
Repositories loaded.
leigh@leigh-pc:~$ dnf repoquery --whatrecommends=gnome-screenshot
Updat
Michael Catanzaro wrote:
> Indeed. Sorry for the confusion.
> On Thu, Aug 28 2025 at 07:39:36 PM -00:00:00, Leigh Scott
> leigh123li...@gmail.com wrote:
> > I will take gnome-screenshot if mclasen has finished with it :-}
> > Do you have some particular reason for wanting to keep it in the
> dist
Indeed. Sorry for the confusion.
On Thu, Aug 28 2025 at 07:39:36 PM -00:00:00, Leigh Scott
wrote:
I will take gnome-screenshot if mclasen has finished with it :-}
Do you have some particular reason for wanting to keep it in the
distro? If so, then OK.
--
_
Michael Catanzaro wrote:
> On Thu, Aug 28 2025 at 07:04:37 PM -00:00:00, Leigh Scott
> leigh123li...@gmail.com wrote:
> > Have you filed a change proposal for this?
> > No. Orphaning packages surely does not require a change proposal.
> Actually, we don't even have per
On Thu, Aug 28 2025 at 07:04:37 PM -00:00:00, Leigh Scott
wrote:
Have you filed a change proposal for this?
No. Orphaning packages surely does not require a change proposal.
Actually, we don't even have permission to orphan packages. Only the
package owner can actually orphan a packag
Have you filed a change proposal for this? and is the target for this F44?
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.
On Mon, 2025-08-25 at 17:11 -0500, Packaging Reports wrote:
> telepathy-logger @kde-sig, orphan, rishi 1
> weeks ago
I really shouldn't be a co-admin of telepathy-logger:
https://src.fedoraproject.org/rpms/telepathy-logger
It's been ten years since I last did anything s
Anton Medvedev wrote:
> There was a bug so during mass branching branches for packages containing
> `+` in their names were not created.
> Here is the list
> <https://amedvede.fedorapeople.org/releng_12810/result_package_list.txt> [1]
> of related packages and their mainta
Hi all,
There was a bug so during mass branching branches for packages containing
`+` in their names were not created.
Here is the list
<https://amedvede.fedorapeople.org/releng_12810/result_package_list.txt> [1]
of related packages and their maintainers.
The solution might be eith
On Wed, Aug 27 2025 at 01:52:46 PM -05:00:00, Michael Catanzaro
wrote:
Looks like gmime is also obsolete, replaced by gmime30. We should
drop that as well.
Hi,
After a second pass, I identified a few additional packages that we
will drop:
gmime, glycin-loaders, gnome-doc-utils
Looks like gmime is also obsolete, replaced by gmime30. We should drop
that as well.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs
On Wed, Aug 27 2025 at 09:57:08 AM -05:00:00, Michael Catanzaro
wrote:
almost all of the packages on this list
(A few exceptions: gnome-packagekit, gnome-nettool, and
gnome-screenshot still have non-archived git repos.)
--
___
devel mailing list
As primary maintainer of libIDL, one of the listed obsolete packages,
I’d like to take this opportunity to go ahead and let go of it, i.e.,
orphan it myself. I’ve CC’ed the individual co-maintainers on this email.
The libIDL package is used directly by ORBit2 and seamonkey; ORBit2 is
also on
On Wed, Aug 27 2025 at 12:05:00 PM +02:00:00, Michal Schorm
wrote:
Could you please check which of them are used by Cinnamon spin?
Hi,
No, but Cinnamon maintainers are welcome to check the list and own
whatever packages they need.
Just keep in mind almost all of the packages on this
On Wed, Aug 27 2025 at 11:21:29 AM -00:00:00, Artur Frenszek-Iwicki
wrote:
I haven't really worked with GTK in any capacity, but I could try my
hand
at maintaining the package (unless someone more experienced steps up).
Thanks! I don't think you actually require much experience to own this
p
> - gtk2
There's still a lot of packages using GTK2.
$ dnf repoquery --releasever=43 --disablerepo='*' --enablerepo='*-source'
--whatrequires gtk2-devel | wc -l
189
$ dnf repoquery --releasever=43 --whatrequires gtk2 | wc -l
339
I haven't really worked with GTK
On Срд, 27 жні 2025, Miro Hrončok wrote:
On 27. 08. 25 11:44, Alexander Bokovoy wrote:
On Срд, 27 жні 2025, Miro Hrončok wrote:
On 27. 08. 25 11:34, Alexander Bokovoy wrote:
On Срд, 27 жні 2025, Miro Hrončok wrote:
But here the ask was to assign a real maintainer to the
freeipa package. Presu
Using the Cinnamon spin, I see I have a number of them.
I don't know whether they are necessary.
But I have a gnome-screenshot without the gnome-shell. Installing the
gnome-shell would use another 400 MB and over 50 packages.
Could you please check which of them are used by Cinnamon spin?
On 27. 08. 25 11:44, Alexander Bokovoy wrote:
On Срд, 27 жні 2025, Miro Hrončok wrote:
On 27. 08. 25 11:34, Alexander Bokovoy wrote:
On Срд, 27 жні 2025, Miro Hrončok wrote:
But here the ask was to assign a real maintainer to the freeipa package.
Presumably sch real person would be from your t
Hi folks,
gnome-sig is doing a cleanup of its packages, which has been discussed in
https://pagure.io/fedora-workstation/issue/483
To begin, we are interested in orphaning clearly obsolete packages under
gnome-sig.
We discussed starting the orphaning process of the packages below a week
from
On Срд, 27 жні 2025, Miro Hrončok wrote:
On 27. 08. 25 11:34, Alexander Bokovoy wrote:
On Срд, 27 жні 2025, Miro Hrončok wrote:
But here the ask was to assign a real maintainer to the freeipa
package. Presumably sch real person would be from your team.
Sure. I cannot do that myself other than
On 27. 08. 25 11:34, Alexander Bokovoy wrote:
On Срд, 27 жні 2025, Miro Hrončok wrote:
But here the ask was to assign a real maintainer to the freeipa package.
Presumably sch real person would be from your team.
Sure. I cannot do that myself other than orphaning the package and
taking it again
hey should eventually receive the "Orphaned packages looking for
new maintainers" email where they are bcced.
However, gmail has a tendency to merge that email with the list
email and that usually makes such email avoid the inbox :(
It looks there is also no communication to all admins
On 27. 08. 25 8:36, Alexander Bokovoy wrote:
On Аўт, 26 жні 2025, Miro Hrončok wrote:
On 26. 08. 25 8:46, Alexander Bokovoy wrote:
The package
still belongs to 'orphan' and none of the package maintainers received a
note about it.
They should eventually receive the "Orphaned p
On Tue, Aug 26, 2025 at 10:27 PM Maxwell G wrote:
> Hi everyone,
>
> I don't use Gmail, but I've heard about this problem before, so it'd be
> good to try and workaround it. Would it be helpful if I sent a separate
> email that only had the affected maintainers BCCed and sent another one
> to the
On Аўт, 26 жні 2025, Maxwell G wrote:
Aug 26, 2025 03:24:04 Miro Hrončok :
The package
still belongs to 'orphan' and none of the package maintainers
received a
note about it.
They should eventually receive the "Orphaned packages looking for
new maintainers" email
On Аўт, 26 жні 2025, Miro Hrončok wrote:
On 26. 08. 25 8:46, Alexander Bokovoy wrote:
The package
still belongs to 'orphan' and none of the package maintainers received a
note about it.
They should eventually receive the "Orphaned packages looking for new
maintainers"
Aug 26, 2025 03:24:04 Miro Hrončok :
The package
still belongs to 'orphan' and none of the package maintainers received
a
note about it.
They should eventually receive the "Orphaned packages looking for new
maintainers" email where they are bcced.
However, gmail has
On Tue, Aug 26, 2025 at 12:30:25PM +0300, pc_magas via devel wrote:
> I feel like community has ditched any Xorg implementation.
I'm not sure what you are trying to say here...
The post you are replying to is only about availablity of X11Libre
packages in copr. Anyone can package anythi
the
Copr.)
The packages include those downstream Fedora patches to xorg-x11-*
that are not already upstream in XLibre. I will bring them up with
XLibre upstream one by one to see if we can get some of them
upstreamed, or if it may make sense to drop them from downstream
instead, but for now I
On 26. 08. 25 8:46, Alexander Bokovoy wrote:
The package
still belongs to 'orphan' and none of the package maintainers received a
note about it.
They should eventually receive the "Orphaned packages looking for new
maintainers" email where they are bcced.
However, gma
On Пан, 25 жні 2025, Maxwell G wrote:
Hi,
It looks like the freeipa and retrace-server packages have invalid
primary maintainers. freeipa has a user named ipa-maint as the main
admin and retrace-server has a user named abrt-team as the main admin.
This is a problem for three reasons:
1
Hi,
It looks like the freeipa and retrace-server packages have invalid
primary maintainers. freeipa has a user named ipa-maint as the main
admin and retrace-server has a user named abrt-team as the main admin.
This is a problem for three reasons:
1.SIGs are not allowed to be listed as a
Hi Mike,
On Monday, 2025-08-25 10:30:17 +0200, Mike FABIAN wrote:
> I can take the icu package.
Given.
Thanks
Eike
--
OpenPGP/GnuPG encrypted mail preferred in all private communication.
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A
Use LibreOffice! https:/
Hi Parag,
On Thursday, 2025-08-21 20:36:31 +0530, Parag Nemade wrote:
> You can assign me (FAS: pnemade) the woff2 package.
Done.
Thanks
Eike
--
OpenPGP/GnuPG encrypted mail preferred in all private communication.
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D
Eike Rathke さんはかきました:
> Hi,
>
> I'm retiring and won't maintain the packages icu and woff2 anymore.
> Please someone take over or I'll have to orphan them.
>
> Thanks
> Eike
I can take the icu package.
--
Mike FABIAN
睡眠不足はいい仕事の敵だ。
--
_
Hi Eike,
On Thu, Aug 21, 2025 at 5:58 PM Eike Rathke wrote:
> Hi,
>
> I'm retiring and won't maintain the packages icu and woff2 anymore.
> Please someone take over or I'll have to orphan them.
>
>
You can assign me (FAS: pnemade)
Hi,
I'm retiring and won't maintain the packages icu and woff2 anymore.
Please someone take over or I'll have to orphan them.
Thanks
Eike
--
OpenPGP/GnuPG encrypted mail preferred in all private communication.
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C
I took python-requests-pkcs12
LS
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List
I took llvm18 and clang18, needed by ghc9.12 - and also lld18.
Jens
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en
Neal Gompa wrote:
> While we in the PSWG/KDE SIG have been working on extending our
> automation to support snapshot builds in COPR/OBS, we've come across a
> few packages in the KDE stack that have been inappropriately switched
> to RPMAutoSpec.
Wow. I find it extremely rude to
is not yet available in the Copr because it does not
compile. All the other xorg-x11-drv-* drivers in Fedora have XLibre
versions in GitHub X11Libre, which are the ones provided in the Copr.)
The packages include those downstream Fedora patches to xorg-x11-* that are
not already upstream in
Hello folks,
While we in the PSWG/KDE SIG have been working on extending our
automation to support snapshot builds in COPR/OBS, we've come across a
few packages in the KDE stack that have been inappropriately switched
to RPMAutoSpec.
It is the position of the KDE SIG that packages that are
On 8/14/25 19:11, Rich Mattes wrote:
Hi all,
I unfortunately don't have the time to keep up with package maintenance
anymore. I am orphaning the packages I am the main admin for:
Sorry to see you go, but thank you for all your work.
--
Orion Poplawski
he/him/his - surely the
On 15. 08. 25 16:40, Sandro wrote:
If I take back python-diff-match-patch now, should I take care of the rebuild
for 3.14.0rc2 myself? Or will it be picked up in the next run?
The builds are pending:
https://koji.fedoraproject.org/koji/taskinfo?taskID=136068438
https://koji.fedoraproject.org/k
n. The question then boils
down to:
Who gave the package away and why?
I suppose only users or scripts with elevated access would be able to
do so.
It look like all the packages from https://pagure.io/releng/
issue/12739 are orphaned now.
That makes me think I must have rerun that action by ac
On 15. 08. 25 12:41, Miro Hrončok wrote:
On 14. 08. 25 12:02, Miro Hrončok wrote:
On 12. 08. 25 22:22, Miro Hrončok wrote:
On 12. 08. 25 13:00, Miro Hrončok wrote:
Hello Fedora packagers.
Unfortunately, we need to rebuild all Fedora 43 (and 44) packages with
Python 3.14 .pyc files. To
clearly does not work that way.
> More importantly, I lost both entries, the main admin and the commit
> access to that package. I suppose groups cannot be the main admins of
> the packages, can they?
Yes, groups cannot be the main point of c
Hi
I took
assimp
eigen3
GeographicLib
tinyobjloader
Sandro
On 15.08.25 03:11, Rich Mattes wrote:
Hi all,
I unfortunately don't have the time to keep up with package
maintenance anymore. I am orphaning the packages I am the main admin for:
abseil-cpp
assimp
bloaty
bullet
cminpack
co
On Thu, Aug 14, 2025 at 9:01 PM Rich Mattes wrote:
> Hi all,
>
> I unfortunately don't have the time to keep up with package maintenance
> anymore. I am orphaning the packages I am the main admin for:
>
I'll take mosquitto, fas: ho
On 14. 08. 25 12:02, Miro Hrončok wrote:
On 12. 08. 25 22:22, Miro Hrončok wrote:
On 12. 08. 25 13:00, Miro Hrončok wrote:
Hello Fedora packagers.
Unfortunately, we need to rebuild all Fedora 43 (and 44) packages with
Python 3.14 .pyc files. To obtain a list, use:
$ repoquery --repo
ave the package away and why?
I suppose only users or scripts with elevated access would be able to do so.
It look like all the packages from https://pagure.io/releng/issue/12739 are
orphaned now.
That makes me think I must have rerun that action by accident. I still don't
know how or when,
e only users or scripts with elevated access would be able to do so.
It look like all the packages from https://pagure.io/releng/issue/12739 are
orphaned now.
That makes me think I must have rerun that action by accident. I still don't
know how or when, but if it was indeed me, I sincerely apol
On 15. 08. 25 7:26, Milan Crha wrote:
No idea how you found that ticket,
I happened to be the one who processed it.
--
Miro Hrončok
--
Phone: +420777974800
Fedora Matrix: mhroncok
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubsc
On 14-08-2025 22:27, Miro Hrončok wrote:
On 14. 08. 25 21:35, Sandro wrote:
Unlikely. The reason for orphaning is cleared (or should be) when a
package is picked up by another user. At least that's my experience
using the UI. The API may behave differently.
I think the reason is hidden from t
On Thu, Aug 14 2025 at 21:11:21 -04:00:00, Rich Mattes
wrote:
bullet
I can take bullet unless someone else wants it.
-Tomi
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.o
s to that package. I suppose groups cannot be the main admins of
the packages, can they?
I took bijiben (again), even I do not intend to be the main admin for
it. I had commit rights only to be able to rebuild it in case
evolution-data-server bumps its soname version. I'd like to give away
th
On Thu, 2025-08-14 at 19:32 +0200, Miro Hrončok wrote:
> Both orphaned via https://pagure.io/releng/issue/12858
Hi,
aha, I see, that makes sense now.
No idea how you found that ticket, but the Filter->Search in pagure is
dull and doesn't find that ticket when searching for the
gtk
Hi all,
I unfortunately don't have the time to keep up with package maintenance
anymore. I am orphaning the packages I am the main admin for:
abseil-cpp
assimp
bloaty
bullet
cminpack
console-bridge
cutecom
eigen3
fast-cdr
fcl
flann
flexiport
gazebo
gearbox
GeographicLib
hokuyoaist
ignition-
On 14. 08. 25 21:35, Sandro wrote:
Unlikely. The reason for orphaning is cleared (or should be) when a package is
picked up by another user. At least that's my experience using the UI. The API
may behave differently.
I think the reason is hidden from the UI but stays in the DB. Assigning the
On 8/13/25 7:46 PM, maxwell--- via devel-announce wrote:
Report started at 2025-08-14 02:00:41 UTC
I'm taking this one and fixing the build issue.
strongswandcavalca, orphan, pemensik, 0 weeks ago
salimma
--
On 14-08-2025 17:47, Miro Hrončok wrote:
On 14. 08. 25 17:25, Sandro wrote:
On 14-08-2025 04:46, maxw...@gtmx.me wrote:
python-diff-match-patch orphan 0
weeks ago
Could someone help me understand how python-diff-match-patch ended up
orphaned? The bug refe
On 14. 08. 25 18:59, Milan Crha wrote:
Hi,
where does one get the reasons behind the orphanage, or the history of
admin/ownership changes in general, please?
No idea.
I think bijiben and gtksourceview4 are suspicious and maybe orphaned in
error.
Both orphaned via https://pagure.io/r
On Thu, 2025-08-14 at 17:47 +0200, Miro Hrončok wrote:
> Looks like it was given to the orphan user now and the previous
> reason stayed there.
>
> No idea what happened here, or who orphaned it this time :/
Hi,
where does one get the reasons behind the orphanage, or the history of
admin/
On 14. 08. 25 17:25, Sandro wrote:
On 14-08-2025 04:46, maxw...@gtmx.me wrote:
python-diff-match-patch orphan 0 weeks ago
Could someone help me understand how python-diff-match-patch ended up orphaned?
The bug referenced in the orphan message [1] is closed
On 14-08-2025 04:46, maxw...@gtmx.me wrote:
python-diff-match-patch orphan 0 weeks ago
Could someone help me understand how python-diff-match-patch ended up
orphaned? The bug referenced in the orphan message [1] is closed and
there are no other open bugs f
On 12. 08. 25 22:22, Miro Hrončok wrote:
On 12. 08. 25 13:00, Miro Hrončok wrote:
Hello Fedora packagers.
Unfortunately, we need to rebuild all Fedora 43 (and 44) packages with Python
3.14 .pyc files. To obtain a list, use:
$ repoquery --repo=rawhide --refresh -f *.cpython-314.pyc
On 12. 08. 25 13:00, Miro Hrončok wrote:
Hello Fedora packagers.
Unfortunately, we need to rebuild all Fedora 43 (and 44) packages with Python
3.14 .pyc files. To obtain a list, use:
$ repoquery --repo=rawhide --refresh -f *.cpython-314.pyc --source
(3931 unique packages)
This is
Hello Fedora packagers.
Unfortunately, we need to rebuild all Fedora 43 (and 44) packages with Python
3.14 .pyc files. To obtain a list, use:
$ repoquery --repo=rawhide --refresh -f *.cpython-314.pyc --source
(3931 unique packages)
This is needed because Python 3.14 just bumped the pyc
I like to work in the garden but my sister hates it. She prefers to read. She
reads in the morning, in the afternoon and at night https://gannelectricks.com
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel
://fedoraproject.org/wiki/Changes/Hardlink_identical_files_in_packages_by_default
Discussion thread -
https://discussion.fedoraproject.org/t/f43-change-proposal-hardlink-identical-files-in-packages-by-default-self-contained/160769
This is a proposed Change for Fedora Linux.
This document represents a proposed
> wrote:
> >>>
> >>> Wiki -
> >>> https://fedoraproject.org/wiki/Changes/Hardlink_identical_files_in_packages_by_default
> >>> Discussion thread -
> >>> https://discussion.fedoraproject.org/t/f43-change-proposal-hardlink-identical-files-in-packages-by-
://discussion.fedoraproject.org/t/f43-change-proposal-hardlink-identical-files-in-packages-by-default-self-contained/160769
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
Dear maintainers.
Based on the current fail to build from source policy, the following packages
should be retired from Fedora 43 approximately one week before branching,
i.e. tomorrow.
Due to delay in process, the retirement will happen on Monday, 2025-08-11.
5 weekly reminders are required
Hello team,
The following packages need review as they are part of new dependencies
for Blender 4.5 and above:
- clipper2:
bugzilla.redhat.com
2386078 – Review Request: clipper2 - Polygon Clipping and Offsetting
Library <#>
🔗 https://bugzilla.redhat.com/show_bug.cgi?id=2386078
On neděle 27. července 2025 16:32:01, středoevropský letní čas Fabio Valentini
wrote:
> On Sat, Jul 26, 2025 at 10:37 AM Pavel Raiskup wrote:
> >
> > I'd rather we show extra care towards Fedora developers who are still
> > using Fedora, if there are any. If we make Fedora development overly
> >
10 AM maxwell--- via devel-announce
wrote:
Report started at 2025-04-20 22:00:03 UTC
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you
know for sure
that the package should be retired, please do so now
03 UTC
>
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for
> sure
> that the package should be retired, please do so now with a proper reason:
> https://fedoraproject.org/wiki/How_to_remove_a_package
On 29. 07. 25 6:36, Maxwell G wrote:
Hi,
On 7/28/25 2:52 AM, Miro Hrončok wrote:
golang-* packages excluded via https://pagure.io/fesco/issue/3447
Looking at the list of packages from last week's notification, I see the
following packages are considered fesco_3447_not_exempt in
On 7/28/25 10:36 PM, maxwell--- via devel-announce wrote:
nng orphan 3 weeks ago
Taken, because KiCad needs it.
Steve
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsu
On 29/07/2025 04:36, maxwell--- via devel-announce wrote:
python-geojsonorphan 3 weeks ago
I took this one
Christiano Anderson
Mastodon: https://chaos.social/@canderson
https://christiano.dev
--
___
dev
Hi,
On 7/28/25 2:52 AM, Miro Hrončok wrote:
golang-* packages excluded via https://pagure.io/fesco/issue/3447
Looking at the list of packages from last week's notification, I see the
following packages are considered fesco_3447_not_exempt in
https://gitlab.com/fedora/sigs/go/package
Hi,
Apologies if you received this twice—my email client got messed up.
On 7/28/25 2:52 AM, Miro Hrončok wrote:
golang-* packages excluded via https://pagure.io/fesco/issue/3447
Looking at the list from last week, I see the following packages that
are listed in fesco_3447_not_exempt in
Hi everyone,
I have some updates about the orphaned packages process. Feedback is
always welcome!
=== IMPORTANT REMINDER ===
Please make sure to pay special attention to the orphaned packages
report [1]. There are many more packages there than usual in part due to
nonresponsive maintainer
> > Discussion thread -
> > https://discussion.fedoraproject.org/t/f43-change-proposal-hardlink-identical-files-in-packages-by-default-self-contained/160769
> >
> > This is a proposed Change for Fedora Linux.
> > This document represents a proposed Change. As part of the Changes
&g
> On Jul 24, 2025, at 7:02 PM, Aoife Moloney via devel-announce
> wrote:
>
> Wiki -
> https://fedoraproject.org/wiki/Changes/Hardlink_identical_files_in_packages_by_default
> Discussion thread -
> https://discussion.fedoraproject.org/t/f43-change-proposal-hardlink-identi
On Mon, Jul 28, 2025 at 07:48:07AM -0500, Chris Adams wrote:
> Once upon a time, Neal Gompa said:
> > The only real problem with hardlinks is that you can't partition them
> > out across volumes. And some filesystems aren't hardlink-safe.
>
> The proposal is for hardlinking under /usr - there's n
t files too.
So as Ben and others wrote, this proposal is abouting using hardlinks
_within_ packages. The intent is for the change to have no effect
on applications and to be mostly invisible to users.
> On 7/28/25 8:33 AM, Neal Gompa wrote:
> > The only real problem with hardlinks is that
On Mon, Jul 28, 2025 at 2:56 PM Marián Konček wrote:
>
> I can see a benefit of this in case of `/usr/share/licenses/`. I don't
> know what other kinds of files are identical across multiple packages.
This Change Proposal is not about cross-package optimizations - it'
if the file is ''modified''. In
particular, all links to the same inode share the same ownership and
permissions, and obviously the same contents. Thus, we want to apply
hardlinking only to files under `/usr`, which are generally read-only
in packages.
My /usr directories are NO
I can see a benefit of this in case of `/usr/share/licenses/`. I don't
know what other kinds of files are identical across multiple packages.
And for licenses we can have a more specific solution and discuss about
hardlinks / symlinks + some canonical location.
On 25. 7. 2025 0:16,
On 28/07/2025 14.19, Chris Adams wrote:
Once upon a time, Michal Schmidt said:
On Sat, Jul 26, 2025 at 10:38 AM Pavel Raiskup wrote:
I'd rather we show extra care towards Fedora developers who are still
using Fedora, if there are any. If we make Fedora development overly
complicated compar
Once upon a time, Neal Gompa said:
> The only real problem with hardlinks is that you can't partition them
> out across volumes. And some filesystems aren't hardlink-safe.
The proposal is for hardlinking under /usr - there's no support for
having /usr (or really / - /usr can't be a separate FS si
1 - 100 of 8655 matches
Mail list logo
