Hot news:
We added new license LicenseRef-Not-Copyrightable that should be used for packages like foo-filesystem that e.g., create
just directories and does not have copyrightable code nor content.
The process of adding the licenses on list is still very slow recently.
I made an error when ad
Congratulations for the PyTorch package!
https://src.fedoraproject.org/rpms/python-torch
I hope someone will announce this great achievement to the Fedora
community too, and update the following page too.
https://fedoraproject.org/wiki/SIGs/PyTorch/packagingStatus
Jun
On Wed, Oct 11, 2023 at 11:
OLD: Fedora-Rawhide-20231206.n.0
NEW: Fedora-Rawhide-20231207.n.1
= SUMMARY =
Added images:8
Dropped images: 0
Added packages: 9
Dropped packages:1
Upgraded packages: 174
Downgraded packages: 0
Size of added packages: 3.20 MiB
Size of dropped packages
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-2/2023-12-07/fesco.2023-12-07-17.00.html
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting-2/2023-12-07/fesco.2023-12-07-17.00.txt
Log:
https://meetbot.fedoraproject.org/fedora-meeting-2/2023-12-07/fesco.2023-12-07-17.00.lo
On Thu, Dec 7, 2023 at 3:26 AM Michal Schorm wrote:
> I'd advise to create PR - wait week or 2,
> if left without response - create BZ for the specific PR as not
> everyone watches PRs and PR notifications, and wait week or two,
> if left without response - send a direct mail to the package maint
Following is the list of topics that will be discussed in the
FESCo meeting Thursday at 17:00UTC in #fedora-meeting-2 on
irc.libera.chat.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2023-12-07 17:00 UTC'
Links to all issues to be
First, let me apologize for the short notice on this. We've been
discussing it at the public ELN meetings over the last month, but I
only just now realized that I forgot to send out one of these general
announcements.
Over the last few months, you've probably seen a number of Fedora ELN
packages p
Am 02.12.23 um 09:46 schrieb Michal Schorm:
In my experience through the years, I've found very little proven
packagers that would work in what *I would see* as the right way.
I fully agree with you but I wanted to mention Miro + the Python team. From my
experience in the Python packaging spa
Because not everyone is active on discourse, I thought it makes sense to
link this here for people from the area in or close to London:
https://discussion.fedoraproject.org/t/local-meetup-london-2024/98029
--
___
devel mailing list -- devel@lists.fedor
On Thu, Dec 7, 2023 at 11:21 AM Florian Weimer wrote:
> Asking individual maintainers for trivial changes does not scale. The
> alternative would be not to address FTBFS and other build issues, maybe
> file bugs, and rely on active maintainers instead.
The alternative we want to achieve is:
(1)
On Tue, Dec 5, 2023 at 11:36 AM Daniel P. Berrangé wrote:
> IMHO all changes should be opened as merge requests in pagure. This gives
> the regular package maintainers a window of opportunity to review the
> change before it is merged. If there's no response from the package
> maintainer after a c
* Kevin Kofler via devel:
> Michael J Gruber wrote:
>> I am sick of this. Really. I am so sick of this way of stomping on each
>> others' feet.
>
> My pet peeve is provenpackagers or comaintainers who add unwanted
> automagic (autorelease, autosetup, autochangelog) to my packages. I do
> not want
12 matches
Mail list logo
