date:20230423

On Sun, Apr 23, 2023 at 11:21:58PM +0200, Björn Persson wrote:
> Kevin Fenzi wrote:
> > We could probibly come up with some
> > better way to start new topics/discussions
> 
> Yes I think I can come up with a better way. Give each tag its own
> email address, like a mailing list. That was very easy to come up with.

I think you mean each category? But you may want multiple tags on a
post... 
ie, 

https://discussion.fedoraproject.org/t/fedora-strategy-2028-focus-area-review-editions-spins-and-interests/79291
is posted in the 'Project Discussion' category with #council and
#strategy2028 tags.

> You can write the tag after the plus sign if that makes it easier to
> implement. Instead of "fedoraproject+newto...@discoursemail.com" the
> address could be "fedoraproject+de...@discoursemail.com" or maybe
> "fedoraproject+devel/newto...@discoursemail.com". Or some other format.
> The local-part can be structured any way the Discourse developers like,
> as long as it's at most 64 bytes and adheres to the dot-atom-text syntax
> in RFC 5322.

But that also doesn't solve the spam problem... anyone could send to
those addresses, and indeed spammers will. ;( 

But perhaps this could be useful with some other way to autenticate
posts. Or perhaps there could be some kind of spam detection and require
'spammy' looking posts to be moderated? 

I'm not a discourse maintainer tho, so I have no idea how open
they would be to implementing this.

kevin

signature.asc
Description: PGP signature
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: It’s time to transform the Fedora devel list into something new

On Sun, Apr 23, 2023 at 11:21:19PM +0200, Björn Persson wrote:
> Kevin Fenzi wrote:
> > One bug I hit setting this up this weekend... some (but not all) of the
> > categories appear to have newlines in the List-ID: header. ;( 
> > 
> > ie, 
> > 
> > List-ID: Fedora Discussion | Ask Fedora Ask in English
> >  
> > 
> > Hopefully this is a bug that can be fixed... 
> > 
> > So the above won't really work as the MATCH doesn't include the second
> > line with the actual listid in it, only the description. ;( 
> 
> I think you'll have to blame Procmail for that. What you show is called
> folding in RFC 5322. It's valid syntax if the continuation line begins
> with whitespace, which it looks like it does. Folding is even
> recommended for lines longer than 78 characters. Programs that parse
> email are supposed to unfold folded lines.
> 
> The complexities of text-based protocols provide for so much fun!

Indeed. Actually procmail matches on it fine, but it doesn't include the
part after the newline in $MATCH, which makes it harder to parse out the
second part if you want to use that to filter into a maildir with that
name. :( 

I can work around it, it just seems... unexpected and I wanted to
mention it in case others were going down that path.

kevin


signature.asc
Description: PGP signature
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Choosing British Dissertation Editors Reviews

2023-04-23 Thread N Buzz

Dissertation editing services can help you improve the quality of your british 
dissertation editors reviews: 
https://www.premiumdissertationhelp.com/dissertation-editing-services/ 
dissertation, making it more readable and easier for readers to understand. 
They can also help you avoid common mistakes, so that your paper looks 
professional and polished. However, it is important to choose a quality service 
that will provide you with the right advice and recommendations for your 
specific needs.
There are many different types of editors dissertation writing service: 
https://www.premiumdissertationhelp.com/dissertation-writing-services/ 
available online, so it can be difficult to know where to start when choosing 
one. Some of the key factors to consider include the quality of the editor and 
their experience. In addition, it is important to find a service that is 
transparent with their work and is willing to discuss what they do and don’t do 
in order to help you make an informed decision about your dissertation editing 
needs.
Grammar and Punctuation:
The first step to hiring a good dissertation editor is to choose one that has 
experience in grammar and punctuation. This online dissertation help uk: 
https://www.premiumdissertationhelp.com/  will ensure that the editor knows how 
to edit your work and can spot errors that could be easily overlooked. The 
editor will be able to improve your writing by correcting grammatical errors 
and punctuation issues.
Sentence Structure:
A professional do my dissertation: 
https://www.premiumdissertationhelp.com/do-my-dissertation/ editor can help you 
improve the flow of your writing by fixing sentence structure issues, as well 
as catching awkward phrasing and other word choices that can be difficult for a 
reader to understand. They can also help you avoid repetition in your writing 
and use more appropriate word choices to convey your message more clearly.
Proofreading:
Finally, a good dissertation editing service will be able to ensure that your 
document is free from dissertation editing services: 
https://www.premiumdissertationhelp.com/dissertation-editing-services/ any 
spelling or grammatical errors. They will also be able to check your formatting 
and citations, so that your dissertation is ready to submit.
The best dissertation editors will also be able to help you with ensuring that 
your paper is structured correctly and meets your university’s requirements. 
They will be able to provide feedback and suggestions for improving your 
document, so that you can get premium dissertation help: 
https://www.premiumdissertationhelp.com/ the recognition you deserve.
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Dissertation Editing Services

2023-04-23 Thread N Buzz

[url=https://www.premiumdissertationhelp.com/dissertation-editing-services.php]british
 dissertation editors reviews[/url]

Dissertation editing services help writers make their work clear and british 
dissertation editors reviews understandable to readers. They correct spelling 
and grammatical errors, improve flow, support arguments, ensure adherence to an 
academic style, and make sure the writing conforms to APA, MLA, Chicago, or 
other citation systems.
Editors will be experts in the specific subject matter they edit. They will be 
able to spot the key points of the thesis, and will have a firm understanding 
of the dissertation process and the particular needs of the client. They will 
be able to identify any recurring problems in the text and provide suggestions 
for improving it.
Some dissertation editors will also ensure that the content of the manuscript 
adheres to the style and formatting online dissertation help uk requirements of 
the client's university or doctoral program. This can include formatting all 
introductory pages and appendices, tables of contents, figures, heading styles, 
and other elements.
Most students spend a long time researching, writing, and editing their 
dissertations, so a professional dissertation editor is essential for ensuring 
the dissertation is error-free. They will also ensure the dissertation is 
properly formatted, including all citations and references, so that the thesis 
follows the prescribed submission guidelines of the school or institution.
When choosing a company for your dissertation editing needs, look for a company 
that uses experienced and trained dissertation editors who have PhDs in the 
field of study you are writing in. They are experts in the topic, and can 
provide detailed feedback to help you improve your work.
They are also experts in the specific do my dissertation academic language and 
style that you need for your project. They will know how to structure your 
paper, and they will be able to help you choose the right words for your 
argument.
Getting your work edited by an experienced editor will make a big difference in 
the quality of your final product. They will be able to pick up on the 
important dissertation editing services details and make them shine in your 
dissertation.
The best dissertation editing services will be able to tell you what they are 
going to do and how much it will cost before you agree to use them. This is 
important to ensure that you can afford their services and that the final 
product will meet your expectations.
Many editing companies will offer a variety of additional services to their 
clients, such as research dissertation writing service assistance, data 
analysis, writing tips and techniques, mentoring to help guide students through 
the dissertation process, preparation of the defense of the dissertation, legal 
services concerning copyright and fair use of copyrighted material, graphics, 
website design and editing, translation, and the preparation of scholarly 
articles.
The best dissertation editing services will also give you a free sample of 
their work to see how they edit, and they will always be willing to answer any 
questions you have. The service will also provide you with a detailed 
explanation of any changes that premium dissertation help were made to your 
document.
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: It’s time to transform the Fedora devel list into something new

Kevin Fenzi wrote:
> We could probibly come up with some
> better way to start new topics/discussions

Yes I think I can come up with a better way. Give each tag its own
email address, like a mailing list. That was very easy to come up with.

You can write the tag after the plus sign if that makes it easier to
implement. Instead of "fedoraproject+newto...@discoursemail.com" the
address could be "fedoraproject+de...@discoursemail.com" or maybe
"fedoraproject+devel/newto...@discoursemail.com". Or some other format.
The local-part can be structured any way the Discourse developers like,
as long as it's at most 64 bytes and adheres to the dot-atom-text syntax
in RFC 5322.

Björn Persson

pgpWVzBgAke8P.pgp
Description: OpenPGP digital signatur
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: It’s time to transform the Fedora devel list into something new

Kevin Fenzi wrote:
> One bug I hit setting this up this weekend... some (but not all) of the
> categories appear to have newlines in the List-ID: header. ;( 
> 
> ie, 
> 
> List-ID: Fedora Discussion | Ask Fedora Ask in English
>  
> 
> Hopefully this is a bug that can be fixed... 
> 
> So the above won't really work as the MATCH doesn't include the second
> line with the actual listid in it, only the description. ;( 

I think you'll have to blame Procmail for that. What you show is called
folding in RFC 5322. It's valid syntax if the continuation line begins
with whitespace, which it looks like it does. Folding is even
recommended for lines longer than 78 characters. Programs that parse
email are supposed to unfold folded lines.

The complexities of text-based protocols provide for so much fun!

Björn Persson


pgp9IXcpXeGMk.pgp
Description: OpenPGP digital signatur
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: It’s time to transform the Fedora devel list into something new

2023-04-23 Thread Alexander Ploumistos

Hello Matthew, everyone,

The TL;DR version of my thoughts and suggestions on this topic:
implement the improvements suggested so far as best as possible, so
that the people who want to interact with Discourse through their mail
reader can do so with little to no friction. Clearly define and
document the new tags, what type of information should go where and
who needs to subscribe to which tag. Redefine our information channels
in a saner way, that reflects our consumption and use of that
information. Document on the docs website how subscriptions, filtering
etc. work in the Discourse UI for each use case. Avoid further
community fragmentation by switching cold turkey once the organization
of the site and the mailing features are on par with what people have
come to expect from mailing lists. Turn on the requirement of adhesion
to a fas group for people who can post on the new channels.

Longer version:
Like most of the people who have chimed in so far, I too have strong
opinions and feelings about such a transition. I joined the mailing
list almost a decade ago and I have been following it for much longer.
I am subscribed to a number of lists, I set up my filters ages ago and
over time, as the project and my involvement with it changed, I
adapted those filters with minimal effort. I can certainly sympathize
with all the people who are far more active than I am and who interact
with Fedora first and foremost through these lists, even though I
don't go so far as to run an NNTP server or type my replies in vi
(admittedly, that was fun for a while).

Since this transition is more or less a settled issue, as far as I can
understand, I would like to make some suggestions as to how this could
be as painless as possible for everyone. Before that though, I'd like
to take a moment to point out something that has been very lightly
touched upon, the nature of the medium (e-mail) and its non-technical
aspects. I think most people are acquainted with the formalisms and
the urgency/importance attributed to different means of communication.
We don't feel the same way about a written letter we found in our
mailbox, a phone call, an e-mail, an instant message, an SMS or a
forum post. E-mail commands a certain "decorum" close to that of a
written letter. Perhaps this is the reason why certain people find it
daunting to engage with the project through the mailing lists. At the
same time and while we're no strangers to heated exchanges and a far
cry from literary correspondence, the etiquette dictated by the medium
does create a safe space for its users. We all pretty much understand
and adhere to the rules associated with this kind of written
communication and have certain expectations when we use it and even
more so given our relationship to Fedora. This is not the case with a
forum and certainly not the case with all the people who will go on
d.f.o. For this reason I strongly suggest that the "Project
Discussion" category or whatever subcategory our particular
subcommunity ends up on, is indeed walled off from the rest of the
website. I do not need the noise, the rudeness and the abuse that I
often found on ask.fedoraproject.org (which is now a part of d.f.o) to
flood over these channels. The requirement on people belonging to a
specific fas group before they can post should be on from day one and
exceptions made only when they are warranted.

On Thu, Apr 20, 2023 at 11:21 PM Matthew Miller
 wrote:
>
> We’re scattered in actual practice
> --

This is not necessarily or always a bad thing, nor is it a problem
that can be solved by the transition to Discourse. I thought I had a
fairly good grasp of most of Fedora's activities and communities until
I saw the organizational chart posted by Marie Nordin a while back and
I realized that about a third of Fedora was terra incognita to me.
Then again, we cannot all afford the time nor do we have the skills
and proclivities required to be involved with everything. The devel ML
has been a good "firehose" of information for people who work on
packaging and development and everything tangentially tied to these.
It's only natural that the stream of information will get fragmented
down the road, but we've mostly had a "bird's eye view" of the issues
of interest to us through this channel and we could (usually) follow
up on whatever place a particular discussion unfolded, be it bugzilla,
a pagure ticket or whatever.

The "announce" ML could become an "announce" category for all things
Fedora, which might be of interest to people from different
subcommunities, while keeping it relatively low-traffic. E.g. voting
for the default wallpaper for the next Fedora release is something
that would fit that description, whereas a release party in Paraguay
or the move to Python 3.12 would not.

If the mailing lists and Discourse are being used simultaneously, we
will end up even more scattered than we are now. If the concerns
voiced so far can be addressed and

[Bug 2188483] perl-Module-CoreList-5.20230423 is available

2023-04-23 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=2188483

Upstream Release Monitoring  
changed:

   What|Removed |Added

Summary|perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023
   |0420 is available   |0423 is available



--- Comment #1 from Upstream Release Monitoring 
 ---
Releases retrieved: 5.20230423
Upstream release that is considered latest: 5.20230423
Current version/release in rawhide: 5.20230320-1.fc39
URL: https://metacpan.org/dist/Module-CoreList/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/3080/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-Module-CoreList


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2188483
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: It’s time to transform the Fedora devel list into something new

2023-04-23 Thread Randy Barlow via devel


On 4/21/23 14:05, Matthew Miller wrote:

Accessiblity is important to Fedora, and I take this seriously. For
Discourse, hit the ? key to bring up the page describing keyboard shortcuts.


One thing I don't care for when it comes to web apps and keyboard 
shortcuts is that they are non-standard. When I can process 
communications in my mail client, all mail uses the same keyboard 
shortcuts, no matter which site it came from. With web apps, every web 
app has it's own keyboard shortcuts, which makes learning them all 
difficult.

___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: It’s time to transform the Fedora devel list into something new

Il 20/04/23 23:20, Matthew Miller ha scritto:
> It’s time to transform the Fedora devel list into something new
> ===
>
> ...
> Matthew Miller
> 
> Fedora Project Leader

I've tried to follow up all the replies this post has caused, but it
takes time to read in a foreign language and there are simply too many
posts to read them all, so I'll just go and give you some thoughts that
may have already been written by someone else.

- I'm not enthusiast of being forced to open a web browser to be noticed
about new posts. I'm aware there's a "mailing list" mode, but it's not
clear if it's perfectly usable or would be sub-optimal. I think it needs
to be tested.

- I'm also skeptical about having all mailing lists under one Discourse
category (I suppose it will be "Project Discussions") and use tags to
filter them. I think an high volume list such as devel should gone under
it's own category. Maybe for other low volumes lists which are specific
to groups or aspects can use the "tags" categorization.

- Another problem is that there are already too many tags available and
the tag description is not visible in the post submit form. I think a
new user would be confused what tag to use. I'm confused too, but that's
probably just me...

- The Discourse Android app is no use. So, again, browser on mobile or
mailing list mode.

Mattia

___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: It’s time to transform the Fedora devel list into something new

On Sun, Apr 23, 2023 at 04:54:48PM +, Mattia Verga via devel wrote:
> Il 23/04/23 17:01, Björn Persson ha scritto:
> >
> > You let the quarrel go this far before you even bothered to mention
> > that? You're clearly not serious about selling the email features of
> > Discourse.
> >
> > You're trying to convince email users that your preferred communication
> > program is better than their preferred communication program. Users of
> > various email programs are saying no, the program I have chosen works
> > better for my needs. Do you also waste time trying to convince Emacs
> > users to switch to Vi?
> >
> > Instead of trying to make everybody use the same Javascript program,
> > what you should do is show how your preferred program implements the
> > relevant standards to be interoperable with my preferred program, so
> > that we can communicate while each using our respective programs. If
> > it's not interoperable, then that's where the problem is.
> >
> I'm not enthusiast about this proposed change too, but let's not go
> personal.

100% agreed.

> As I understand, it's not about Matthew personal preferences, it's about
> maintaining mailing list running needs manpower which Fedora is running
> out of. Switching to Discourse can probably relief some of the burden
> from fedora-infra guys.

I can't speak (or type) for Matthew, but I don't think that actually has
much to do with this. I'd love to be running a newer/better supported
mailman3 (and some folks have been hard at work to make that happen),
but even if right now today we had a super clean, well supported
mailman3 install for our lists, all the points in Matthews email would
still apply. He didn't mention mailman3 in his post at all that I can
see. I think we will be running mailing lists in some form for a long
while still, just fewer people will be interacting with them.

kevin


signature.asc
Description: PGP signature
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2188469] perl-CPAN-Perl-Releases-5.20230423 is available

2023-04-23 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=2188469

Upstream Release Monitoring  
changed:

   What|Removed |Added

Summary|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2
   |0230420 is available|0230423 is available



--- Comment #1 from Upstream Release Monitoring 
 ---
Releases retrieved: 5.20230423
Upstream release that is considered latest: 5.20230423
Current version/release in rawhide: 5.20230416-1.fc39
URL: https://metacpan.org/dist/CPAN-Perl-Releases/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/5881/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-CPAN-Perl-Releases


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2188469
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: It’s time to transform the Fedora devel list into something new

On Sat, Apr 22, 2023 at 03:04:26PM -0700, Kevin Fenzi wrote:
> 
> So I've been using the email bridge for a while (I think since we set it
> up) and it's got it's issues for sure, but I am not sure if it's as bad
> as folks fear. 
> 
> https://discussion.fedoraproject.org/t/guide-to-interacting-with-this-site-by-email/25960
> has general info. 
> 
> I had just been dumping it into one mailbox, but today I poked at
> getting it sorted better. For those of you ancient dinosaurs like myself
> still using procmail (written in 1990!), the following hacky recipe
> works for me: 
> 
> 
> :0
> * ^List-Id: .*<\/[-a-z0-9]*\.discussion\.fedoraproject\.org>
> {
>  NAME=`echo "${MATCH}" | sed 
> 's/\.discussion\.fedoraproject\.org>$//'`
> 
>  :0
>  $HOME/Maildir/.fedora.discussion.$NAME/ 
> }
> 
> This gets posts flowing into folders by list-id, so: 
> 
> .fedora.discussion.Ask-Fedora_Ask-in-English/
> .fedora.discussion.Project-Discussion/
> 
> And of course you can filter more with the actual tags from there if you
> like. Posts should work fine as they have a reply-to hash with the
> topic/post and who the email was sent to.

One bug I hit setting this up this weekend... some (but not all) of the
categories appear to have newlines in the List-ID: header. ;( 

ie, 

List-ID: Fedora Discussion | Ask Fedora Ask in English
 

Hopefully this is a bug that can be fixed... 

So the above won't really work as the MATCH doesn't include the second
line with the actual listid in it, only the description. ;( 

kevin


signature.asc
Description: PGP signature
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: It’s time to transform the Fedora devel list into something new

On Sun, Apr 23, 2023 at 05:01:53PM +0200, Björn Persson wrote:
> Matthew Miller wrote:
> > There _are_ email notifications, 
> 
> You keep talking about "notifications". I don't want a notification
> saying "somebody said something; run our Javascript program to find out
> what it was". I want the actual message delivered to my mailbox.
> 
> But some people in this thread talk as if it's possible to get the
> actual messages by email. I even see some hints that a proper tree view
> might be possible. But many others say the email features of Discourse
> are no good. The overall picture is unclear and far from convincing.

Yes, you absolutely can interact with discourse via email (mostly).
You will need to go to the website to setup things initially, but after
that you should not need to.

> > and you can interact by replying to them.
> 
> You let the quarrel go this far before you even bothered to mention
> that? You're clearly not serious about selling the email features of
> Discourse.
> 
> You're trying to convince email users that your preferred communication
> program is better than their preferred communication program. Users of
> various email programs are saying no, the program I have chosen works
> better for my needs. Do you also waste time trying to convince Emacs
> users to switch to Vi?
> 
> Instead of trying to make everybody use the same Javascript program,
> what you should do is show how your preferred program implements the
> relevant standards to be interoperable with my preferred program, so
> that we can communicate while each using our respective programs. If
> it's not interoperable, then that's where the problem is.
> 
> So how complete is Discourse's email functionality actually? Can it be
> used as a mailing list server, or not?

It can send you emails for the things you tell it you want emails and
you can sort and read and reply to them as you like.

> > Do take a look at
> > 
> > https://discussion.fedoraproject.org/t/guide-to-interacting-with-this-site-by-email/25960
> 
> Okay okay fine! I'll start up a browser in which the Javascript program
> even works and go read in the Javascript program about how I might not
> have to use the Javascript program.
> 
> So it says a "tag" is supposed to be sort of like a mailing list, but
> there's only a single global email address for starting new threads.

Yes, as noted, this is currently the setup for new threads/discussions
due to spam. Possibly some better way can be implemented.

> There's no way to send to a specific tag. Thus it's impossible to post
> to a specific mailing-list-equivalent. How am I supposed to ensure that
> my messages reach the appropriate audience?

Thats the weakest part of the setup for discourse by email right now I
think. You can easily reply to existing posts just fine. It's just new
threads/discussions that you need to either post from the web interface
or send into the one address and have some moderator tag it and approve
it.
> 
> Maybe by replying? It's rather unclear how replies by email are handled,
> but I can guess that they're given the same tag as the message they
> reply to. If that's the case, then it almost seems like they *want*
> people to reply to an irrelevant thread instead of posting a new thread.
> I suppose a more likely explanation is that the email notifications are
> meant to draw users back to the Javascript program.

You can reply to any email you get. It appears to use a reply-to thats a
hash so it knows who you are and what post/discussion you are replying
to so it can process your reply. 

> Either way, according to that post the answer is no, Discourse is not
> usable as a list server. Those who want to replace Mailman with
> Discourse should work on improving its email capabilities until it can
> be used as a list server.

Things can always be improved by "used as a list server" is not a spec
of concrete proposal for functionality. 

Anyhow, I invite you to give it a try. I am using the email gateway here
and for the most part it works fine. 

There's a bug I did hit where some of the categories seem to put \n in
List-Id: headers, which is anoying to manage, but aside from that, all
the emails come in, I can reply. We could probibly come up with some
better way to start new topics/discussions, but in the mean time either
the web interface or just sending an email and adding a 'please tag this
as #foo' should work I would think.

kevin


signature.asc
Description: PGP signature
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: It’s time to transform the Fedora devel list into something new

Il 23/04/23 17:01, Björn Persson ha scritto:
>
> You let the quarrel go this far before you even bothered to mention
> that? You're clearly not serious about selling the email features of
> Discourse.
>
> You're trying to convince email users that your preferred communication
> program is better than their preferred communication program. Users of
> various email programs are saying no, the program I have chosen works
> better for my needs. Do you also waste time trying to convince Emacs
> users to switch to Vi?
>
> Instead of trying to make everybody use the same Javascript program,
> what you should do is show how your preferred program implements the
> relevant standards to be interoperable with my preferred program, so
> that we can communicate while each using our respective programs. If
> it's not interoperable, then that's where the problem is.
>
I'm not enthusiast about this proposed change too, but let's not go
personal.

As I understand, it's not about Matthew personal preferences, it's about
maintaining mailing list running needs manpower which Fedora is running
out of. Switching to Discourse can probably relief some of the burden
from fedora-infra guys.

Mattia
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: It’s time to transform the Fedora devel list into something new

2023-04-23 Thread Michael Catanzaro

On Sun, Apr 23 2023 at 05:01:53 PM +0200, Björn Persson 
 wrote:

But some people in this thread talk as if it's possible to get the
actual messages by email. I even see some hints that a proper tree 
view

might be possible. But many others say the email features of Discourse
are no good. The overall picture is unclear and far from convincing.


You have to check one checkbox in settings if you want to get messages 
by mail. The mailing list mode is not amazing, but it works.


___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: It’s time to transform the Fedora devel list into something new

Matthew Miller wrote:
> It is also possible to enable
> new topics by email, but that's vulernable to impersonation (and spam) so
> if we enable that there probably will be a moderation step.

Email signed with OpenPGP/MIME solves the impersonation and spam
problems. A message could be allowed to bypass the moderation after it's
verified that it's signed with the correct public key for an email
address registered in a Fedora account.

DKIM also seems able to assert that a message is from a certain sender
address, although almost all usage I've seen states only a domain name.

But if those new topics can't be sent to a mailing-list-equivalent, but
just end up in some sort of "other" bucket, then it seems useless
anyway.

Björn Persson

pgpcbyFcDPtSX.pgp
Description: OpenPGP digital signatur
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: It’s time to transform the Fedora devel list into something new

Matthew Miller wrote:
> There _are_ email notifications,

You keep talking about "notifications". I don't want a notification
saying "somebody said something; run our Javascript program to find out
what it was". I want the actual message delivered to my mailbox.

But some people in this thread talk as if it's possible to get the
actual messages by email. I even see some hints that a proper tree view
might be possible. But many others say the email features of Discourse
are no good. The overall picture is unclear and far from convincing.

> and you can interact by replying to them.

You let the quarrel go this far before you even bothered to mention
that? You're clearly not serious about selling the email features of
Discourse.

You're trying to convince email users that your preferred communication
program is better than their preferred communication program. Users of
various email programs are saying no, the program I have chosen works
better for my needs. Do you also waste time trying to convince Emacs
users to switch to Vi?

Instead of trying to make everybody use the same Javascript program,
what you should do is show how your preferred program implements the
relevant standards to be interoperable with my preferred program, so
that we can communicate while each using our respective programs. If
it's not interoperable, then that's where the problem is.

So how complete is Discourse's email functionality actually? Can it be
used as a mailing list server, or not?

> Do take a look at
>
> https://discussion.fedoraproject.org/t/guide-to-interacting-with-this-site-by-email/25960

Okay okay fine! I'll start up a browser in which the Javascript program
even works and go read in the Javascript program about how I might not
have to use the Javascript program.

So it says a "tag" is supposed to be sort of like a mailing list, but
there's only a single global email address for starting new threads.
There's no way to send to a specific tag. Thus it's impossible to post
to a specific mailing-list-equivalent. How am I supposed to ensure that
my messages reach the appropriate audience?

Maybe by replying? It's rather unclear how replies by email are handled,
but I can guess that they're given the same tag as the message they
reply to. If that's the case, then it almost seems like they *want*
people to reply to an irrelevant thread instead of posting a new thread.
I suppose a more likely explanation is that the email notifications are
meant to draw users back to the Javascript program.

Either way, according to that post the answer is no, Discourse is not
usable as a list server. Those who want to replace Mailman with
Discourse should work on improving its email capabilities until it can
be used as a list server.

Björn Persson

pgpUVt9_aKC4f.pgp
Description: OpenPGP digital signatur
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue

Re: package WP-CLI needs update

2023-04-23 Thread Marius Schwarz


Am 20.04.23 um 11:01 schrieb Dan Horák:

On Thu, 20 Apr 2023 09:20:27 +0200
Marius Schwarz  wrote:


Hi,

package WP-CLI needs an update to 2.7.1 in all releases as in the
current state, it's useless.

A bugreport against the package is open since nov. 2022:

https://bugzilla.redhat.com/show_bug.cgi?id=2148434

the maintainer hasn't been active in years if I see right, feel free to
take over the maintainership via
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/



No big deal, besides, i need to get into the packager group first, 
therefor i need a sponsor afaik.


best regards,
Marius Schwarz
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Heads-up: edflib 1.24 coming to Rawhide

2023-04-23 Thread Ben Beasley

In one week (2023-04-30), or slightly later, I plan to update edflib to 
1.24, which includes a .so version bump. The shared library versioning 
was previously added downstream; now upstream is handling it. The 
package is currently a leaf, so there should be no impact.

___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: fedora-review crash

2023-04-23 Thread Alexander Ploumistos

On Sun, Apr 23, 2023 at 3:37 PM Sérgio Basto  wrote:
>
> On Thu, 2023-03-23 at 01:38 +0200, Alexander Ploumistos wrote:
> > On Wed, Mar 22, 2023 at 8:29 PM Sérgio Basto 
> > wrote:
> > >
> > > ah. I think this is one bug in Fedora review (already reported)
> > >
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1824526
> >
>
> Sorry, I want mention this bug report
> https://bugzilla.redhat.com/show_bug.cgi?id=2132574

Thank you Sergio, this makes more sense. I've been meaning to ask, but
I've been overwhelmed with work and it slipped my mind.
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: fedora-review crash

2023-04-23 Thread Sérgio Basto

On Thu, 2023-03-23 at 01:38 +0200, Alexander Ploumistos wrote:
> On Wed, Mar 22, 2023 at 8:29 PM Sérgio Basto 
> wrote:
> > 
> > ah. I think this is one bug in Fedora review (already reported)
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=1824526
> 

Sorry, I want mention this bug report
https://bugzilla.redhat.com/show_bug.cgi?id=2132574




> Thanks for that, though I do not have any non-rpm files in that
> folder:
> $ ls -AC Desktop/coding/reviews/deps/
> edwin-fonts-0.54-1.fc39.noarch.rpm
> finale-broadway-text-fonts-1.1-1.fc39.noarch.rpm
> finale-legacy-fonts-1.6-1.fc39.noarch.rpm
> leland-fonts-all-0.77-1.fc39.noarch.rpm
> finale-ash-fonts-1.7-1.fc39.noarch.rpm
> finale-engraver-fonts-1.4-1.fc39.noarch.rpm
> finale-lyrics-fonts-2.3-1.fc39.noarch.rpm
> leland-text-fonts-0.77-1.fc39.noarch.rpm
> finale-ash-text-fonts-1.3-1.fc39.noarch.rpm
> finale-jazz-fonts-1.9-1.fc39.noarch.rpm
> finale-maestro-fonts-2.7-1.fc39.noarch.rpm
> finale-broadway-fonts-1.4-1.fc39.noarch.rpm
> finale-jazz-text-fonts-1.3-1.fc39.noarch.rpm
> finale-maestro-text-fonts-1.6-1.fc39.noarch.rpm
> finale-broadway-legacy-text-fonts-1.1-1.fc39.noarch.rpm
> finale-jazz-text-lowercase-fonts-1.4-1.fc39.noarch.rpm
> leland-fonts-0.77-1.fc39.noarch.rpm
> ___
> 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 Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

-- 
Sérgio M. B.
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora rawhide compose report: 20230423.n.0 changes

2023-04-23 Thread Fedora Rawhide Report

OLD: Fedora-Rawhide-20230422.n.0
NEW: Fedora-Rawhide-20230423.n.0

= SUMMARY =
Added images:0
Dropped images:  1
Added packages:  0
Dropped packages:0
Upgraded packages:   30
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   2.98 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   87.87 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =

= DROPPED IMAGES =
Image: Server_KVM qcow2 aarch64
Path: Server/aarch64/images/Fedora-Server-KVM-Rawhide-20230422.n.0.aarch64.qcow2

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  IQmol-3.1.2-2.fc39
Old package:  IQmol-3.1.2-1.fc39
Summary:  A free open-source molecular editor and visualization package
RPMs: IQmol IQmol-samples
Size: 37.19 MiB
Size change:  -63.50 KiB
Changelog:
  * Sat Apr 22 2023 Susi Lehtola  - 3.1.2-2
  - Fix file paths for data files.


Package:  R-digest-0.6.31-1.fc39
Old package:  R-digest-0.6.29-2.fc38
Summary:  Create Cryptographic Hash Digest of R Objects
RPMs: R-digest R-digest-devel
Size: 1.12 MiB
Size change:  -935 B
Changelog:
  * Fri Apr 21 2023 I??aki ??car  - 0.6.31-1
  - R-maint-sig mass rebuild
  - Update to latest version


Package:  calls-44.1-1.fc39
Old package:  calls-44.0-1.fc39
Summary:  A phone dialer and call handler
RPMs: calls
Size: 1.38 MiB
Size change:  5.02 KiB
Changelog:
  * Sat Apr 22 2023 torbuntu  - 44.1-1
  - Update calls to 44.1


Package:  ceph-2:17.2.6-2.fc39
Old package:  ceph-2:17.2.6-1.fc39
Summary:  User space components of the Ceph file system
RPMs: ceph ceph-base ceph-common ceph-exporter ceph-fuse 
ceph-grafana-dashboards ceph-immutable-object-cache ceph-mds ceph-mgr 
ceph-mgr-cephadm ceph-mgr-dashboard ceph-mgr-diskprediction-local 
ceph-mgr-k8sevents ceph-mgr-modules-core ceph-mgr-rook ceph-mon ceph-osd 
ceph-prometheus-alerts ceph-radosgw ceph-resource-agents ceph-selinux ceph-test 
ceph-volume cephadm cephfs-java cephfs-mirror cephfs-shell cephfs-top 
libcephfs-devel libcephfs2 libcephfs_jni-devel libcephfs_jni1 libcephsqlite 
libcephsqlite-devel librados-devel librados2 libradospp-devel 
libradosstriper-devel libradosstriper1 librbd-devel librbd1 librgw-devel 
librgw2 python3-ceph-argparse python3-ceph-common python3-cephfs python3-rados 
python3-rbd python3-rgw rados-objclass-devel rbd-fuse rbd-mirror rbd-nbd
Size: 416.84 MiB
Size change:  62.06 MiB
Changelog:
  * Thu Apr 20 2023 Kaleb S. KEITHLEY  - 2:17.2.6-2
  - ceph-17.2.6, rebuild with bundled rocksdb until ready for rocksdb-8.x


Package:  clamtk-6.15-1.fc39
Old package:  clamtk-6.14-6.fc39
Summary:  Easy to use graphical user interface for Clam anti virus
RPMs: clamtk
Size: 215.55 KiB
Size change:  1.71 KiB
Changelog:
  * Sat Apr 22 2023 Dave M.  - 6.15-1
  - Updated to release 6.15.


Package:  clojure-maven-plugin-1.9.2-1.fc39
Old package:  clojure-maven-plugin-1.8.4-9.fc38
Summary:  Clojure plugin for Maven
RPMs: clojure-maven-plugin
Size: 76.34 KiB
Size change:  -67 B
Changelog:
  * Sat Apr 22 2023 Markku Korkeala  - 1.9.2-1
  - Update to upstream release 1.9.2
  - Remove unnecessary plugins from pom


Package:  container-selinux-2:2.211.0-1.fc39
Old package:  container-selinux-2:2.210.0-1.fc39
Summary:  SELinux policies for container runtimes
RPMs: container-selinux
Size: 51.50 KiB
Size change:  18 B
Changelog:
  * Sat Apr 22 2023 RH Container Bot  - 
2:2.211.0-1
  - auto bump to v2.211.0


Package:  elfutils-0.189-2.fc39
Old package:  elfutils-0.189-1.fc39
Summary:  A collection of utilities and DSOs to handle ELF files and DWARF 
data
RPMs: elfutils elfutils-debuginfod elfutils-debuginfod-client 
elfutils-debuginfod-client-devel elfutils-default-yama-scope elfutils-devel 
elfutils-libelf elfutils-libelf-devel elfutils-libs
Size: 5.61 MiB
Size change:  -1.03 KiB
Changelog:
  * Sat Apr 22 2023 Mark Wielaard  - 0.189-2
  - Add elfutils-0.189-c99-compat.patch
  - Add elfutils-0.189-elfcompress.patch


Package:  gcc-13.0.1-0.16.fc39
Old package:  gcc-13.0.1-0.15.fc39
Summary:  Various compilers (C, C++, Objective-C, ...)
RPMs: cpp gcc gcc-c++ gcc-gdb-plugin gcc-gdc gcc-gfortran gcc-gm2 
gcc-gnat gcc-go gcc-objc gcc-objc++ gcc-offload-nvptx gcc-plugin-annobin 
gcc-plugin-devel libasan libasan-static libatomic libatomic-static libgcc 
libgccjit libgccjit-devel libgfortran libgfortran-static libgm2 libgm2-static 
libgnat libgnat-devel libgnat-static libgo libgo-devel libgo-static libgomp 
libgomp-offload-nvptx libgphobos libgphobos-static libhwasan libhwasan-static 
libitm libitm-devel libitm-static liblsan liblsan-static libobjc libquadmath 
libquadmath-devel libquadmath-static libstdc++ libstdc++-devel libstdc++-docs 
libstdc++-static libtsan

Re: SPDX Statistics - ZX Spectrum edition

2023-04-23 Thread Richard Shaw

On Sun, Apr 23, 2023 at 4:09 AM Miroslav Suchý  wrote:

> New version of fedora-license-data and license-validate has been released.
>
> NEW: the package fedora-license-data now contains BNF grammar which you
> can use. It is available in `/usr/share/fedora-license-data/grammar.lark`
>

You'll have to explain to me the significance of this.

Thanks,
Richard
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Broken gcc 13.0.1-0.15.fc39 (missing )

Il 23/04/23 11:17, Tomasz Kłoczko ha scritto:

> Hi,
>
> Looks like with latest gcc 31.0.1-0.15.fc39 many packages builds are failing 
> with:
>
> /usr/lib/gcc/x86_64-redhat-linux/13/include/immintrin.h:135:10: fatal error: 
> amxcomplexintrin.h: No such file or directory
> 135 | #include 
> | ^~~~
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109600
>
> kloczek
> --
> Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH

Today I was able to builda package that was previously failed, 
gcc-13.0.1-0.16.fc39 has fixed the problem in Rawhide.

Mattia___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: SPDX Statistics - ZX Spectrum edition

Il 23/04/23 11:09, Miroslav Suchý ha scritto:
>
> 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
>
> https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-final-maintainers.txt
>
>
I have updated some of my packages, but they're still listed there. I've
used "Update license tag to SPDX" in the changelog.

kpmcore and kde-partitionmanager were rebuilt after the update.

indistarter, libpasastro and libpasraw were not rebuilt after the change
(only updated in src).

python-pymediawiki is MIT (no change).

Mattia

___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Broken gcc 13.0.1-0.15.fc39 (missing )

2023-04-23 Thread Tomasz Kłoczko

Hi,

Looks like with latest gcc 31.0.1-0.15.fc39 many packages builds are
failing with:

/usr/lib/gcc/x86_64-redhat-linux/13/include/immintrin.h:135:10: fatal
error: amxcomplexintrin.h: No such file or directory
  135 | #include 
  |  ^~~~

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109600

kloczek
-- 
Tomasz Kłoczko | LinkedIn: *http://lnkd.in/FXPWxH *
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

SPDX Statistics - ZX Spectrum edition

2023-04-23 Thread Miroslav Suchý


Two weeks ago we had:


* 22918 spec files in Fedora

* 29406license tags in all spec files

* 19348 tags have not been converted to SPDX yet

* 7521tags can be trivially converted using `license-fedora2spdx`

* Progress: 34% ░░░███ 100%



Today we have:

* 22961 spec files in Fedora

* 29459license tags in all spec files

* 19099 tags have not been converted to SPDX yet

* 7404tags can be trivially converted using `license-fedora2spdx`

* Progress: 35% ░░░███ 100%

ELN subset:

* 2099 out of 4669 packages has been converted

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

https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-final-maintainers.txt

New version of fedora-license-data and license-validate has been released.

NEW: the package fedora-license-data now contains BNF grammar which you can use. It is available in 
`/usr/share/fedora-license-data/grammar.lark`


Legal docs and especially

https://docs.fedoraproject.org/en-US/legal/allowed-licenses/

was updated too.

I updated the progress in this spreadsheet:

https://docs.google.com/spreadsheets/d/1QVMEzXWML-6_Mrlln02axFAaRKCQ8zE807rpCjus-8s/edit?usp=sharing

You converted about 300 license tags in 14 days.

New projection when we will be finished is 2024-07-07. Pure linear 
approximation.

If your package does not have neither git-log entry nor spec-changelog entry mentioning SPDX and you know your license 
tag matches SPDX formula, you can put your package on ignore list


https://pagure.io/copr/license-validate/blob/main/f/ignore-packages.txt

Either pull-request or email to me is fine.

Tip of the day:

We will have hackfest this week at Wednesday! There will be a short presentation for background and a demo on updating a 
package to start, then we'll work on packages and be available for questions and help.

https://calendar.fedoraproject.org/SIGs/2023/4/26/#m10492d away.


Why ZX Spectrum? On this day, 41 years ago was sold the first ZX Spectrum. It was one of the first home computer. And it 
was my first computer too.


https://en.wikipedia.org/wiki/ZX_Spectrum

You can try it thanks to http://www.rastersoft.com/programas/fbzx.html

You will need fbzx and fuse-emulator-roms packages.


Do you hesitate how to proceed with the migration? Please follow

https://docs.fedoraproject.org/en-US/legal/update-existing-packages/

or attend SPDX office hours (see different thread in this mailing list)

Miroslav


___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: It’s time to transform the Fedora devel list into something new

2023-04-23 Thread Roberto Ragusa


On 4/21/23 18:55, Jonathan Corbet wrote:

Matthew Miller  writes:


On Fri, Apr 21, 2023 at 08:45:31AM -0600, Jonathan Corbet wrote:

I will just make the point that, when you make this switch, you will be
missing people as well.  Projects that switch to forum systems, to a
great extent, go dark for people who aren't immersed in them all the
time.  Keeping up with fedora-devel takes very little of my time;
keeping up with Discourse instances is a much slower affair.


What could we do to make that easier for you?


A decent NNTP feed (or set of feeds) would be wonderful :)


If there will be a switch to a web based forum, I will be one of the
subscribers that will be lost.
Not sure if anybody cares, but I'm pointing it out since the proposal
aims at having more participants.
I've subscribed on 24/12/2005 and all the emails are in my IMAP
server, and accessed with Thunderbird.

Honestly, the NNTP feed is exactly what I would have answered too.

I understand the world changes, and the attraction of avatars,
and emojis powered by piles of javascript is unstoppable
to some people.
But from a marketing point of view it might not be the right
direction: Fedora is an old-style technical thing, there is
no point in chasing Ubuntu, everybody liking that kind of world
will surely prefer the original.

Last but not least, mailing lists are one of the ways we can try
keeping email service decently available to everybody, resisting
the trend to let only a few companies be "senders", so either
you write from gmail to gmail or you have to buy a "mail sending"
service to have your mails accepted by receivers.
It is bad enough already.

Regards.

--
   Roberto Ragusamail at robertoragusa.it
___
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 Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: RFC: No koji builds during mass branching and updates-testing enablement