Re: Unresponsive packagers: suanand and vponcova

[Jens-Ulrik Petersen]

I think for ex-redhatters it may be more appropriate to make a new bz
account for their new email address?

Jens

On Tue, May 7, 2024 at 2:11 PM Emmanuel Seyman  wrote:

> * Sundeep Anand [07/05/2024 05:50] :
> >
> > (not sure how to update email at bugzilla.redhat.com)
>
> Go to https://bugzilla.redhat.com/userprefs.cgi?tab=account and fill in
> the 'New email address' field.
--
___
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: Unresponsive packagers: suanand and vponcova

[Jens-Ulrik Petersen]

I cc'ed Sundeep (no longer in Red Hat for some time).

But I have been in contact with him recently and suggested to update his
email.

Jens

On Fri, May 3, 2024 at 4:59 PM Pierre-Yves Chibon 
wrote:

> Good Morning Everyone,
>
> We have been emailing daily the following users to notify that the email
> they
> have set in FAS does not correspond to a valid bugzilla account.
> This is a requirement for Fedora packagers.
>
> Does someone know how to contact them?
>
> suanand - emailed since April 5th
>
> suanand is maintainer of rpms/gettext
> suanand is main admin of rpms/php-gettext-gettext
>   rpms/php-gettext-gettext co-maintainers: @petersen
> suanand has a bugzilla override on rpms/php-gettext-gettext
> suanand is main admin of rpms/php-gettext-languages
>   rpms/php-gettext-languages co-maintainers: @petersen
> suanand has a bugzilla override on rpms/php-gettext-languages
> suanand is maintainer of rpms/python-polib
> suanand is maintainer of rpms/python-tinydb
> suanand is maintainer of rpms/translate-toolkit
> suanand is maintainer of rpms/transtats-cli
> suanand is maintainer of rpms/zanata-python-client
>
>
--
___
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: Files missing in RPM database

[Jens-Ulrik Petersen]

On Thu, May 2, 2024 at 1:21 AM Christoph Karl via devel <
devel@lists.fedoraproject.org> wrote:

> I tried to find out which files on my upgraded fc40 installation are not
> installed via dnf/rpm.
> The list is surprisingly long.
>

Perhaps you could upload the list to fedorapeople or somewhere?
Maybe also the script you used?

Main reasons are symlinks and directories not defined in the spec file.
> A quick check shows that this is also the case with a fresh installation.
--
___
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: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

https://botan.randombit.net/handbook/support.html#branch-support-status
can be referenced in the retirement commit:

Branch

First Release

End of Active Development

End of Life

Botan 1.8

2008-12-08

2010-08-31

2016-02-13

Botan 1.10

2011-06-20

2012-07-10

2018-12-31
(Though 1.11.x also exists, or was that a devel series for botan2?)
--
___
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: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

On Thu, Apr 4, 2024 at 12:51 AM Sandro  wrote:

> On 03-04-2024 18:35, Jens-Ulrik Petersen wrote:
> > I took botan [...]
>

I guess that was a bad idea - so I have re-orphaned it after some detailed
discussions with @penguinpee in #devel.
He also helped to decouple monotone from ikiwiki in rawhide, so the impact
should be less now.

The last botan-1.1 release was in 2018 and I think Debian/Ubuntu dropped
botan1 at the same time?
So it seems high time to remove this unmaintained version from Fedora too.
(We have botan2 in Fedora of course and I hope to see botan3 as well?)

It seems too late to do more on this for F40 now? or we would need an Final
Exception

Thanks, 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-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: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

I took botan as a penance for my sins in the previous thread ;-) haha 
--
___
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: F42 Change Proposal: Fedora Plasma Workstation (System-Wide)

[Jens-Ulrik Petersen]

On Wed, Apr 3, 2024 at 4:08 AM Steve Cossette  wrote:

> Alright, so a substantial amount of information changed since the original
> submission of the change proposal.
>
It did?  Because the page still reads:
*"Switch the default desktop experience for Workstation to KDE Plasma."*


> We aren't necessarily thinking of demoting Gnome.
>

And continues *"**The GNOME desktop is moved to a separate spin / edition,
retaining release-blocking status."*

Or are you saying you are planning to rewrite the page??

The overall spirit of the CP is that we think KDE, and to some extent the
> other spins too, need a bit more visibility on the website. At the very
> least, Gnome and KDE should be up front on the frontpage.
>

Asking to improve KDE's visibility on the website is certainly quite
different to replacing GNOME in Workstation.

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-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: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

On Wed, Mar 27, 2024 at 9:46 PM Miro Hrončok  wrote:

> On 25. 03. 24 7:48, Jens-Ulrik Petersen wrote:
> > Also botan got orphaned despite the FTI going away
> > <https://bugzilla.redhat.com/show_bug.cgi?id=2259559> [1] ;-(
> > Could it be un-orphaned back?
>
> > [1] Seems FTI failed to close the bug fixed on 2024-03-07
>
> It was closed after it was fixed. The update was stuck at beta freeze and
> nobody associated the FTI bugzilla with it.
>

No, it was reported <https://bugzilla.redhat.com/show_bug.cgi?id=2259559#c5>
installable (comment 5) on 7th March by fti-bugs but was not closed as it
should have been then.
Then it was orphaned
<https://bugzilla.redhat.com/show_bug.cgi?id=2259559#c6> (comment 6) on
21st March.
Then again reported <https://bugzilla.redhat.com/show_bug.cgi?id=2259559#c7>
installable (comment 7) on 25th which actually closed the bug.
Which is why I am asking if the orphaned can be reverted, please.

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-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: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

Also botan got orphaned despite the FTI going away
 [1] ;-(
Could it be un-orphaned back?

I really don't need another package, but if no one is willing to pick it
up, I can sit on it to prevent breaking monotone and ikiwiki, and above...

> Depending on: botan (13)

Jens
[1] Seems FTI failed to close the bug fixed on 2024-03-07
--
___
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: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

On Fri, Mar 22, 2024 at 12:22 AM Maxwell G  wrote:

> botan orphan   0 weeks
> ago


Is botan1 still considered safe?  Perhaps the python which causes the FTI
apparently could be removed?
Of course we have botan2 (but not botan3) in Fedora...

(I am asking because of ikiwiki, which doesn't require python.)

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-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: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

[Jens-Ulrik Petersen]

On Fri, Feb 9, 2024 at 8:05 PM Christopher Klooz  wrote:

> The package "pandoc" remains at 3.1.3 in Fedora, but pandoc is already at
> 3.1.11.1. Among the updates since 3.1.3, there have been two
> security-critical (including the medium CVE-2023-35936. Security fixes are
> in 3.1.4 & 3.1.6).
>
> The actual risk is limited, but these should be updated nevertheless.
>

Just noting here for the record too, that those pandoc CVEs are now fixed
with backports in Rawhide, and I will gradually push them back to current
releases in the near future.

Thanks, 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-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: pandoc-cli replaces the pandoc binary package in Rawhide

[Jens-Ulrik Petersen]

Based on feedback originally upstream (which prompted the upstream
pandoc-cli version bump and locking) and also similar feedback received
today on #devel,
I went ahead and renamed the binary package back to pandoc with version
3.1.3, to avoid further confusion by the pandoc-cli version drop.
So this is largely now just a packaging change and should hopefully be a
non-event for most fedora pandoc users and packagers.

Testing is still welcome though :-)

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-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

pandoc-cli replaces the pandoc binary package in Rawhide

[Jens-Ulrik Petersen]

Hi, Today I built the new pandoc-cli package into Rawhide, which replaces
the pandoc binary package: due to an upstream packaging change last year.
The accompanying pandoc build also fixes a couple of CVEs, so I will be
backporting this to F40 and F39 soon.

The current initial version is pandoc-cli-0.1.1.1 (previously bundled
within the F39+ pandoc package) but the package Provides: pandoc-3.1.3 and
Obsoletes older nvr's.

I am currently blocked for updating beyond pandoc-3.1.3 by missing deps
(see other recent threads here - particularly if you want to help with
reviewing).
Also note that from pandoc version 3.1.10 on, the pandoc-cli version is
locked to the pandoc version so any version ambiguity will go away at that
point: I certainly hope that will be in F41 at least.

/usr/bin/pandoc still reports its version as 3.1.3.
So yea, I am also pondering if it would make more sense if pandoc-cli just
provides a pandoc binary package instead.

Packagers can/may wish to use (Build)Requires: pandoc-cli instead of pandoc
in their packages going forward, though I would suggest to wait until the
packages are also built for branches.

Testing is very welcome since this is quite a large packaging change.
Let me know and report if you see any problems.

Thanks, 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-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 reviews for Pandoc and CVE-2023-35936

[Jens-Ulrik Petersen]

Hmm it looks like I really do need to update everything to LTS 22 to
achieve the pandoc rebase properly (since it needs newer Haskell tls).

Here's one more package review:

  toml-parser: https://bugzilla.redhat.com/show_bug.cgi?id=2266093

needed by the typst library.

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-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 reviews for Pandoc and CVE-2023-35936

[Jens-Ulrik Petersen]

Another day, another needed package (this would also be part of the
postponed Stackage LTS 22 change):
I forgot that pandoc > 3.1.3 had moved to the new crypton stack that
replaces cryptonite:

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

Next would be crypton-x509...

Is it better I just pump the whole stack straight to bz, though my
preference is to only open RRs which can actually build.
But if it is less painful to review them together/back-to-back I can pump
them out faster (maybe a few of the next crypto-x509-* packages can be done
in parallel).

Thanks, 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-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

package reviews for Pandoc and CVE-2023-35936

[Jens-Ulrik Petersen]

(changed the subject)

On Thu, Feb 22, 2024 at 9:14 PM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:

> On Thu, Feb 22, 2024 at 02:06:22PM +0800, Jens-Ulrik Petersen wrote:
> > I realised a second open package review is
> > https://bugzilla.redhat.com/show_bug.cgi?id=2068718 (isocline)
>
> Done.
>

Thank you very much, Zbigniew

Okay I have opened a crucial one:

https://bugzilla.redhat.com/show_bug.cgi?id=2265552 (pandoc-cli),

which will actually replace the pandoc binary package.

With this it will simplify the pandoc package further, since this package
depends on the pandoc library!

Jens

>
> zbyszek
> --
> ___
> 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
>


-- 

Jens Petersen

*he/him/his*

Associate Manager, Software Engineering
Display Systems Group & RHEL i18n Subsystem

Core Platforms - Global/Product Engineering

Singapore
<https://www.redhat.com>
--
___
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: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

[Jens-Ulrik Petersen]

On Sat, Feb 17, 2024 at 11:17 AM Michel Lind 
wrote:

> On Thu, Feb 15, 2024 at 07:53:38PM +, Christopher Klooz wrote:
> > On 14/02/2024 17.35, Michel Lind wrote:
> > > As a pandoc user, I'm happy to help with any reviews. Is there a list
> > > where this tends to get posted, apart from devel?
>

Thanks Michel for taking the base64 review.

I realised a second open package review is
https://bugzilla.redhat.com/show_bug.cgi?id=2068718 (isocline)
- it's a newer dep for pandoc (actually hslua-repl).

Was just wondering if there's another place where Haskell packaging is
> coordinated.


It is a good question...

I was trying to do that previously in the Haskell SIG (mailing list and
channel), but the traction became so low that I largely gave up with
that... other than occasionally begging someone specifically to help with
an urgent review. ;-(
I can certainly send out such mails there and/or here going forward for
more direct awareness.
(Not sure if it makes sense to post to Discourse: Haskell library reviews
are still a little bit "esoteric" since ghc uses some non-standard linking
(ie various warnings appear which tend to discourage/throw less experienced
reviewers alas: perhaps they should be spelled out further as exception(s)
in the Haskell Packaging policy, so I don't need to keep explaining them).

I will be posting more reviews soon: in particular a large bunch of hslua
related packages - though I think it is better to roll them out in reverse
dependency order.

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-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: Modern C failures in Haskell stack

[Jens-Ulrik Petersen]

Thanks Richard for the PR and Florian for the patch

On Thu, Feb 15, 2024 at 11:28 PM Richard W.M. Jones 
wrote:

> On Thu, Feb 15, 2024 at 12:57:21PM +0100, Florian Weimer wrote:
> > For the first issue, please try this GHC patch
>


> I submitted it to GHC here:
> https://gitlab.haskell.org/ghc/ghc/-/merge_requests/12079


The patch was approved upstream.

It should now be in the Rawhide buildroot as ghc-9.4.5-140.fc41
(Richard: hopefully also serves as a rebuild bump for riscv64)

Cheers, 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-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: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

[Jens-Ulrik Petersen]

Thanks for the support.

I will start to post more review requests, maybe post them on discourse
too...

Currently there is https://bugzilla.redhat.com/show_bug.cgi?id=2163472
(base64) which I opened 1 year ago.

Jens

On Fri, Feb 16, 2024 at 3:54 AM Christopher Klooz  wrote:

> On 14/02/2024 17.35, Michel Lind wrote:
>
> As a pandoc user, I'm happy to help with any reviews. Is there a list
> where this tends to get posted, apart from devel?
>
> Thanks,
>
> Michel
>
> Once the package needs a review, the request should be found here:
> http://fedoraproject.org/PackageReviewStatus/
>
> Details of the roles of "contributor" and "reviewer" in the "package
> review process" can be found here:
> https://docs.fedoraproject.org/en-US/package-maintainers/Package_Review_Process/
> (based upon its history, I expect this page is kept updated but I don't
> know for sure)
>
> According to the elaboration, you need to be in the FAS packager group,
> even for reviews.
>
> On Fri, Feb 09, 2024 at 11:26:33PM +0800, Jens-Ulrik Petersen wrote:
>
> I should also have added there's an increasing amount of technical debt
> with the pandoc packaging - I guess I need to beg people to help with
> package reviews: also reminded of our packaging (review) streamlining
> discussion from Flock last year.
>
> Jens
>
> On Fri, 9 Feb 2024, 23:23 Jens-Ulrik Petersen,  
>  wrote:
>
>
> Hello I am here - thanks for contacting me.
>
> I was hoping to cover this as part of my F40 Change, but unfortunately I
> haven't gotten to it, so the Change is now at risk of being deferred to F41.
>
> Nevertheless I will see what I can do about this for F40: maybe a backport
> can also be done for F39.
>
> Next time you could also comment on the relevant 
> bug:https://bugzilla.redhat.com/show_bug.cgi?id=1996301 - that would be
> appreciated.
>
> Thanks, Jens
>
> PS Special thanks to Neal Gompa for pinging me in Matrix. 
>
>
> On Fri, 9 Feb 2024, 20:05 Christopher Klooz,  
>  wrote:
>
>
> I cannot reach the maintainer petersen (see mail below): The package
> "pandoc" remains at 3.1.3 in Fedora, but pandoc is already at 3.1.11.1.
> Among the updates since 3.1.3, there have been two security-critical
> (including the medium CVE-2023-35936. Security fixes are in 3.1.4 & 3.1.6).
>
> The actual risk is limited, but these should be updated nevertheless.
>
> Does anyone know how to reach him by other means?
>
> Regards,
> Chris
>
>
>  Forwarded Message 
> Subject: Fedora package "pandoc" outdated and contains security
> vulnerability
> Date: Thu, 1 Feb 2024 15:55:09 +0100
> From: py0...@posteo.net
> To: peter...@fedoraproject.org
>
> Hi petersen,
>
> I am reaching out because of the package "pandoc", which you maintain.
>
> I have seen that the package is still at version 3.1.3 [1] when I tried
> to install it with dnf, whereas the current version is 3.1.11.1 [2]: is
> this intended or an accident?
>
> It has to be noted that the updates that have been added in the meantime
> contain fixes for security vulnerabilities (at least CVE-2023-35936; I have
> just roughly skimmed the changelogs). So at the moment, it seems the Fedora
> build can be exploited by attackers in some circumstances [3] [4] because
> it is still at 3.1.3.
>
> Regards & thanks for maintaining,
>
> Chris
>
> [1] https://koji.fedoraproject.org/koji/packageinfo?packageID=11560
>
> [2] https://hackage.haskell.org/package/pandoc &https://github.com/jgm/pandoc
>
> [3] https://github.com/jgm/pandoc/releases?page=1
>
> [4] https://github.com/jgm/pandoc/releases?page=2
>
> --
> ___
> 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
>
> --
> ___
> 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 sp

Re: Modern C failures in Haskell stack

[Jens-Ulrik Petersen]

Thank you for looking into this, much appreciated,
since I hadn't found proper time yet.

It might be helpful to have a downstream ghc bug to track this too.

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-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: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

[Jens-Ulrik Petersen]

I should also have added there's an increasing amount of technical debt
with the pandoc packaging - I guess I need to beg people to help with
package reviews: also reminded of our packaging (review) streamlining
discussion from Flock last year.

Jens

On Fri, 9 Feb 2024, 23:23 Jens-Ulrik Petersen,  wrote:

> Hello I am here - thanks for contacting me.
>
> I was hoping to cover this as part of my F40 Change, but unfortunately I
> haven't gotten to it, so the Change is now at risk of being deferred to F41.
>
> Nevertheless I will see what I can do about this for F40: maybe a backport
> can also be done for F39.
>
> Next time you could also comment on the relevant bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1996301 - that would be
> appreciated.
>
> Thanks, Jens
>
> PS Special thanks to Neal Gompa for pinging me in Matrix. 
>
>
> On Fri, 9 Feb 2024, 20:05 Christopher Klooz,  wrote:
>
>> I cannot reach the maintainer petersen (see mail below): The package
>> "pandoc" remains at 3.1.3 in Fedora, but pandoc is already at 3.1.11.1.
>> Among the updates since 3.1.3, there have been two security-critical
>> (including the medium CVE-2023-35936. Security fixes are in 3.1.4 & 3.1.6).
>>
>> The actual risk is limited, but these should be updated nevertheless.
>>
>> Does anyone know how to reach him by other means?
>>
>> Regards,
>> Chris
>>
>>
>>  Forwarded Message 
>> Subject: Fedora package "pandoc" outdated and contains security
>> vulnerability
>> Date: Thu, 1 Feb 2024 15:55:09 +0100
>> From: py0...@posteo.net
>> To: peter...@fedoraproject.org
>>
>> Hi petersen,
>>
>> I am reaching out because of the package "pandoc", which you maintain.
>>
>> I have seen that the package is still at version 3.1.3 [1] when I tried
>> to install it with dnf, whereas the current version is 3.1.11.1 [2]: is
>> this intended or an accident?
>>
>> It has to be noted that the updates that have been added in the meantime
>> contain fixes for security vulnerabilities (at least CVE-2023-35936; I have
>> just roughly skimmed the changelogs). So at the moment, it seems the Fedora
>> build can be exploited by attackers in some circumstances [3] [4] because
>> it is still at 3.1.3.
>>
>> Regards & thanks for maintaining,
>>
>> Chris
>>
>> [1] https://koji.fedoraproject.org/koji/packageinfo?packageID=11560
>>
>> [2] https://hackage.haskell.org/package/pandoc &
>> https://github.com/jgm/pandoc
>>
>> [3] https://github.com/jgm/pandoc/releases?page=1
>>
>> [4] https://github.com/jgm/pandoc/releases?page=2
>>
>> --
>> ___
>> 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
>>
>
--
___
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: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

[Jens-Ulrik Petersen]

Hello I am here - thanks for contacting me.

I was hoping to cover this as part of my F40 Change, but unfortunately I
haven't gotten to it, so the Change is now at risk of being deferred to F41.

Nevertheless I will see what I can do about this for F40: maybe a backport
can also be done for F39.

Next time you could also comment on the relevant bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1996301 - that would be
appreciated.

Thanks, Jens

PS Special thanks to Neal Gompa for pinging me in Matrix. 


On Fri, 9 Feb 2024, 20:05 Christopher Klooz,  wrote:

> I cannot reach the maintainer petersen (see mail below): The package
> "pandoc" remains at 3.1.3 in Fedora, but pandoc is already at 3.1.11.1.
> Among the updates since 3.1.3, there have been two security-critical
> (including the medium CVE-2023-35936. Security fixes are in 3.1.4 & 3.1.6).
>
> The actual risk is limited, but these should be updated nevertheless.
>
> Does anyone know how to reach him by other means?
>
> Regards,
> Chris
>
>
>  Forwarded Message 
> Subject: Fedora package "pandoc" outdated and contains security
> vulnerability
> Date: Thu, 1 Feb 2024 15:55:09 +0100
> From: py0...@posteo.net
> To: peter...@fedoraproject.org
>
> Hi petersen,
>
> I am reaching out because of the package "pandoc", which you maintain.
>
> I have seen that the package is still at version 3.1.3 [1] when I tried to
> install it with dnf, whereas the current version is 3.1.11.1 [2]: is this
> intended or an accident?
>
> It has to be noted that the updates that have been added in the meantime
> contain fixes for security vulnerabilities (at least CVE-2023-35936; I have
> just roughly skimmed the changelogs). So at the moment, it seems the Fedora
> build can be exploited by attackers in some circumstances [3] [4] because
> it is still at 3.1.3.
>
> Regards & thanks for maintaining,
>
> Chris
>
> [1] https://koji.fedoraproject.org/koji/packageinfo?packageID=11560
>
> [2] https://hackage.haskell.org/package/pandoc &
> https://github.com/jgm/pandoc
>
> [3] https://github.com/jgm/pandoc/releases?page=1
>
> [4] https://github.com/jgm/pandoc/releases?page=2
>
> --
> ___
> 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
>
--
___
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: F40 Change Proposal: Optimized Binaries for the AMD64 Architecture (System-Wide)

[Jens-Ulrik Petersen]

We don't generally use/talk about amd64 in Fedora, so I was a bit thrown by
the naming of this Change.
I don't want to start a skirmish about amd64 vs x86_64, but iiuc this
Change is not AMD specific
so by now I personally feel x86-64 actually kinda sounds more neutral in
this sense
(I am aware that deb based distros favor "amd64" and some may consider it
more "PC").
Perhaps you could consider changing the naming in the title?

Further the text already talks a lot about x86-64-v{1,2,3,4}...
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-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 Linux 37 is EOL

[Jens-Ulrik Petersen]

(Replying to devel list)

Can someone please update
https://docs.fedoraproject.org/en-US/releases/eol/#_unsupported_fedora_linux_releases
to correct the EOL date for F37 to 5th Dec?

Or should I open a releng ticket for that?

Thanks!
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-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: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

I took ghc-X11-xft and vala-language-server for now (would welcome
comaintainers).

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-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: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

On Mon, Nov 6, 2023 at 7:32 PM Miro Hrončok  wrote:

> llvm12orphan, petersen, sergesanspaille
> 4 weeks ago
> llvm13jistone, orphan, petersen, sergesanspaille
>  4 weeks ago
>

I took these as usual.

At least llvm12 is still needed on aarch64 and s390x:

$ fdrq -q -a aarch64 rawhide --whatrequires llvm12 | grep -v llvm12
ghc8.10-compiler-8.10.7-12.fc40.aarch64 (fedora-rawhide-aarch64)
ghc9.0-compiler-9.0.2-14.fc39.aarch64 (fedora-rawhide-aarch64)
$ fdrq -q -a s390x rawhide --whatrequires llvm12 | grep -v llvm12
ghc9.2-compiler-9.2.8-21.fc39.s390x (fedora-rawhide-s390x)

Jens

ps You can try fedora-repoquery from this copr repo
.
___
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: Donate 1 minute of your time to test upgrades from F38 to F39

[Jens-Ulrik Petersen]

On Thu, Aug 24, 2023 at 2:23 AM Miroslav Suchý  wrote:
:

> dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
>
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo
> --enablerepo=updates-testing-modular) \
> --assumeno distro-sync
>

So are the F39M modular repos empty?? (since I thought they were being
removed)
Maybe they have to stay around for F39 to allow smooth upgrades, is that
the point?

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-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: F39 Change Proposal: Haskell GHC 9.4 and Stackage LTS 21 (Self-Contained)

[Jens-Ulrik Petersen]

This Change proposal is really mostly informational...
I know it's only 9 days since it was announced, but with Flock around the
corner and
the Testable deadline fast approaching the following week,
it would really help me if this could get a formal green light soon to go
ahead.

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-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 39 Mass Rebuild

[Jens-Ulrik Petersen]

On Wed, Jul 26, 2023 at 5:56 PM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:

> I submitted
> https://pagure.io/fesco/issue/3043 Change: Migrate NetworkManager ifcfg
> profiles to keyfile
> https://pagure.io/fesco/issue/3044 Change: IBus 1.5.29
> https://pagure.io/fesco/issue/3045 Change: GNU Toolchain Update (gcc
> 13.2, binutils 2.40, glibc 2.38, gdb 13.2)
> to push things through fesco. But I did not very well, e.g. I didn't
> update the categories in the wiki.


Just noting that in https://fedoraproject.org/wiki/Category:ChangeAnnounced
the following proposed System Wide Changes are also still waiting to go to
Fesco:

   - https://fedoraproject.org/wiki/Changes/Color_Bash_Prompt
   - https://fedoraproject.org/wiki/Changes/Indic_Noto_fonts
   - https://fedoraproject.org/wiki/Changes/MigrateIfcfgToKeyfile

as well as 3 Self-Contained Changes.

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-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: Flock CFP: Language SIGs discussion

[Jens-Ulrik Petersen]

On Thu, Jul 13, 2023 at 6:11 PM Miroslav Suchý  wrote:

> Dne 13. 07. 23 v 10:45 Florian Festi napsal(a):
> > As it is relevant for this meeting may be someone that attended my
> > workshop can give a 3 or 5 minute summary of the new Dynamic Spec
>
> I can volunteer. I was on your workshop and I will be at Flock.


Sure, thank you - that would be useful :up:

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-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: Flock CFP: Language SIGs discussion

[Jens-Ulrik Petersen]

On Fri, Jul 14, 2023 at 12:56 AM Ron Olson  wrote:

> There isn’t a SIG, and I don’t know if there’s any interest really, but
> I’d be happy to tell my tales of packaging Swift for Fedora. :\
>

Sure, such perspectives are definitely also welcome - this will be a broad
discussion.
In many cases the hurdles are even bigger with the newest developing
languages, where typically one finds that even the core/compiler's
buildsystem etc even does not cater well to distro needs in my experience.


Btw this cross-SIG community roundtable discussion has been scheduled

for the first morning and I'm really looking forward to a good vigorous
conversation with broad participation.
Do reach out to me by reply or chat if you want to help out and be more
involved.

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-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: F39 Change Proposal: Color Bash Prompt (System Wide)

[Jens-Ulrik Petersen]

On Fri, Jul 7, 2023 at 7:38 PM Vít Ondruch  wrote:

> Dne 05. 07. 23 v 11:25 Aoife Moloney napsal(a):
> > https://fedoraproject.org/wiki/Changes/Color_Bash_Prompt
> :
>
> There seems to be a general desire to have a colored prompt like other
> > popular distros, which commonly use green
>


> Shouldn't blue be the default for Fedora?
>

(In some palettes the visibility of cyan text on white background is really
poor
and similarly blue text is often hard to make out on black background.)

We could try PROMPT_COLOR='46' which would give us a prompt with cyan
background.
Background prompt color actually achieves better contrast and stands out
more I feel:

https://petersen.fedorapeople.org/color-bash-prompt-cyan-dark.png
https://petersen.fedorapeople.org/color-bash-prompt-cyan-light.png

It has the advantage of not looking like colored text output by some
commands:
e.g. dnf may print packages in green. I personally use a prompt background
color
for good contrast.

And I think that dark as well as light color schemes should be
> considered. IOW I appreciate the screenshot attached above, but could
> you also attach one with the light scheme? Thx a lot.


Okay, I have added a link to a light gnome-terminal screenshot too on the
page.
https://petersen.fedorapeople.org/color-bash-prompt-light.png

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-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: F39 Change Proposal: Color Bash Prompt (System Wide)

[Jens-Ulrik Petersen]

On Fri, Jul 7, 2023 at 9:36 PM Marián Konček  wrote:

> I actually copy-paste the Debian prompt since Debian Jessie on my systems.
> Even though it uses blue-green colors, I can see it very well on both
> white and black background.
>

Okay


> I think it would be nicer if we played around with several options and
> have the user have a simple way of choosing.
>

They *can* set PROMPT_COLOR to change coloring immediately.
But it would be nice to have a configuration tool/UI some day.

> There are many variants, some using git info, some using exit codes and
> so...


Exit code is already handled in the current implementation.
I would like to make it more extensible in the future...

But I made a criteria that this simple MVP should not use PROMPT_COMMAND
nor should the default PS1 cause *any* external process to run by default.
So anyway this Change is not setting the bar very high, by design:
there are certainly lots of more powerful solutions around
like powerline or starship etc, and this Change is not competing with them.
:-)
The hope is that a simple conservative solution like this would be broadly
acceptable as a desktop default.

Thanks, 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-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: F39 Change Proposal: Color Bash Prompt (System Wide)

[Jens-Ulrik Petersen]

Thanks for the replies so far.

Unfortunately there is no easy way to detect dark or light terminals, to my
knowledge at least.
Green seems the most friendly color across different palettes and terminals.
Though these days modern terminals tend to default to dark
(most Fedora editions' default terminals are dark by default I think).

https://copr-dist-git.fedorainfracloud.org/cgit/petersen/bash-color-prompt/bash-color-prompt.git/tree/bash-color-prompt.sh
lists various examples of how users can customize the color: eg
PROMPT_COLOR='33' (for yellow/brown).
___
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: Flock CFP: Language SIGs discussion

[Jens-Ulrik Petersen]

Oops, somehow I forgot Ruby -- anyway all Lang ecosystem SIGs participation
to welcome and encouraged of course.

On Wed, 5 July 2023, 14:22 Jens-Ulrik Petersen,  wrote:

> I have submitted a Flock proposal to have a common discussion session for
> (modern) Language SIGs. I think for this to be successful we need
> representatives from various Language SIGs to be there (Rust, Haskell,
> OCaml, Golang and of course Python and older ecosystems like Perl, R, TeX
> come to mind immediately - surely there are more). Language packaging
> experts are also welcome of course independently or affiliated to one or
> more language SIGs. Of course I also hope there will be broad attendance by
> interested contributors.
>
> The idea is to talk about common and distinct problems faced, both to
> learn from each other and to come up with practical ideas and plans for
> generally easing Fedora's mass packaging efforts.
>
> If you plan to be at Flock and are willing and able to represent your
> Language SIG at this Flock session do please reply or reach out to me. I
> think each SIG could do a brief presentation there to kick off the dialogue.
>
> Thanks, 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-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

Flock CFP: Language SIGs discussion

[Jens-Ulrik Petersen]

I have submitted a Flock proposal to have a common discussion session for
(modern) Language SIGs. I think for this to be successful we need
representatives from various Language SIGs to be there (Rust, Haskell,
OCaml, Golang and of course Python and older ecosystems like Perl, R, TeX
come to mind immediately - surely there are more). Language packaging
experts are also welcome of course independently or affiliated to one or
more language SIGs. Of course I also hope there will be broad attendance by
interested contributors.

The idea is to talk about common and distinct problems faced, both to learn
from each other and to come up with practical ideas and plans for generally
easing Fedora's mass packaging efforts.

If you plan to be at Flock and are willing and able to represent your
Language SIG at this Flock session do please reply or reach out to me. I
think each SIG could do a brief presentation there to kick off the dialogue.

Thanks, 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-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: more distinct default bash prompt?

[Jens-Ulrik Petersen]

So I made a copr repo PoC:

https://copr.fedorainfracloud.org/coprs/petersen/bash-color-prompt/

which you can test: the bash-color-prompt package there drops a
conditionalized PS1 into /etc/profile.d/ for now.

$ sudo dnf-3 copr enable petersen/bash-color-prompt
$ sudo dnf install bash-color-prompt

This shouldn't really be the final solution though - I would like it to be
available by default (even if turned off), but at least this allows more
user-testing now in different scenarios.

The prompt is similar to the one from my original post and can still be
"user-themed" with PROMPT_COLOR: it now defaults to normal green and adds the
red error code from Stephan (maybe this part could still be improved?) -
both now non-bright/bold.

https://copr-dist-git.fedorainfracloud.org/cgit/petersen/bash-color-prompt/bash-color-prompt.git/tree/

I can create a proper github or even pagure repo later if needed, but right
now I feel it would be helpful to have more user-feedback first.
I am happy to adapt this into a F39 Change (it could be monochrome by
default if pre-installed) if people want that: I feel it is only really
compelling if integrated into default desktop installations in some form.

Jens
ps It would be nice to support toolbox/containers too (like $debian_chroot) and
have opt-in for git branch too, but those could be added later I think.
Also a root color perhaps, as discussed.

pps I did test dim reverse-video but it looks quite stark in a light
terminal.
___
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: more distinct default bash prompt?

[Jens-Ulrik Petersen]

Late follow-up...

On Tue, May 30, 2023 at 2:46 AM Peter Oliver <
lists.fedoraproject@mavit.org.uk> wrote:

> On Fri, 26 May 2023, Björn Persson wrote:
>
> > One way to avoid all the color issues could be to just make the prompt
> > bold by default. That would probably make it stand out enough in many
> > situations. I think it wouldn't help much for programmers compiling
> > software though, because GCC outputs filenames in uncolored bold text,
> > so even a bold prompt would blend in among the compilation errors.
>

Right, true


> Underlining or reverse video would get my vote, instead of bold.
>

I did play with reverse video before my original post, and found it rather
"high contrast" - though it may deserve more exploration.
Dim reverse video seems more palatable perhaps.


> For myself, I have a more complicated scheme that sets the prompt
> background colour to light grey on light terminals and dark grey on dark
> terminals.  I find this is just enough to easily find the prompt when
> scrolling back, without distracting from the output I’m looking at.  My
> instinct is that detecting the background colour too fiddly to inflict on
> users by default, though.


Yes, setting the background and foreground together is probably the safest
way to maintain good contrast.

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-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: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

On Thu, Jun 8, 2023 at 7:47 PM Omair Majid  wrote:

> Not an expert, just a casual Urdu speaker with a drive by contribution.
> I don't write Urdu much these days but I can read it.
>

Cool

Akira TAGOH  writes:
> > I have no idea if Noto Sans Arabic or Noto Naskh Arabic is qualified
> > for Urdu and Punjabi.  Even though they have minimal coverage in
> > fontconfig perspective, there might be minor differences which look
> > strange for native speakers like punctuation marks in CJK etc.
>

Right, Noto Naskh Arabic could also be an option perhaps.


> I looked through the Urdu bits using
> https://fonts.google.com/noto/specimen/Noto+Naskh+Arabic and things
> generally look okay. All the letters used in Urdu (~40, which is more
> than ~30 used in Arabic) seem to be present. The text is legible and
> readable. I tried a few punctuation marks and they are getting rendered
> in a way I can read it.
>

Good to know, thanks

What would be really helpful is to know how it compares with other Naskh
fonts
like Paktype (current default) and Nafees, and even Noto Nastaliq Urdu
(they are all in Fedora 38).

Thanks, 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-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: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

Actually nafees-naskh-fonts would need some font config to become default.
So I guess the easiest thing is indeed to unretire the old default package.
___
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: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

I suggest we can go with nafees-naskh-fonts for now.

Though we should have caught some of the paktype fonts anyway. :-(
___
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: more distinct default bash prompt?

[Jens-Ulrik Petersen]

Also while we are bike-shedding... What about \W vs \w ?
I think fedora has used \W "forever" - I am not a huge fan...
though I suppose its main merit is not over-flowing/extending for very long
dir paths.
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-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: more distinct default bash prompt?

[Jens-Ulrik Petersen]

On Tue, May 23, 2023 at 12:47 PM Neal Gompa  wrote:

> I actually would prefer that we color both, and make it obvious that
> "root" is special. We should account for common color-blindness
> issues, though.


Sure, I think I agree: perhaps purple for root?

I am all for "color blind testing" (though I am not completely sure that
"color-blind" is the right term here
though I am not an a11y expert - I thought color blind is more about
differentiating different colors like green and red,
but if you mean visual impairment/contrast/readability then I completely
agree).
I think in the end it will come down also to wider user testing since there
are so many different terminals
and color palettes around.

Anyway that's why I proposed green since it seems to have reasonable
contrast for both light and dark terminals (unlike blue/cyan/yellow often).
I assume that may also be why Ubuntu and Nixos went with green.

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-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: more distinct default bash prompt?

[Jens-Ulrik Petersen]

On Mon, May 22, 2023 at 1:49 PM Dridi Boukelmoune <
dridi.boukelmo...@gmail.com> wrote:

> On Mon, May 22, 2023 at 3:50 AM Jens-Ulrik Petersen 
> wrote:
> > For example I could suggest we change the default fedora bash prompt
> from:
> > PS1="[\u@\h \W]\\$ "
> > to something like:
> > PS1="\[\e[\${PROMPT_COLOR}m\][\u@\h \W]\[\e[0m\]\\$ ".
>
> Maybe make it ${PROMPT_COLOR:-1;32} to have a default value without
> polluting the environment?


Thanks for the suggesion

Personally I think that's reasonable: however I was also being cautious in
the sense of making it easy for people to opt out of the color prompt.
Also it is not really pollution: PROMPT_COLOUR is actually used for each
prompt and in theory it could be changed dynamically (maybe by
PROMPT_COMMAND etc, shrug?).
But if there is broad consensus wouldn't mind I guess.

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-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: disabling Haskell i686 packages

[Jens-Ulrik Petersen]

Thanks, Florian, very good point.

On Thu, May 18, 2023 at 7:12 PM Florian Weimer  wrote:

> I think this will make quite a few packages FTBFS on i686 because they
> require pandoc at build time.  It's not that many—I count ~75 that
> build-depend on something pandoc-ish without also build-depending on
> something ghc-ish.  The actual number will be lower once we stop
> building noarch packages on i686 (not yet implemented as far as I know).
> And there are probably some packages which build-depend indirectly on
> ghc.


Then I guess it will have to wait then.
It is not that big a deal yet: though a few i686 issues are slowly starting
to creep in for a few Haskell packages.

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-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

more distinct default bash prompt?

[Jens-Ulrik Petersen]

In Fedora the bash prompt is not colored or highlighted by default.

I personally find this a usability issue: it makes it hard to find previous
commands between long outputs when scrolling back in a terminal.  Of course
in my own host I have a custom prompt, but it means whenever I am using a
different Fedora/Centos/RHEL system or vm, the prompt is not highlighted by
default, which I miss.

Since I spent a little time thinking about and investigating this I thought
I would write to start a discussion here.

I noticed that Ubuntu has a bold green and blue prompt and NixOS has a
green one by default, though not Archlinux or OpenSuSE I think.

I think it would be nice to have a distinctive prompt by default, or at
least a very easy way to get one permanently (ie in a single command: even
if that were `dnf install bash-color-prompt` or running say `colorprompt`
once).

For example I could suggest we change the default fedora bash prompt from:
PS1="[\u@\h \W]\\$ "
to something like:
PS1="\[\e[\${PROMPT_COLOR}m\][\u@\h \W]\[\e[0m\]\\$ ".

Then the PROMPT_COLOR envvar would make it easy for users to change or
customize their prompt coloring anyway.
For example with PROMPT_COLOR="1;32" one gets a bold green prompt, which
seems readable in both dark or light terminals.

What do people think overall? Are there other pros and cons of a color
prompt?
Any better ideas or direction?

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-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

disabling Haskell i686 packages

[Jens-Ulrik Petersen]

We have been building i386 packages for ghc and Haskell for a long time,
but I think it is time to stop for Fedora 39. So as part of F39 Haskell
updates, I plan to disable 32bit ix86 builds across all the packages: I
doubt anyone is still using them anyway.

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-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: F36 is End of Life

[Jens-Ulrik Petersen]

On Wed, May 17, 2023 at 5:32 AM Samyak Jain  wrote:

> On the other hand, Fedora Linux f37 will continue to receive updates until
> approximately one month after the release of Fedora Linux f38.
>

Sorry, but that should say "one month after the release of Fedora Linux f
*39*".

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-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: F39 Proposal: LIBFFI34 static trampolines (System-Wide Change)

[Jens-Ulrik Petersen]

On Thu, May 11, 2023 at 7:27 AM DJ Delorie  wrote:

> Jens-Ulrik Petersen  writes:
> > I have just now pushed fixes for all ghc*, so can you try to rebuild
> > them again in your repo?
>
> That's a good question, to which I know not the answer.  Fred?  Can MPB
> be told to retest a specific set of packages?  Or do I have to start
> from scratch and/or do them manually?i18n Engineering - Display Systems


Well, it is "only" ghc, ghc9.0, ghc9.2, and ghc9.6 (though ideally the
ghc-* and other Haskell packages should also be built against the rebuilt
ghc package).
You could also just build them manually in your djdelorie/libffi-3.4.4 copr
or in a separate copr if that is cleaner.

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-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: disabling yum modular repos by default?

[Jens-Ulrik Petersen]

On Wed, May 10, 2023 at 8:39 PM Debarshi Ray via devel <
devel@lists.fedoraproject.org> wrote:

> On Tue, 2023-05-09 at 12:31 +0800, Jens-Ulrik Petersen wrote:
> If we do decide to disable the fedora-cisco-openh264 repository on the
> base fedora OCI image, then we might have to enable it separately for
> the fedora-toolbox images, because the OpenH264 codec is something that
> applications running inside the container might want to use.


Right, so I already dropped that idea based on the feedback given so far,
thanks. :+1:

An initial draft (I will rename the page later before submitting) is here
btw for those really interested:
https://fedoraproject.org/wiki/Changes/TurnOffModularRepos
(At this point I would probably prefer critical feedback/suggestions in
private until it is submitted. :-)

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-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: F39 Proposal: LIBFFI34 static trampolines (System-Wide Change)

[Jens-Ulrik Petersen]

On Wed, May 10, 2023 at 3:13 AM DJ Delorie  wrote:

> Jens-Ulrik Petersen  writes:
> MPB uses BuildRequires to collect all packages that *might* be affected
> by your change.  It builds all those packages with and without your
> change, and lets you know what you broke.  In this case, one broke (cjs,
> since fixed), ten didn't build before my change anyway[*], and the rest
> were OK.  So if your package doesn't already FTBFS, you're good.
>

Okay thanks for the clarification and explanations.
(I got now that by "affected packages" you didn't mean "failed":)

"after" builds:
> https://copr.fedorainfracloud.org/coprs/djdelorie/libffi-3.4.4/


Okay I was already aware of all the ghc failures: mostly due to the new
sphinx version in Rawhide
(which I had already fixed for ghc9.4). So it looks fine from my pov so
far, thanks.
I have just now pushed fixes for all ghc*, so can you try to rebuild them
again in your repo?
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-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: disabling yum modular repos by default?

[Jens-Ulrik Petersen]

Thanks for all the helpful comments and feedback,
though more is still welcome of course.
So I am leaning now towards not installing fedora-repos-modular by default
(rather than disabling the modular repos by default): also for upgrade
compatibility.

I have started a Change proposal draft, which I think should be ready soon,
with current working title *"Turn off modular dnf repos by default"*.
Perhaps *"No default fedora-repos-modular"* would be more precise.
Or any better suggestions (that don't sound like modularity is being
removed)?

I think the actual work (PR's) required is not huge,
but if someone is particularly keen to join the effort let me know.

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-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: F39 Proposal: LIBFFI34 static trampolines (System-Wide Change)

[Jens-Ulrik Petersen]

On Tue, May 9, 2023 at 12:18 PM Jens-Ulrik Petersen 
wrote:

> On Tue, May 9, 2023 at 4:35 AM DJ Delorie  wrote:
>
>> According to mpb at least:
>>
>
(Okay I found mpb <https://gitlab.com/fedora/packager-tools/mass-prebuild>)
Are the results available?


> The majority of those packages are maintained by me... so I can't say I
> thrilled.
> I thought ghc 9 was supposed to be okay with static trampolines?
>
___
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

disabling yum modular repos by default?

[Jens-Ulrik Petersen]

I have been thinking about proposing a Change to Fedora 39,
which would disable yum modular repos by default in installs.
I thought I would float the idea here first.

I suspect the vast majority of Fedora users don't use
the modular repos, so I don't see the point of enabling
them by default anymore. Does this make sense?

I know dnf5 is coming with performance improvements
but I still think turning off the modular repos would speed up dnf
and save users a lot of time.

Jens (pulling his flame-wear closer :)

ps I think it would be a good idea to disable the cisco-h264 repo too by
default in the fedora container image, and maybe also for headless Fedora
editions.
___
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: F39 Proposal: LIBFFI34 static trampolines (System-Wide Change)

[Jens-Ulrik Petersen]

On Tue, May 9, 2023 at 4:35 AM DJ Delorie  wrote:

> According to mpb at least:
>

mpb?

The majority of those packages are maintained by me... so I can't say I
thrilled.
I thought ghc 9 was supposed to be okay with static trampolines?
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-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

GHC 9.2 is now in F38 and Rawhide

[Jens-Ulrik Petersen]

I am pleased to announce the arrival of ghc version 9 (9.2.6) and Haskell
packages based on Stackage LTS 20 versions in Rawhide and F38
.

This landed in f38 and f39 today for
https://fedoraproject.org/wiki/Changes/Haskell_GHC_9.2_and_Stackage_20.

With ghc 9.2 there are some significant performance improvements
particularly for aarch64 (with its new Native Code Generator compilation
times are now on par with Intel arch's) and also s390x gains a llvm
backend, which also improves build times a lot. (ppc64le is now the slowest
ghc arch in current Fedora). Also Haskell packages' modules are now built
in parallel in Koji for further build speed ups.

There are still a small handful of packages which didn't build yet, which I
will be sorting in the next days (the only significant ones are the gi-gtk
and dhall stacks).

If you see any problems please let me know or open a bug.

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-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

help needed with 2 haskell package reviews

[Jens-Ulrik Petersen]

Hi, I would really like these two packages added to F38:

NEW ghc-constraints: https://bugzilla.redhat.com/show_bug.cgi?id=2162872
NEW ghc-base64: https://bugzilla.redhat.com/show_bug.cgi?id=2163472

both are needed by newer pandoc and a number of other packages.

Can anyone please help review them?

Thanks, 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-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: List of long term FTBFS packages to be retired next week

[Jens-Ulrik Petersen]

On Mon, Feb 6, 2023 at 6:50 PM Vít Ondruch  wrote:

> Dne 06. 02. 23 v 1:13 Georg Sauthoff napsal(a):
> > Judging from the FTBFS mail/Bugzilla/
> https://src.fedoraproject.org/rpms/datamash it
> > looks like jhladky (Jiri Hladky) currently is the sole maintainer?
>
> You are looking at the right place. Or you can use the API:
>
[snip]

You can also install and use the pagure-cli tool: it defaults to this
server and outputs the json with yaml like this:

$ pagure project datamash
fullname: rpms/datamash
parent: null
close_status: []
namespace: rpms
url_path: rpms/datamash
access_users:
  owner:
  - jhladky
  ticket: []
  admin: []
  collaborator: []
  commit: []
priorities: {}
access_groups:
  ticket: []
  admin: []
  collaborator: []
  commit: []
name: datamash
full_url: https://src.fedoraproject.org/rpms/datamash
id: 24246
date_modified: '1569590838'
milestones: {}
user:
  fullname: Jirka Hladky
  url_path: user/jhladky
  name: jhladky
  full_url: https://src.fedoraproject.org/user/jhladky
custom_keys: []
date_created: '1503079151'
description: The datamash package
tags: []
___
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: List of long term FTBFS packages to be retired in February​

[Jens-Ulrik Petersen]

On Mon, Jan 30, 2023 at 9:26 AM Jens-Ulrik Petersen 
wrote:

> On Mon, Jan 30, 2023 at 4:09 AM Miro Hrončok  wrote:
>
>> On 29. 01. 23 18:15, Jens-Ulrik Petersen wrote:
>> > llvm11   jistone, petersen,
>> sergesanspaille, tstellar
>> > llvm12   petersen,
>> sergesanspaille,tstellar
>>
>
These have been built now already for Rawhide (along with llvm13) and
building now for current releases too.
Big thank you to Jerry James for his assistance - much appreciated.

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-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: List of long term FTBFS packages to be retired in February​

[Jens-Ulrik Petersen]

On Mon, Jan 30, 2023 at 6:47 PM Florian Weimer  wrote:

> * Jens-Ulrik Petersen:
> > which are still needed by various packages, the latter also including
> > ghc8.10-compiler.aarch64, ghc9.0-compiler.aarch64,
> > ghc9.2-compiler.s390x, and ghc9.4-compiler.s390x
>
> Isn't the LLVM code generator optional for GHC?  Could you just disable
> it?


No, it depends on the arch: it is needed for arm for ghc < 9.2 and for
s390x for ghc > 9.2.
___
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: List of long term FTBFS packages to be retired in February​

[Jens-Ulrik Petersen]

On Mon, Jan 30, 2023 at 4:09 AM Miro Hrončok  wrote:

> On 29. 01. 23 18:15, Jens-Ulrik Petersen wrote:
> > I would like to request exemptions for:
> >
> > llvm11   jistone, petersen,
> sergesanspaille, tstellar
> > llvm12   petersen,
> sergesanspaille,tstellar
> >
> > which are still needed by various packages, the latter also including
> > ghc8.10-compiler.aarch64, ghc9.0-compiler.aarch64,
> ghc9.2-compiler.s390x, and
> > ghc9.4-compiler.s390x
>
> Could you please open a ticket at https://pagure.io/fesco/issues


Sure, I just opened https://pagure.io/fesco/issue/2947


> Do you happen to know why the llvm versions haven't been built/buildable
> since F35?


Various tedious build errors on different archs, which don't look fun to
fix.
If someone has ideas and even better time to help, that would be really
great.

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-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: List of long term FTBFS packages to be retired in February​

[Jens-Ulrik Petersen]

On Tue, Jan 24, 2023 at 10:56 PM Miro Hrončok  wrote:

> If you see a package that should be exempted from the process,
> please let me know and we can work together to get a FESCo approval for
> that.


I would like to request exemptions for:

llvm11   jistone, petersen,
> sergesanspaille, tstellar
> llvm12   petersen, sergesanspaille,
> tstellar
>

which are still needed by various packages, the latter also including
ghc8.10-compiler.aarch64, ghc9.0-compiler.aarch64, ghc9.2-compiler.s390x,
and ghc9.4-compiler.s390x

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-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: List of long term FTBFS packages to be retired in February

[Jens-Ulrik Petersen]

On Wed, Jan 11, 2023 at 8:59 PM Miro Hrončok  wrote:

> llvm10   petersen, sergesanspaille
>
Probably okay to drop at this point.

> llvm11   jistone, petersen, 
> sergesanspaille,
> tstellar
> llvm12   petersen, sergesanspaille,
> tstellar
>
These two are also still in use by ghc for some archs: aarch64 (ghc,
ghc8.10, ghc9.0) and s390x (ghc9.2 and ghc9.4).
Though I am planning to move them to only llvm12 at least for F38.

Anyway I think I may be able to workaround these by disabling the testsuite
probably...

llvm9.0  jistone, petersen, tstellar

I think this could be retired now.  At least I am not aware of any
remaining dependents.

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-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: updating cmark to 0.30

[Jens-Ulrik Petersen]

On Tue, Jan 17, 2023 at 3:38 PM Milan Crha  wrote:

> On Tue, 2023-01-17 at 13:55 +0800, Jens-Ulrik Petersen wrote:
> > So I plan to go ahead with this rebase and rebuilding these packages
> > after the mass rebuild if that's okay.
>
> Hi,
> does the new version change any API and/or soname version?
>

I don't think so and the test results look quite good actually (only
neochat fails due to cmark-0.30.2):
https://copr.fedorainfracloud.org/coprs/petersen/cmark/monitor/
(I think upstream is a bit conservative with still linking the SONAME to
the version.)

so I think we can go ahead and push this to rawhide.


> > We can consider whether to backport to F37 and possibly F36 if needed
> > afterwards.
>
> I do not think you should change API/soname version in stable releases,
> that can lead to trouble (for example for 3rd-party packages).


You are right - let's not plan to do that yet, though I know one new
dependent package newly needs 0.30.

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-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

updating cmark to 0.30

[Jens-Ulrik Petersen]

Currently we have an old version of cmark in Fedora: version 0.29.

I had several requests to update it to the latest release 0.30.2 from 2021.
https://bugzilla.redhat.com/show_bug.cgi?id=1974335

I created a copr repo for testing:
https://copr.fedorainfracloud.org/coprs/petersen/cmark/

>From my repoquerying I think the following fedora packages depend on cmark:

evolution-3.47.1-1.fc38.src.rpm
gnome-builder-43.4-3.fc38.src.rpm
mkvtoolnix-73.0.0-1.fc38.src.rpm
neochat-22.11-2.fc38.src.rpm
nheko-0.11.0-1.fc38.src.rpm
perl-Clownfish-CFC-0.6.3-17.fc37.src.rpm
perl-CommonMark-0.29-13.fc37.src.rpm
So I plan to go ahead with this rebase and rebuilding these packages after
the mass rebuild if that's okay. We can consider whether to backport to F37
and possibly F36 if needed afterwards.

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-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: Web Assembly on Fedora: interested in a Fedora SIG to work on this?

[Jens-Ulrik Petersen]

Just noting that initial wasm support also just got merged upstream for ghc
9.6.

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-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: Red Hat Bugzilla fonts

[Jens-Ulrik Petersen]

I think good to open a bug against the Bugzilla product in bugzilla.

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-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: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

On Mon, Oct 31, 2022 at 8:39 PM Miro Hrončok  wrote:

> llvm11.0  orphan, tstellar 3 weeks
> ago
>

(Just noting that llvm11.0 should indeed be retired as it's an unwanted
duplicate of the Fedora llvm11 package.)
___
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: F38 proposal: Node.js Repackaging (Self-Contained Change proposal)

[Jens-Ulrik Petersen]

On Fri, Sep 16, 2022 at 1:14 AM Stephen Gallagher 
wrote:

> As I'm implementing this, I'm realizing that it probably only makes
> sense to have the default version of Node.js on each Fedora release
> provide the unversioned-command. Otherwise it becomes really hard to
> ensure that the RPM macros like %{nodejs_sitelib} refer to the correct
> location. So I think I'll stick with "if you're packaging for Fedora,
> it has to work on the default Node release *or* you must deal with
> everything yourself if you need to run on a different runtime".


Sounds reasonable (as a non-nodejs user:)

For our Haskell ghc, the new ghcX.Y packages introduced since F36 have
given a big improvement in flexibility in my opinion.
The main Fedora ghc package provides /usr/bin/ghc by default, though the
ghcX.Y packages do have an optional unversioned subpackage for it that
conflicts with ghc.
So users are normally expected just to use the default version or specify
the wanted version, unless they really want to default to a newer (or older
in the future) one instead.

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-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: F37 proposal: Emacs 28 (Self-Contained Change proposal)

[Jens-Ulrik Petersen]

Hi Göran,

Also did you see https://bugs.launchpad.net/vm/+bug/1979048 ?
It might help you.

On Tue, Aug 9, 2022 at 4:56 PM Göran Uddeborg  wrote:

> My package (emacs-vm) was one of the ones that broke with the upgrade
> to Emacs 28 in F36. I'm trying to get it to work again.
>
> One of the issues is that it shows up a large number of warnings.
> After some time I've now understood this is because of the new native
> compilation feature. Since my package doesn't include any *.eln files
> and Emacs will do the compilation on first use, and put in the home
> directory. The VM package has a lot of old code that triggers
> warnings. Previously those have only shown up at build time, and I
> have hoped for upstreams to some day fix them. Now they will also show
> up at run time, which obviously is a more annoying user experience.


Do you want to try adding native compilation your package?

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-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: F37 proposal: Emacs 28 (Self-Contained Change proposal)

[Jens-Ulrik Petersen]

On Tue, Aug 9, 2022 at 4:56 PM Göran Uddeborg  wrote:

> That brought up a question: what should Emacs add-on packages do when
> it comes to native compilation? Should they build and bundle native
> code? If I understand it correctly, that would mean a new patch build
> of Emacs itself would also require a rebuild of all add-on packages.
> Or should we let Emacs recompile native files at run time? That would
> make the recompilation at Emacs upgrades automatic, but it would on
> the other hand put a copy of all used libraries in each user's home
> directory.
>

Good point - I feel it probably makes sense yes.


> I checked the packaging guidelines
> (https://docs.fedoraproject.org/en-US/packaging-guidelines/Emacs/) but
> it didn't mention anything around this as far as I could tell. (It
> still talks about xemacs which has been retired from the distribution,
> which tells me it hasn't been updated very recently.)


If there is consensus on native compilation of elisp packages,
then the Emacs guidelines should indeed be updated.
I guess then the packages would become arch'ed.

I feel the bigger problem is that many of the emacs lisp packages in Fedora
are out of date.
The general recommendation is to use Emacs' own packaging system(s) to
install elisp,
though I appreciate some people may prefer to use a distro package.

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-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: List of long term FTBFS packages to be retired in 1 week

[Jens-Ulrik Petersen]

On Mon, Aug 1, 2022 at 8:56 PM Miro Hrončok  wrote:

> xs   petersen


Thanks, I finally retired this one already.

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-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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F37 proposal: Emacs 28 (Self-Contained Change proposal)

[Jens-Ulrik Petersen]

>From the 28.1 NEWS file: this seems to be a breaking change:

** The WHEN argument of 'make-obsolete' and related functions is mandatory.
> The use of those functions without a WHEN argument was marked obsolete
> back in Emacs 23.1.  The affected functions are: 'make-obsolete',
> 'define-obsolete-function-alias', 'make-obsolete-variable',
> 'define-obsolete-variable-alias'.
>

which if I am not wrong probably caused several of emacs-* packages to
FTBFS in the mass rebuild.
(Unfortunately the build.log's only refer to the line-number in the elisp
files: dunno if that can be improved?)

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-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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F37 proposal: Emacs 28 (Self-Contained Change proposal)

[Jens-Ulrik Petersen]

On Tue, Jul 19, 2022 at 5:14 AM Marcus Müller  wrote:

> Since the pgtk toolkit supports both X and wayland under the hood, I'd
> very much propose
> that we do not only package an emacs-pgtk binary, but also, that it
> becomes what you get
> by default (i.e. when you install and run `emacs`).


Good catch, but it looks to me like pgtk was deferred to Emacs 29!
Seems it is not actually part of 28.

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-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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F37 Change: Drop i686 builds of jdk8,11,17 and latest (18) rpms from f37 onwards (System-Wide Change)

[Jens-Ulrik Petersen]

Has a bug been filed against subversion (and other low-lying deps) yet?
(I could not see any bug and wondering why not?)

Naively it looks like the filed bugs are more targeting higher dependent
packages which is less useful.
I think it is the immediate dependencies like subversion (and possibly some
of their direct dependents) which need the most immediate attention.
Filing bugs against many higher dependent packages first seems a bit
premature yet and creates confusion for many packagers.

I think the thread "You can't be serious! you want to remove
mesa-libGL.i686 support?" summarizes the problem better,
but I wanted to make sure the problem is mentioned clearly here in this
Change thread too.

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-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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F37 Change Proposal: Firefox Langpacks Subpackage (System-Wide Change)

[Jens-Ulrik Petersen]

On Thu, Jun 30, 2022 at 2:27 AM Vitaly Zaitsev via devel <
devel@lists.fedoraproject.org> wrote:

> On 29/06/2022 19:00, Vipul Siddharth wrote:
> > Firefox langpacks, which have been bundled in the Fedora firefox base
> > package until now, will be moved to a firefox-langpacks subpackage.
>
> +1. It might be better to split it even more: firefox-langpack-%{lang}
> and depend on the system-wide language (just like spelling dictionaries).
>
> Users will be able to install only the required locales.
>

Right, I am aware of that.

One problem is that the number of firefox langpacks changes somewhat over
releases,
so Martin was hesitant to take this approach in the past.  Probably still
applies.
So the proposed approach seems like a reasonable compromise and step
forward.

(I have pondered if we could decide on a set of core firefox langpacks
which are "guaranteed" to exist
and so hopefully could be safely subpackaged - but this makes the handling
more complicated
and delicate - it would have to be done very carefully in langpacks.)

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-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 on the list, report it: 
https://pagure.io/fedora-infrastructure

[headsup] ghc-8.10.7 + Stackage lts-18.28 landed in Rawhide

[Jens-Ulrik Petersen]

Hi,
Just a heads-up to say that Haskell ghc in Rawhide has been updated from
8.10.5 to 8.10.7, and Haskell package versions have been updated to the
final versions in Stackage lts-18.28.

See https://bodhi.fedoraproject.org/updates/FEDORA-2022-3ae019aee4

These package versions should act as a base for Epel 9 Haskell (which
already has ghc-8.10.7).

Let me know if you notice any problems.

It is planned to further update Rawhide to ghc-9.0.2 and Stackage lts-19
before the F37 mass-rebuild.

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-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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F37 proposal: Enhance Persian Font Support (Self-Contained Change proposal)

[Jens-Ulrik Petersen]

I am also curious how the Vazirmatn font compares with Noto Naskh Arabic,
and also the old Dejavu coverage?
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

On Mon, Mar 7, 2022 at 5:42 PM Miro Hrončok  wrote:

> ghc-dbus  orphan   0 weeks
> ago
> ghc-libxml-saxorphan   0 weeks
> ago


I took these two.

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-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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Non-responsive maintainer check for nim

[Jens-Ulrik Petersen]

Adding an alternative address for Nicolas too, just to be sure.

On Fri, Feb 4, 2022 at 7:08 PM Miro Hrončok  wrote:

> There seem to be a common knowledge that nim has quit Fedora around a year
> ago.
>
> This is the mandatory email required by
>
> https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
>
> Nonresponsive bugzilla:
> https://bugzilla.redhat.com/show_bug.cgi?id=2050622
>
> I am required to ask if anyone knows how to contact the maintainer, so
> consider
> that done.
>
> My real question is, do you know if they really quit?
>
> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> ___
> 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 on the list, report it:
> https://pagure.io/fedora-infrastructure
>


-- 

Jens Petersen

*he/him/his*

Associate Manager, Software Engineering

Linux Engineering - i18n

Singapore

___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

On Tue, Feb 8, 2022 at 3:52 AM Miro Hrončok  wrote:

> perl-HTML-Tidy gnat, jplesnik, mmaslano, mspacek,  0 weeks
> ago
> orphan, ppisar
>

Anyone interested in keeping 'ikiwiki' and 'perl-Text-Markdown' around?

The following packages require above mentioned packages:
> Report too long, see the full version at
> https://churchyard.fedorapeople.org/orphans-2022-02-07.txt
>
> See dependency chains of your packages at
> https://packager-dashboard.fedoraproject.org/
> See all orphaned packages at
> https://packager-dashboard.fedoraproject.org/orphan
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F37 Change: RetireARMv7 (System-Wide Change proposal)

[Jens-Ulrik Petersen]

Thank you, Peter, for coming up with this!

I have to say this is really good news to hear indeed - I have been waiting
silently for this for quite a long time.

Kudos, 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-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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F36 Change: GHC compiler parallel version installs (Self-Contained Change proposal)

[Jens-Ulrik Petersen]

On Fri, Dec 24, 2021 at 11:49 AM Tom Stellard  wrote:

> On 12/13/21 08:56, Ben Cotton wrote:
> > https://fedoraproject.org/wiki/Changes/GHC_parallel_version_installs
> >
> > == Summary ==
> > Introduce ghcX.Y packages to Fedora which can be parallel installed,
> > in addition to the main ghc package.
> :

> == Detailed Description ==
> > Currently ghc modules are available in Fedora but they cannot be
> > installed in parallel.
>
> What is the plan for the ghc modules?


It's a good question: I kind of avoided going into detail on this point in
the Change,
since I was not intending to remove/drop the modules just yet.
In the meantime I have added an optional ghcX.Y-compiler-default subpackage
which allows making ghcX.Y the default ghc too though, so with that
the modules no longer seem to provide any advantage.
If there are no strong objections I think I will probably drop the modules
before F37 anyway.
But I didn't really want to frame this Change as "demodularization", but I
will concede that
maintaining the modules has been more stressful than I would like to admit.
Most likely I will also switch EPEL to using ghcX.Y instead of modules.

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-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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F36 Change: GHC compiler parallel version installs (Self-Contained Change proposal)

[Jens-Ulrik Petersen]

On Wed, Dec 22, 2021 at 11:00 PM Neal Gompa  wrote:

> So will the default version be the "ghc" package going forward?


That's correct - general Haskell users/consumers should just continue to
use the main ghc package and ghc-* libraries.

ghcX.Y is for people who need/want to use or test different (newer/older)
ghc versions,
rather like the compatibility llvmX packages.
ghc9.2 is already available in Rawhide and F35 updates testing, and ghc9.0
should be available soon too.


> How will defaults be handled in future Fedora Linux releases?


The main Fedora ghc package will continue to be maintained and upgraded
along with the ecosystem.
It is not completely clear yet if the ghc package set will move to ghc-9.0
in time for F36 GA, otherwise hopefully to ghc-8.10.7.
ghcX.Y can also provide a better testing ground for packaging improvements
(than the ghc modules) before they land in the main ghc package.
It will make new minor ghc versions more easily available in Fedora (and
EPEL where ghcX.Y will be even more meaningful).

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-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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Orphaned packages looking for new maintainers​

[Jens-Ulrik Petersen]

On Mon, Oct 25, 2021 at 6:43 PM Miro Hrončok  wrote:

> ghc-HStringTemplate   orphan   2 weeks
> ago
> ghc-filestore orphan   2 weeks
> ago
> ghc-hoauth2   orphan   2 weeks
> ago
> ghc-recaptcha orphan   2 weeks
> ago
> ghc-uri   orphan   2 weeks
> ago
> ghc-uri-bytestring-aeson  orphan   2 weeks
> ago
> ghc-url   orphan   2 weeks
> ago
> gitit orphan   2 weeks
> ago


I went ahead and took these.
But if anyone is keen to help maintain any of them, don't hesitate to let
me know.

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-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 on the list, report it: 
https://pagure.io/fedora-infrastructure

haskell ghc-8.10 is now in rawhide

[Jens-Ulrik Petersen]

On behalf of the Haskell SIG I am pleased to announce that
in F35 Rawhide ghc has been updated from 8.8.4 to 8.10.5 and
Haskell packages from Stackage LTS 16 to 18.5 versions.

This is for https://fedoraproject.org/wiki/Changes/GHC_8.10_%26_Stackage_18
and has many important version updates including:

ghc: 8.8.4 -> 8.10.5
cabal-install: 3.0.0.0 -> 3.2.0.0
stack: 2.3.3 -> 2.7.3
hlint: 3.1.6 -> 3.2.7
ormolu: 0.1.3.0 -> 0.1.4.1

pandoc: 2.9.2.1 -> 2.14.0.3

Agda: 2.6.1.2 -> 2.6.2
bustle: 0.7.5 -> 0.8.0
darcs: 2.14.4 -> 2.16.4
dhall: 1.32.0 -> 1.39.0
dhall-json: 1.6.4 -> 1.7.7
hadolint: 1.18.2 -> 2.6.1
hakyll: 4.13.4.0 -> 4.14.0.0
haskell-gi: 0.24.7 -> 0.25.0
hledger: 1.18.1 -> 1.21
xmobar: 0.36 > 0.38
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure

dropping pt-sans-fonts (ParaType Cyrillic) from the default @fonts group?

[Jens-Ulrik Petersen]

Oops sorry resending to the correct devel list:

-- Forwarded message -
From: Jens-Ulrik Petersen 
Date: Mon, Jun 28, 2021 at 1:38 PM
Subject: dropping pt-sans-fonts (ParaType Cyrillic) from the default @fonts
group?
Cc: fonts , trans <
tr...@lists.fedoraproject.org>

Hi

Currently the pt-sans-fonts package is installed by default as part of the
@fonts yum group.

However as far as I can tell, e.g. looking at
https://tagoh.fedorapeople.org/fonts/status/34.html the font is not used by
default for any of our locales.

Therefore unless there is a strong reason to keep it pre-installed I would
like to propose dropping pt-sans-fonts from @fonts in F35. Obviously we
still have Cyrillic coverage provided by deja-sans-fonts. Any feedback on
this? Note also that langpacks-ru pulls in pt-sans-fonts.

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-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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

On Wed, May 19, 2021 at 4:06 AM Miro Hrončok  wrote:

llvm10orphan, sergesanspaille  1 weeks
> ago
> llvm9.0   jistone, orphan, tstellar5 weeks
> ago


I have taken these two.

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-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 on the list, report it: 
https://pagure.io/fedora-infrastructure

aajohan-comfortaa-fonts and julietaula-montserrat-fonts

[Jens-Ulrik Petersen]

Hi,

For quite a while both aajohan-comfortaa-fonts and
julietaula-montserrat-fonts have been installed by default in the @fonts
package group.

In the Fedora I18n subproject we are currently reviewing
 and documenting
 the set of default
installed fonts and wondering if these two fonts need to be installed by
default or not?

It seems these fonts are mostly used for Design? So maybe they could be
pulled in by the packages that typically need them instead or moved to a
different package group in comps?

Before going any further though it would be good to hear if users feel
these fonts really should be installed by default or whether they could
just be optional? They are not causing any problems that I know of, but on
the other hand if they are not needed then it would be tidier to not
install them by default.

Thanks, 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-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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 34 Change: fbrnch (Self-Contained Change proposal)

[Jens-Ulrik Petersen]

On Wed, Jan 20, 2021 at 11:31 PM Jens-Ulrik Petersen 
wrote:

> On Tue, Jan 19, 2021 at 1:38 AM Zbigniew Jędrzejewski-Szmek <
> zbys...@in.waw.pl> wrote:
>
>> > ** Submit and complete package review(s).
>>
>
I still need one more package review completed before I can build fbrnch in
Rawhide and submit it's review:

ghc-pretty-terminal (NEW)
https://bugzilla.redhat.com/show_bug.cgi?id=1925891
If anyone can help review it, that would be great.

Thanks, 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-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

Re: Fedora 34 Change: fbrnch (Self-Contained Change proposal)

[Jens-Ulrik Petersen]

On Tue, Jan 19, 2021 at 1:38 AM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:

> > Add the [https://github.com/juhp/fbrnch fbrnch] packager tool to Fedora.
>
> Sounds good ;)
>
> > ** Submit and complete package review(s).
>
> Links?
>

Thanks - I will try to get those posted soon.
Or for the initial Fedora package versions I might put some of the Fedora
web services bindings into fbrnch in the first instance to avoid the extra
packaging overhead for now.

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-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

Re: Fedora 34 Change: Localization measurement and tooling (Self-Contained Change proposal)

[Jens-Ulrik Petersen]

> https://fedoraproject.org/wiki/Changes/LocalizationMeasurementAndTooling

It would be good to at least mention Transtats on the Change page as a
related project.

Jens

On Fri, Jan 15, 2021 at 4:52 AM Jean-Baptiste Holcroft <
jibec...@fedoraproject.org> wrote:

> Transtats covers 100 packages, while the change darknao and I do the
> following (stats are for f33):
>
> * use dnf to download all srpm for a fedora relaese (21330 packages)
> * detect po files (2230 packages have at least one po file, more file
> format exists, but it will be for the future ;))
> * extract all po files (200 337 po files)
> * deduct language list (344 languages)
> * produce stats and consolidated files (16GB of files before compression)
> * publish a website (2 GB once files are compressed)
>
> The Transtats UI is good, but it really is focused on translation
> propagation accross system, bringing a huge complexity.
> Sometimes we can't prevent complexity, but I don't really understand the
> main goal/use case transtats want to answer.
> It may simply solve issues I don't have.
>
> I'm really happy of the discussion we are having through this change
> process, I think we should use change process more often!
>
___
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

Re: Fedora 34 Change: Localization measurement and tooling (Self-Contained Change proposal)

[Jens-Ulrik Petersen]

I think it is really worth mentioning here that Transtats
 already provides a lot of
Fedora translation statistics and info.
There is certainly more that could be done and we would like to do, to
enhance it further...
While I know Jean-Baptiste is not a fan and has his own approach here, the
overlap in effort does make me sad.

I also want to call out and thank Jean-Baptiste for all the awesome work he
has done on migrating Fedora L10n to Weblate.

Thank you, 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-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

Re: Fedora 34 Change: Stop Shipping Individual Nodejs Library Packages (Self-Contained)

[Jens-Ulrik Petersen]

On Thu, Dec 10, 2020 at 3:52 AM James Cassell 
wrote:

> On Wed, Dec 9, 2020, at 1:44 PM, Ben Cotton wrote:
> > https://fedoraproject.org/wiki/Changes/NodejsLibrariesBundleByDefault



> Is there really no better solution?


A general comment: I feel it is a shame that more language ecosystems don't
provide source distributions of packages.

The only one I am really aware of is Stackage 
for Haskell (about ~2500 compatible packages from Hackage
).
I know this is not easy and does not come for free, but I am surprised
there is not more demand for package sets.
It would certainly be a big win for distro packaging.

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-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

announce: rhbzquery

[Jens-Ulrik Petersen]

Hi, I want to announce another small tool I made called rhbzquery
.
It generates bugzilla query urls (and can open them automatically) like
this:

$ rhbzquery f33 kernel summary=network
https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__=Fedora=33=kernel=short_desc=substr=network

If you want to try it you can install it from:
https://copr.fedorainfracloud.org/coprs/petersen/rhbzquery/
Suggestions for improvements are welcome.
I hope it will be useful for some people.

Thanks, 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-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

Re: Reducing noise on devel list

[Jens-Ulrik Petersen]

Fwiw I have been filtering out the rawhide report to a separate folder for
years...

I mean I originally did it for the opposite reason: I wanted to be able to
find the reports without all the other devel discussions.

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-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

Re: List of long term FTBFS packages to be retired in a week

[Jens-Ulrik Petersen]

On Tue, Jul 28, 2020 at 5:58 PM Miro Hrončok  wrote:

> ghc-pretty-show (maintained by: mathstuf)
> ghc-pretty-show-1.9.5-3.fc32.x86_64 requires js-jquery1 =
> 1.12.4-7.fc30
>

I fixed this in ghc-pretty-show-1.10-2.fc33 two weeks ago btw.
___
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

Re: ghc-cryptonite LTO failure on s390x

[Jens-Ulrik Petersen]

Hi Elliot, thanks for the heads up:

On Mon, Aug 3, 2020 at 8:12 AM Elliott Sales de Andrade <
quantum.anal...@gmail.com> wrote:

> The build for ghc-cryptonite failed in the mass rebuild [1] and a
> later rebuild by me [2], but only on s390x. The failure appears to be
> LTO related. This doesn't appear to affect many other Haskell
> packages. (I've found one seemingly-related failure in
> ghc-haskell-src-exts [3].) Since it's Haskell, I'm using the standard
> macros that should pass consistent flags, etc., so I'm not sure what
> more information I can provide.
>
> What happens is that ld.gold warns about mixed LTO/non-LTO:
>
Yeah this seems to be affecting profiling libraries (ghc-*-prof.s390x).

[2] https://koji.fedoraproject.org/koji/taskinfo?taskID=48408236


I opened https://bugzilla.redhat.com/show_bug.cgi?id=1863601 using the
output from this build.

For now I am going to workaround this by disabling LTO for s390x Haskell
packages in ghc-rpm-macros.
I think when we move to ghc-8.10 for F34 we can hopefully switch s390x to
llvm10 which should make this problem go away.

Thanks, 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-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

Re: List of long term FTBFS packages to be retired in August

[Jens-Ulrik Petersen]

On Tue, Jul 21, 2020 at 7:11 AM Miro Hrončok  wrote:

> ghc-pretty-show (maintained by: mathstuf)
> ghc-pretty-show-1.9.5-3.fc32.x86_64 requires js-jquery1 =
> 1.12.4-7.fc30


Turns out the upstream bundling already moved to jquery 3.3, so I am fixing
this.

On the other hand, I don't have a good feel for jquery3 compatibility:
is it a safe bet to assume 3.5 should be compatible with 3.3.1?

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-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

Re: Fedora 33 Self-Contained Change proposal: GHC 8.8 and Haskell Stackage LTS 16

[Jens-Ulrik Petersen]

On Fri, Jun 26, 2020 at 10:44 PM Ben Cotton  wrote:

> https://fedoraproject.org/wiki/Changes/GHC_8.8_and_LTS16


On behave of the Haskell SIG I am happy to announce that ghc-8.8.4 and
Stackage 16.5 based Haskell packages have now been pushed to Rawhide.

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-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