Fedora-Legal-README.txt in installation media outdated?

[Qiyu Yan]

If you download a Fedora 34 live iso at https://getfedora.org/
with filename: Fedora-Workstation-Live-x86_64-34-1.2.iso

Mount it and see Fedora-Legal-README.txt in the image. There are many
Fedora 31 things show up, should this file be updated on each release
cycle?

(Maybe not, unless someone like me mounts the iso file by mistake, and
check the Legal file by curiosity LOL)

--
Part of the file:
The accompanying Fedora 31 release includes copyrighted
software that is licensed under the GNU General Public License and
other licenses. You may obtain the complete machine-readable source
code corresponding to portions of this release by sending a check or
money order in the amount of US $5.00 to:

VP, Legal - Products & Technologies | Red Hat, Inc. | 100 East Davie
Street | Raleigh, NC 27601 USA

Please write "source for Fedora 31" in the memo line of your payment.

You may also access a copy of this source code at:
http://dl.fedoraproject.org/pub/fedora/linux/releases/31/Everything/source/

-- 
Qiyu Yan
GPG keyid: 0x4FC914F065F2DF12






signature.asc
Description: This is a digitally signed message part
___
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

Orphaning xfontsel

[Peter Hutterer]

I've orphaned xfontsel, one of the many possibly-older-than-thou X
utilities. From the man page: 

  xfontsel - point and click selection of X11 font names

So it does support both point *and* click. Futuristic stuff indeed ;)

Package is here if you want to take it:
https://src.fedoraproject.org/rpms/xfontsel

Cheers,
   Peter
___
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: Thoughts about packaging a standalone python-PyQt5-sip?

[Scott Talbert]

On Tue, 27 Apr 2021, Kevin Fenzi wrote:


I'd be able and willing to assist here too, thanks for working on it!

As far as sip6 goes, I'd venture the adjustment from v5 to v6 will be
smaller than what v4 to v5 was.


Yeah, agreed.

Happy to work with you both and get this done. :)


Okay, I'll work on dusting off my existing work, refreshing it, and get 
in touch with you guys.


Scott
___
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: Dynamic preemption support in Linux 5.12 kernel

[Justin Forbes]

On Tue, Apr 27, 2021 at 2:30 PM Chris Murphy  wrote:
>
> I created a Fedora Workstation issue to track the progress, and figure
> out if any or all of the desktops want to do full preemption by
> default.
> https://pagure.io/fedora-workstation/issue/228

Unless I missed a commit, it is x86_64 only so far.

Justin
___
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: New RPM submission

[Emmanuel Seyman]

* Joan Moreau [27/04/2021 20:51] :
>
> Hi Emmanuel
> 
> I am trying my best to foloow the process but I get nowhere
> 
> Now I get a "koji" error ("AuthError: unable to obtain a session")

That looks like a recurring kerberos issue.

https://pagure.io/koji/issue/2063
https://pagure.io/releng/issue/7522

You probably want to contact releng to help solve this.

> I tried "fedpkg request-repo --exception dovecot-fts-xapian" -> Lead some
> error ("fedpkg request-repo --exception dovecot-fts-xapian")

Why is this package exempt from the review process?

> I filed a "bug" on redhat :
> https://bugzilla.redhat.com/show_bug.cgi?id=1953340
> 
> And now, how to get things moving ?

You need to seek out a sponsor:
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group

> Isnt' there just a repo where to push the RPM ? (similar to Arch)

There is COPR but I suspect this is reserved to Fedora packagers so you
will still need to be sponsored.

https://fedoraproject.org/wiki/Category:Copr

Emmanuel
___
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: [Input Requested] Preset support for third-party services

[Dominik 'Rathann' Mierzejewski]

On Tuesday, 27 April 2021 at 21:14, Stephen Gallagher wrote:
> I originally raised this as a question to FESCo[1], but I was asked to
> bring it up on the Fedora Devel list. My apologies for taking so long
> to get around to it.
> 
> While looking into a preset request, I realized that the guidelines[2]
> do not say anything at all about enabling default services that are
> not packaged in Fedora.
> 
> For a specific example: suppose that a particular VM host provides its
> guest tools only as a closed-source binary that they ship. Do we
> permit them to request the inclusion of their service in presets under
> the reasoning that it would enhance users' performance on those
> systems, or do we disallow any non-Fedora software from being included
> in the presets?
> 
> What about a third-party repository that provides a closed-source
> service that enhances an open-source project (for example, a
> closed-source codec server that works with open-source encoding
> software)?

Our SELinux policy contains rules for software not included in Fedora,
including some proprietary software, so I would say we have a precedent
in other areas.

If the service in question follows the rules then I don't see why it
cannot be included.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
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: Bacula 11.0.2-3 for Fedora 33?

[John Florian]

On 4/27/21 1:52 PM, Steven A. Falco wrote:
> On 4/27/21 5:14 AM, Paul Howarth wrote:
>> On Sun, 25 Apr 2021 11:17:49 -0400
>> "Steven A. Falco"  wrote:
>>> Are there any additional instructions on how to update the bacula
>>> database?
>>
>> Normally I would use /usr/libexec/bacula/update_mysql_tables but I
>> found in this case that it didn't work because it was trying to drop an
>> index from a table that didn't already exist (the index, not the
>> table).
>
> Thanks for the reply.  I turned out to be able to run:
>
> /usr/libexec/bacula/update_bacula_tables
>
> I'm using postgresql, and the script did manage to update the
> database.  And as you say, it took a long time.
>
> Then, I was getting failures from bacula that it couldn't insert into
> the File area, and I found that I additionally had to re-run:
>
> grant_bacula_privileges
>
> Once I did that, it all started working.

Thank you for this!  I too am using postgresql and I also had simply ran
/usr/libexec/bacula/update_bacula_tables.  Things looked ok until I
tried a test restore:

Building directory tree for JobId(s) 15256,15739,15762 ...  Query
failed: DECLARE _bac_cursor CURSOR FOR SELECT Path.Path, T1.Filename,
T1.FileIndex, T1.JobId, LStat, DeltaSeq  FROM ( SELECT DISTINCT ON
(Filename, PathId, DeltaSeq) JobTDate, JobId, FileId, FileIndex, PathId,
Filename, LStat , DeltaSeq FROM (SELECT FileId, JobId, PathId,
Filename, FileIndex, LStat ,DeltaSeq FROM File WHERE JobId IN
(15256,15739,15762) UNION ALL SELECT File.FileId, File.JobId, PathId,
Filename, File.FileIndex, LStat , DeltaSeq FROM BaseFiles JOIN File
USING (FileId) WHERE BaseFiles.JobId IN (15256,15739,15762) ) AS T JOIN
Job USING (JobId) ORDER BY Filename, PathId, DeltaSeq, JobTDate DESC  )
AS T1 JOIN Path ON (Path.PathId = T1.PathId) WHERE FileIndex > 0 ORDER
BY T1.JobTDate, FileIndex ASC: ERR=ERROR:  permission denied for table file

However, once I ran /usr/libexec/bacula/grant_bacula_privilege, that
problem was solved.  From what I can see, everything is working fine now.

John Florian

___
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: KDE Autostart in F34

[Benjamin Berg]

On Tue, 2021-04-27 at 20:03 +, Ravindra Kumar wrote:
> > This desktop file need to be replaced by the systemd-user unit,
> > IMO.
> 
> Thanks Vitaly. We will look into converting it to systemd-user unit.
> I believe that would work for all other desktop managers as well.

Yeah, you might want to ship both a systemd unit and an XDG autostart
file for the time being. There will still be graphical desktops
environments which are not started using systemd in the foreseeable
future.

If you decide to ship both, please add X-GNOME-HiddenUnderSystemd=true
and X-systemd-hidden=true to the desktop file to prevent the service
from getting started twice.

If the ExitType= patch fixes this, then the problem is that the
generated service does not handle forking services right now and it
will work fine with systemd v249 and later.

Benjamin


signature.asc
Description: This is a digitally signed message part
___
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: KDE Autostart in F34

[Ravindra Kumar]

> This desktop file need to be replaced by the systemd-user unit, IMO.

Thanks Vitaly. We will look into converting it to systemd-user unit. I believe 
that would work for all other desktop managers as well.

Thanks,
Ravindra
___
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: KDE Autostart in F34

[Ravindra Kumar]

> I commented in the bug with some debugging steps to try.

Thanks Rex. We can discuss this further in the bug.

Thanks,
Ravindra
___
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: New RPM submission

[Joan Moreau via devel]

Hi Emmanuel

I am trying my best to foloow the process but I get nowhere

Now I get a "koji" error ("AuthError: unable to obtain a session")

I tried "fedpkg request-repo --exception dovecot-fts-xapian" -> Lead 
some error ("fedpkg request-repo --exception dovecot-fts-xapian")


I filed a "bug" on redhat : 
https://bugzilla.redhat.com/show_bug.cgi?id=1953340


And now, how to get things moving ?

Isnt' there just a repo where to push the RPM ? (similar to Arch)

thank you so much

On 2021-04-25 15:51, Emmanuel Seyman wrote:


* Joan Moreau via devel [24/04/2021 18:49] :


It looks overwhelmingly complicated.


Out of curiosity, which part of the process looks complicated.
Perhaps we can simplify it.

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

New Mock release v2.10

[Pavel Raiskup]

I'm pleased to announce that we have a new (small) Mock bugfix release.  Worth
mentioning is that there are many new config files in `mock-core-configs`
package.  Release notes are here:

https://github.com/rpm-software-management/mock/wiki/Release-Notes-2.10

Updates:

Fedora 34: https://bodhi.fedoraproject.org/updates/FEDORA-2021-281879244b
Fedora 33: https://bodhi.fedoraproject.org/updates/FEDORA-2021-63c40bf04d
Feodra 32: https://bodhi.fedoraproject.org/updates/FEDORA-2021-7a8958c321
EPEL 8: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-df65033a42
EPEL 7: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-7c9d9cf44e

Happy building!
Pavel


___
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: Dynamic preemption support in Linux 5.12 kernel

[Chris Murphy]

I created a Fedora Workstation issue to track the progress, and figure
out if any or all of the desktops want to do full preemption by
default.
https://pagure.io/fedora-workstation/issue/228
___
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

[Input Requested] Preset support for third-party services

[Stephen Gallagher]

I originally raised this as a question to FESCo[1], but I was asked to
bring it up on the Fedora Devel list. My apologies for taking so long
to get around to it.

While looking into a preset request, I realized that the guidelines[2]
do not say anything at all about enabling default services that are
not packaged in Fedora.

For a specific example: suppose that a particular VM host provides its
guest tools only as a closed-source binary that they ship. Do we
permit them to request the inclusion of their service in presets under
the reasoning that it would enhance users' performance on those
systems, or do we disallow any non-Fedora software from being included
in the presets?

What about a third-party repository that provides a closed-source
service that enhances an open-source project (for example, a
closed-source codec server that works with open-source encoding
software)?


[1] https://pagure.io/fesco/issue/2575
[2] https://docs.fedoraproject.org/en-US/packaging-guidelines/DefaultServices/
___
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: F34 update experience

[Neal Becker]

rpm -qa | wc - reports 5939

On Tue, Apr 27, 2021 at 2:13 PM Tomasz Torcz  wrote:
>
> Dnia Tue, Apr 27, 2021 at 04:08:38PM +, Zbigniew Jędrzejewski-Szmek 
> napisał(a):
> > On Tue, Apr 27, 2021 at 10:04:34AM -0400, Neal Becker wrote:
> > > Updated F33 -> F34.  Mostly went well, except there is one thing which
> > > could be better.  This is not new to F34 but has been there since the
> > > dnf system-upgrade.
> > >
> > > Running on a pretty decent laptop (core i7, 8GB, SSD).  The issue is
> > > that the installation hangs a long time with no evidence of activity.
> > > The hang begins at
> > > dnf running transaction.  It is disconcerting because it hangs for
> > > about 20-30 minutes, and during that time the fan is not running, so
> >
> > 20-30 minutes seems unexpected… There is a phase where dnf is solving
> > the deps, but it's usually much much shorter (*), and it's CPU-bound,
> > so the fans should be on. I don't know what's going on in your case,
> > but it sounds like some bug.
>
>   In 2019 I did some measurements of F31→F32. First step of distribution 
> upgrade
> took 16 minutes on a desktop computer. The results are at
> https://enotty.pipebreaker.pl/posts/2019/12/time-needed-to-dist-upgrade-fedora/
>
> > Do you have a huge number of packages? Lot's of modules? A very slow disk?
>
>  `rpm -qa` returns 3109. No modules (I think). Storage is btrfs raid1
> over 2xHDD (5900 RPM) + bcache with 2x384GiB partitions.
>
> --
> Tomasz   .. oo o.   oo o. .o   .o o. o. oo o.   ..
> Torcz.. .o .o   .o .o oo   oo .o .. .. oo   oo
> o.o.o.   .o .. o.   o. o. o.   o. o. oo .. ..   o.
> ___
> 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



-- 
Those who don't understand recursion are doomed to repeat it
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Schedule for Tuesdays's FESCo Meeting (2021-04-27)

[Stephen Gallagher]

===
#fedora-meeting: FESCO (2021-04-27)
===


Meeting started by sgallagh at 17:01:49 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2021-04-27/fesco.2021-04-27-17.01.log.html
.



Meeting summary
---
* init process  (sgallagh, 17:01:49)

* #2598 F35 Change: Package information on ELF objects  (sgallagh,
  17:05:20)
  * We will revisit this topic next week after zbyszek provides feedback
on the devel list  (sgallagh, 17:12:01)

* #2597 F35 Change: Debuginfod By Default  (sgallagh, 17:12:09)
  * ACTION: sgallagh to talk to Security team about a threat analysis
(sgallagh, 18:06:10)
  * ACTION: dcantrell to speak to Council about privacy concerns
(sgallagh, 18:06:24)
  * ACTION: fche to explore consent dialogs/warnings  (sgallagh,
18:08:04)

* Next Week's Chair  (sgallagh, 18:08:26)
  * ACTION: sgallagh to chair next week's meeting  (sgallagh, 18:10:51)

* Open Floor  (sgallagh, 18:10:56)

Meeting ended at 18:13:57 UTC.




Action Items

* sgallagh to talk to Security team about a threat analysis
* dcantrell to speak to Council about privacy concerns
* fche to explore consent dialogs/warnings
* sgallagh to chair next week's meeting




Action Items, by person
---
* dcantrell
  * dcantrell to speak to Council about privacy concerns
* fche
  * fche to explore consent dialogs/warnings
* sgallagh
  * sgallagh to talk to Security team about a threat analysis
  * sgallagh to chair next week's meeting
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* sgallagh (73)
* mhroncok (69)
* fche (49)
* zbyszek (46)
* nirik (33)
* Eighth_Doctor (19)
* zodbot (17)
* dcantrell (13)
* decathorpe1 (12)
* cverna (5)
* ignatenkobrain (2)
* Conan_Kudo (0)
* Sir_Gallantmon (0)
* King_InuYasha (0)
* Son_Goku (0)
* decathorpe (0)
* Pharaoh_Atem (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

On Tue, Apr 27, 2021 at 12:50 PM Stephen Gallagher  wrote:
>
> Sorry for the late agenda.
>
>
> Following is the list of topics that will be discussed in the
> FESCo meeting Tuesday at 17:00UTC in #fedora-meeting on
> irc.freenode.net.
>
> To convert UTC to your local time, take a look at
>   http://fedoraproject.org/wiki/UTCHowto
>
> or run:
>   date -d '2021-04-27 17:00 UTC'
>
>
> Links to all issues to be discussed can be found at:
> https://pagure.io/fesco/report/meeting_agenda
>
> = Discussed and Voted in the Ticket =
>
> Title of issue
> https://pagure.io/fesco/issue/###
> DECISION (+X, Y, -Z)
>
> = Followups =
>
> #2597 F35 Change: Debuginfod By Default
> https://pagure.io/fesco/issue/2597
>
> = New business =
>
> = Open Floor =
>
> For more complete details, please visit each individual
> issue.  The report of the agenda items can be found at
> https://pagure.io/fesco/report/meeting_agenda
>
> If you would like to add something to this agenda, you can
> reply to this e-mail, file a new issue at
> https://pagure.io/fesco, e-mail me directly, or bring it
> up at the end of the meeting, during the open floor topic. Note
> that added topics may be deferred until the following meeting.
___
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: F34 update experience

[Tomasz Torcz]

Dnia Tue, Apr 27, 2021 at 04:08:38PM +, Zbigniew Jędrzejewski-Szmek 
napisał(a):
> On Tue, Apr 27, 2021 at 10:04:34AM -0400, Neal Becker wrote:
> > Updated F33 -> F34.  Mostly went well, except there is one thing which
> > could be better.  This is not new to F34 but has been there since the
> > dnf system-upgrade.
> > 
> > Running on a pretty decent laptop (core i7, 8GB, SSD).  The issue is
> > that the installation hangs a long time with no evidence of activity.
> > The hang begins at
> > dnf running transaction.  It is disconcerting because it hangs for
> > about 20-30 minutes, and during that time the fan is not running, so
> 
> 20-30 minutes seems unexpected… There is a phase where dnf is solving
> the deps, but it's usually much much shorter (*), and it's CPU-bound,
> so the fans should be on. I don't know what's going on in your case,
> but it sounds like some bug.

  In 2019 I did some measurements of F31→F32. First step of distribution upgrade
took 16 minutes on a desktop computer. The results are at
https://enotty.pipebreaker.pl/posts/2019/12/time-needed-to-dist-upgrade-fedora/

> Do you have a huge number of packages? Lot's of modules? A very slow disk?

 `rpm -qa` returns 3109. No modules (I think). Storage is btrfs raid1
over 2xHDD (5900 RPM) + bcache with 2x384GiB partitions.

-- 
Tomasz   .. oo o.   oo o. .o   .o o. o. oo o.   ..
Torcz.. .o .o   .o .o oo   oo .o .. .. oo   oo
o.o.o.   .o .. o.   o. o. o.   o. o. oo .. ..   o.
___
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: Bacula 11.0.2-3 for Fedora 33?

[Steven A. Falco]

On 4/27/21 5:14 AM, Paul Howarth wrote:

On Sun, 25 Apr 2021 11:17:49 -0400
"Steven A. Falco"  wrote:

Are there any additional instructions on how to update the bacula
database?


Normally I would use /usr/libexec/bacula/update_mysql_tables but I
found in this case that it didn't work because it was trying to drop an
index from a table that didn't already exist (the index, not the
table).


Thanks for the reply.  I turned out to be able to run:

/usr/libexec/bacula/update_bacula_tables

I'm using postgresql, and the script did manage to update the database.  And as 
you say, it took a long time.

Then, I was getting failures from bacula that it couldn't insert into the File 
area, and I found that I additionally had to re-run:

grant_bacula_privileges

Once I did that, it all started working.

Thanks again for the help!

Steve
___
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: F35 Change: CompilerPolicy Change (System-Wide Change proposal)

[Tom Stellard]

On 4/27/21 8:52 AM, Kevin Kofler via devel wrote:

Tom Stellard wrote:

I don't really want to get in into a debate about specific packages, but
your general point that upstream preference may not be best for Fedora is
a good one, and it's why the proposal was changed from "packagers should
use upstream preference" to "packagers should use best judgement".


That amounts to saying that every packager can use whatever compiler they
want, which basically means we do not have a preferred compiler at all
anymore. I do not consider this acceptable.



The change proposal defines a default compiler for Fedora:

"The default compiler for Fedora is gcc or when upstream doesn't support gcc,
then the default compiler is clang. "


The actual text from the change proposal that describes when a packager may
switch from the default is:

"Given a good technical reason, a packager may:

Choose to build with their package with clang even if the upstream project 
supports gcc.
Choose to build with gcc even if upstream does not support it.
"

-Tom


 Kevin Kofler
___
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


___
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

Schedule for Tuesdays's FESCo Meeting (2021-04-27)

[Stephen Gallagher]

Sorry for the late agenda.


Following is the list of topics that will be discussed in the
FESCo meeting Tuesday at 17:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2021-04-27 17:00 UTC'


Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Discussed and Voted in the Ticket =

Title of issue
https://pagure.io/fesco/issue/###
DECISION (+X, Y, -Z)

= Followups =

#2597 F35 Change: Debuginfod By Default
https://pagure.io/fesco/issue/2597

= New business =

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
___
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: F34 update experience

[Neal Becker]

As I said, the machine has an ssd.  But it has a very large number of
packages.  It's used for development so has lots of devel pkgs, and a large
selection of the live.

On Tue, Apr 27, 2021, 12:10 PM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:

> On Tue, Apr 27, 2021 at 10:04:34AM -0400, Neal Becker wrote:
> > Updated F33 -> F34.  Mostly went well, except there is one thing which
> > could be better.  This is not new to F34 but has been there since the
> > dnf system-upgrade.
> >
> > Running on a pretty decent laptop (core i7, 8GB, SSD).  The issue is
> > that the installation hangs a long time with no evidence of activity.
> > The hang begins at
> > dnf running transaction.  It is disconcerting because it hangs for
> > about 20-30 minutes, and during that time the fan is not running, so
>
> 20-30 minutes seems unexpected… There is a phase where dnf is solving
> the deps, but it's usually much much shorter (*), and it's CPU-bound,
> so the fans should be on. I don't know what's going on in your case,
> but it sounds like some bug.
>
> Do you have a huge number of packages? Lot's of modules? A very slow disk?
>
> Zbyszek
>
> (*) I was upgrading a rpi3 recently, and I had to wait a few minutes...
> But on a beefy machine, anything above a few dozen seconds is suspicious.
> ___
> 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
>
___
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: The Death of Java (packages)

[Mikolaj Izdebski]

On Tue, Apr 27, 2021 at 5:18 PM Dan Čermák
 wrote:
>
> Hi Mikolaj,
>
> Mikolaj Izdebski  writes:
>
> >  5) automating the process of bootstrapping Maven and Ant with related
> > components, so that new versions can be imported and built
> > reproducibly and with consistent quality.
>
> You might want to take a look at openSUSE's maven package:
> https://build.opensuse.org/package/show/Java:packages/maven
>
> It builds itself using ant and not using maven. You'll probably
> recognize a good chunk of the spec, because it originally came from
> Fedora (I'm also pretty certain that Fridrich, the package maintainer,
> would not object to a cross distribution collaboration).

Thanks for the suggestion, but IMO Maven in Fedora should be built the
same way as upstream builds it, that is with Maven. That minimizes the
possibility of deviating from upstream and introducing unnoticed bugs.
Instead a custom project was created that is used to build from
scratch a minimal environment that contains Maven and that can be used
to build Maven package. Then Maven can be used to rebuild itself as
many times as needed.

--
Mikolaj Izdebski
>
>
> Cheers,
>
> Dan
___
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: F34 update experience

[Zbigniew Jędrzejewski-Szmek]

On Tue, Apr 27, 2021 at 10:04:34AM -0400, Neal Becker wrote:
> Updated F33 -> F34.  Mostly went well, except there is one thing which
> could be better.  This is not new to F34 but has been there since the
> dnf system-upgrade.
> 
> Running on a pretty decent laptop (core i7, 8GB, SSD).  The issue is
> that the installation hangs a long time with no evidence of activity.
> The hang begins at
> dnf running transaction.  It is disconcerting because it hangs for
> about 20-30 minutes, and during that time the fan is not running, so

20-30 minutes seems unexpected… There is a phase where dnf is solving
the deps, but it's usually much much shorter (*), and it's CPU-bound,
so the fans should be on. I don't know what's going on in your case,
but it sounds like some bug.

Do you have a huge number of packages? Lot's of modules? A very slow disk?

Zbyszek

(*) I was upgrading a rpi3 recently, and I had to wait a few minutes...
But on a beefy machine, anything above a few dozen seconds is suspicious.
___
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: F35 Change: CompilerPolicy Change (System-Wide Change proposal)

[Kevin Kofler via devel]

Tom Stellard wrote:
> I don't really want to get in into a debate about specific packages, but
> your general point that upstream preference may not be best for Fedora is
> a good one, and it's why the proposal was changed from "packagers should
> use upstream preference" to "packagers should use best judgement".

That amounts to saying that every packager can use whatever compiler they 
want, which basically means we do not have a preferred compiler at all 
anymore. I do not consider this acceptable.

Kevin Kofler
___
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: The Death of Java (packages)

[Jerry James]

On Mon, Apr 26, 2021 at 1:20 PM Fabio Valentini  wrote:
> Long story short, I can no longer in good conscience be the primary
> maintainer of (most) Java packages in Fedora. I am not using any of
> them, I don't like Java or any other languages targeting the JVM, and
> don't get me started on the horrid Java ecosystem. Recently I've been
> spending 40-60 hours per week at my desk, and I just don't have the
> capacity to feel guilty for not taking care of those packages any
> longer.

As I recall, you made it clear when you started that your involvement
with Java packaging was going to be temporary.  Thank you for all the
work you did.  It really did benefit a lot of people.  Regards,
-- 
Jerry James
http://www.jamezone.org/
___
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: The Death of Java (packages)

[Miro Hrončok]

On 27. 04. 21 16:49, Mikolaj Izdebski wrote:

On Mon, Apr 26, 2021 at 9:26 PM Fabio Valentini  wrote:

I will orphan all Java packages I am the main admin of, later today.


I've adopted the majority of Java packages that were orphaned by Fabio,
primarily those that are related to Maven or Ant.

I've been maintaining numerous Java packages in Fedora for more than 9
years.  As modularity was developed, I saw it as an opportunity to
make my life as a package maintainer easier.  Initially I tried to make
Maven and Ant available as default streams and in the buildroot so
they could be available and consumed by non-modular packages.  In the
end that did not and I completely respect the decisions of FESCo to
disallow default streams to then to disallow modules except for
alternative versions.  That means I'll be maintaining Maven and Ant
with their runtime and build dependencies as non-modular packages.

...snip...


Thank You!

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

Re: The Death of Java (packages)

[Dan Čermák]

Hi Mikolaj,

Mikolaj Izdebski  writes:

>  5) automating the process of bootstrapping Maven and Ant with related
> components, so that new versions can be imported and built
> reproducibly and with consistent quality.

You might want to take a look at openSUSE's maven package:
https://build.opensuse.org/package/show/Java:packages/maven

It builds itself using ant and not using maven. You'll probably
recognize a good chunk of the spec, because it originally came from
Fedora (I'm also pretty certain that Fridrich, the package maintainer,
would not object to a cross distribution collaboration).


Cheers,

Dan


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora Linux 34 is available now!

[old sixpack13]

> I'm excited to announce the official release of Fedora Linux 34! 
> 
> The beta version has been very popular this time around, so I know you are
> excited too. Please join me in thanking the thousands of people who work in
> the Fedora Project every year and who make this amazing collaborative
> community operating system possible. Fedora friends: you are awesome, and
> because of you Fedora Linux 34 is as well.
> 

Yes, thanks to all
___
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: The Death of Java (packages)

[Mikolaj Izdebski]

On Mon, Apr 26, 2021 at 9:26 PM Fabio Valentini  wrote:
> I will orphan all Java packages I am the main admin of, later today.

I've adopted the majority of Java packages that were orphaned by Fabio,
primarily those that are related to Maven or Ant.

I've been maintaining numerous Java packages in Fedora for more than 9
years.  As modularity was developed, I saw it as an opportunity to
make my life as a package maintainer easier.  Initially I tried to make
Maven and Ant available as default streams and in the buildroot so
they could be available and consumed by non-modular packages.  In the
end that did not and I completely respect the decisions of FESCo to
disallow default streams to then to disallow modules except for
alternative versions.  That means I'll be maintaining Maven and Ant
with their runtime and build dependencies as non-modular packages.

My plans for the upcoming months regarding adopted packages include:

 1) triaging all open bugs and reviewing all open pull requests,

 2) closing the gap between Fedora and CentOS, by merging dist-git
contents of appropriate components in Fedora Rawhide and CentOS
Stream 9,

 3) unretiring some of Maven and Ant dependencies,

 4) improving testing automation, especially implementing
package-specific tests for use in gating,

 5) automating the process of bootstrapping Maven and Ant with related
components, so that new versions can be imported and built
reproducibly and with consistent quality.

 6) restoring Maven compatibility with OpenJDK 8, so that users who
are stuck with older JDKs have an ability to keep using their
build tools with JDK of their preference.

--
Mikolaj Izdebski
___
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: Kerberos and Fedora's 2FA UX

[Stephen Gallagher]

In the meantime, I created a simple BASH script that you can use:

https://pagure.io/fedora-kinit/blob/main/f/fedora-kinit

$ fedora-kinit --help
Acquire a Kerberos ticket-granting ticket for Fedora
Usage: /home/sgallagh/.local/bin/fedora-kinit [-u|--user ] [-h|--help]
-u, --user: Fedora account name (default: )
-h, --help: Prints help


$ fedora-kinit
Enter your password and OTP concatenated. (Ignore that the prompt is
for only the token)
Enter OTP Token Value:

On Tue, Apr 27, 2021 at 7:32 AM Miroslav Suchý  wrote:
>
> Dne 25. 04. 21 v 0:01 Kevin Fenzi napsal(a):
>
>  - (easy) supply a script/wrapper like Miroslav is showing as a part of
>the fedora-packager rpm package
>
> Yeah, we talked about this a while back, I am not sure why it wasn't
> implemented. ;( Would someone care to submit a PR to fedora-packager for
> it? Otherwise hopefully we can get to it...
>
>
> https://pagure.io/fedora-packager/pull-request/168
>
> Miroslav
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
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: Thoughts about packaging a standalone python-PyQt5-sip?

[Kevin Fenzi]

On Mon, Apr 26, 2021 at 02:29:52PM -0400, Scott Talbert wrote:
> On Sat, 24 Apr 2021, Kevin Fenzi wrote:
> 
> > On Tue, Jan 12, 2021 at 10:42:28PM -0500, Scott Talbert wrote:
> > > 
> > > OK, I'm going to make an attempt to move python-qt5 (and its friends) to
> > > sip5.  I'm planning to build everything in a copr first.
> > 
> > Hey Scott.
> > 
> > Did you get any further with this?
> > 
> > Anything I can do to help? I'd really like to be able to update calibre
> > again. :)
> 
> Yes, I got fairly far with porting all PyQt5 SIP consumers (including
> calibre) to use SIPv5.  I think I then got discouraged at the thought of
> making a bunch of PRs and having to nag maintainers to merge them in some
> sort of coordinated fashion.
> 
> I guess - if I get everything working, would you be willing to merge a bunch
> of related PRs as provenpackager and do rebuilds in a side tag?

Sure! As long as maintainers are on board... 

> At this point, it might also make sense to go directly to SIPv6 as that's
> out already.

I'm not sure how wide support for 6 is, but I suspect it's easier to get
to than 4-5 was. ;) 


On Mon, Apr 26, 2021 at 10:47:43PM -0500, Rex Dieter wrote:
> 
> I'd be able and willing to assist here too, thanks for working on it!
> 
> As far as sip6 goes, I'd venture the adjustment from v5 to v6 will be 
> smaller than what v4 to v5 was.

Yeah, agreed. 

Happy to work with you both and get this done. :) 

kevin


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora Linux 34 is available now!

[Matthew Miller]

I'm excited to announce the official release of Fedora Linux 34! 

The beta version has been very popular this time around, so I know you are
excited too. Please join me in thanking the thousands of people who work in
the Fedora Project every year and who make this amazing collaborative
community operating system possible. Fedora friends: you are awesome, and
because of you Fedora Linux 34 is as well.

Read the official announcement at:

* https://fedoramagazine.org/announcing-fedora-34

or just go ahead and upgrade your system, or download install media from:

* https://getfedora.org/

-- 
Matthew Miller

Fedora Project Leader
___
announce mailing list -- annou...@lists.fedoraproject.org
To unsubscribe send an email to announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/annou...@lists.fedoraproject.org
___
announce mailing list -- annou...@lists.fedoraproject.org
To unsubscribe send an email to announce-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/annou...@lists.fedoraproject.org
___
announce mailing list -- annou...@lists.fedoraproject.org
To unsubscribe send an email to announce-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/annou...@lists.fedoraproject.org
___
announce mailing list -- annou...@lists.fedoraproject.org
To unsubscribe send an email to announce-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/annou...@lists.fedoraproject.org
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-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-annou...@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure
___
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

F34 update experience

[Neal Becker]

Updated F33 -> F34.  Mostly went well, except there is one thing which
could be better.  This is not new to F34 but has been there since the
dnf system-upgrade.

Running on a pretty decent laptop (core i7, 8GB, SSD).  The issue is
that the installation hangs a long time with no evidence of activity.
The hang begins at
dnf running transaction.  It is disconcerting because it hangs for
about 20-30 minutes, and during that time the fan is not running, so
no evidence of cpu usage.  There seems to be no way to switch VT to
try to see what's happening.  I'd hate to see what happens on a less
capable machine.

I wish there was some way to get some better feedback that the update is alive.

-- 
Those who don't understand recursion are doomed to repeat it
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Kerberos and Fedora's 2FA UX

[Miroslav Suchý]

Dne 25. 04. 21 v 0:01 Kevin Fenzi napsal(a):

  - (easy) supply a script/wrapper like Miroslav is showing as a part of
the fedora-packager rpm package

Yeah, we talked about this a while back, I am not sure why it wasn't
implemented. ;( Would someone care to submit a PR to fedora-packager for
it? Otherwise hopefully we can get to it...



https://pagure.io/fedora-packager/pull-request/168

Miroslav

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Self Introduction Sergei Petrosian

[Sergei Petrosian]

Hello Fedora developers,

I am a fairly new member of the team maintaining Ansible roles for managing
linux - namely this repo  [1] and
this RPM  [2] and
would like to introduce myself to you. In the past I worked as Technical
Writer on Red Hat Satellite and participated in upstreaming the Satellite
documentation to the upstream, this resulted in this upstream Foreman
documentation  [3].
Now I focus on the mssql  [4]
Ansible role that automates installation on the configuration of Microsoft
SQL Server on linux. It is working now and is published in Ansible Galaxy
as microsoft.sql , I want to also
publish it as an RPM package for Fedora.

I live in Prague, my main passion is music, play trumpet and investigate
synths.

Thank you

[1] https://github.com/linux-system-roles
[2] https://src.fedoraproject.org/rpms/linux-system-roles
[3] https://docs.theforeman.org/
[4] https://github.com/linux-system-roles/mssql
[5] https://galaxy.ansible.com/microsoft/sql

-- 

Sergei Petrosian, RHCE

He / Him / His

Software Engineer, RHEL System Roles

Red Hat Prague, Czech Republic 

spetr...@redhat.com
M: +420792444506 IRC: spetrosi

___
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: Self Introduction: Anatoly Vildemanov

[Vitaly Zaitsev via devel]

On 27.04.2021 12:11, Anatoly Vildemanov wrote:

And I will do packages UCX for fedora
For this could you please add me to “packager” group like member


Hello and welcome to Fedora. Please follow this procedure:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers

--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.org)
___
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: KDE Autostart in F34

[Vitaly Zaitsev via devel]

On 27.04.2021 02:23, Ravindra Kumar wrote:
It looks like KDE in Fedora 34 is not honoring open-vm-tools autostart 
script in /etc/xdg/autostart/vmware-user.desktop. GNOME seems to work fine.


This desktop file need to be replaced by the systemd-user unit, IMO.

--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.org)
___
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: question was: What do we think about always autoreconfing? was: Re: Fedora 35 Change: Autoconf-2.71 (Self-Contained Change proposal))

[Sérgio Basto]

On Mon, 2021-04-19 at 09:27 +0200, Ondrej Dubaj wrote:
> 
> 
> On Fri, Apr 16, 2021 at 3:30 PM David Cantrell 
> wrote:
> > On Tue, Apr 13, 2021 at 11:26:24AM +0100, Richard W.M. Jones wrote:
> > >Hijacking this thread originally about
> > >https://fedoraproject.org/wiki/Changes/Autoconf_271
> > >
> > >What is the current thinking in Fedora about always running
> > >"autoreconf -i" during builds that use autotools?
> > 
> > I think we are likely to see the least problems for projects that
> > created their configure.ac files using autoscan.  For projects that
> > constructed them manually or in other ways, we'll likely see some
> > fallout.  I would encourage maintainers to work towards fixing
> > these
> > things and contributing them back upstream.  Still, we would need
> > to
> > provide a way to disable the autoreconf step for particular
> > problematic packages.
> > 
> > Some projects provide their own autotools macros and wrappers
> > around
> > autoreconf.  For example, Xfce either provides or provided xdt-
> > autogen
> > as a wrapper to run autoreconf with the Xfce-specific macros and
> > other
> > defines available.  If it's best to rerun xdt-autogen in these
> > cases,
> > how could we handle that in the spec file so it runs the correct
> > 'autoreconf' command?
> > 
> > >The cons of always autoreconfing are that it slows down builds,
> > >sometimes considerably.  It also could fail - I noticed that
> > autoconf
> > >2.71 has several incompatibilities with the most widely used
> > autoconf
> > >(2.69).
> > 
> > I think the failures will be the most frustrating part of this
> > rather
> > than the build time.  An FAQ or something of how to fix common
> > failures for 2.71 would be useful for contributors.
> > 
> 
> 
> Document with common failures and fixes already exists [1]. Also
> multiple ways of testing are documented in the change proposal [2],
> where the link to the document [1] is present.
> 
> Updating autoconf to version 2.71 is a hard process, we are doing our
> best to make it as fluent as possible. There is a copr created for
> testing, bugs in bugzilla created (with link to change proposal) for
> failing components and we are actively moving things forward.
> 
> Hopefully it will be enough to make this possible.
> 
> [1]
> https://docs.google.com/document/d/1SAGTJZEF9z_nkHMbXTF-YTTvKRja7ygfOOMzl-DYBSk/edit
> 

I almost missed this precious document, in my opinion it should go to
the fedoraproject wiki pages along [2] 
The document covers almost all the problems that I found 

"if test "$ac_test_CFLAGS" = set" , stopped to work what is the correct
replacement ? "if test -z $CFLAGS; then"
or "if test $ac_test_CFLAGS; then"  this second option was found here
[3] 


[3] 
https://chromium.googlesource.com/external/github.com/Distrotech/autoconf/+/76754e04fce5f6a7701bec57b057020585df2ae3%5E%21/


> [2] https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test
> 
> 
> > 
> > Thanks,
> > 
> > ___
> > 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

-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Self Introduction: Anatoly Vildemanov

[Anatoly Vildemanov]

Hi,

My name is Anatoly Vildemanov, I work at Nvidia on UCX opensource project 
https://github.com/openucx/ucx
My general responsibility is CI and CD
And I will do packages UCX for fedora
For this could you please add me to "packager" group like member

Anatoly Vildemanov
Sr. Software Engineer, DevOps | Networking SW Mellanox
Mob: +79082335079
NVIDIA

___
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

Fedora-Cloud-32-20210427.0 compose check report

[Fedora compose checker]

No missing expected images.

Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-32-20210426.0):

ID: 870854  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/870854
ID: 870861  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/870861

Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
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: Bacula 11.0.2-3 for Fedora 33?

[Paul Howarth]

On Sun, 25 Apr 2021 11:17:49 -0400
"Steven A. Falco"  wrote:

> This morning "dnf update" brought in bacula 11.0.2-3.  Previously I
> had been on 9.6.7-1.
> 
> Apparently, the new bacula wants a different database version.  I
> have version 16, but it wants 1022.

I was surprised by this myself yesterday.

> I looked at the files in /usr/share/doc/bacula-director/updatedb but
> there doesn't seem to be anything to update the db from 16 to 1022.
> 
> For now, I've rolled back to 9.6.7-1 and blocked further dnf updates
> of bacula.
> 
> Are there any additional instructions on how to update the bacula
> database?

Normally I would use /usr/libexec/bacula/update_mysql_tables but I
found in this case that it didn't work because it was trying to drop an
index from a table that didn't already exist (the index, not the
table).

I did manage to complete the update by opening up a mysql session and
manually running the commands in the update script for upgrades from
version 16, which is several incremental upgrades to get to 1022. I
ignored the errors relating to commands for dropping indexes that
weren't there.

Beware that if you have a substantial "File" database that this process
will take quite a long time and require a little more free disk space
than taken by the existing bacula database, on top of the original
database.

My backups ran apparently successfully last night on the new version.
This morning I tested a restore that pulled in 14,637 files that came
from a mix of full and differential backups on the old version and the
latest incremental on the latest version. That worked OK.

Paul.
___
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: Heads-up: RPM 4.17 alpha coming to rawhide near you (broken python-srpm-macros)

[Panu Matilainen]

On 4/27/21 10:28 AM, Miro Hrončok wrote:

On 27. 04. 21 8:41, Panu Matilainen wrote:

On 4/27/21 12:47 AM, Miro Hrončok wrote:

We see a problem with this construct:

Source0:    %{pypi_source}

It used to work:

$ rpmspec -P python-asyncpg.spec | grep Source0
Source0: 
https://files.pythonhosted.org/packages/source/a/asyncpg/asyncpg-0.22.0.tar.gz 



$ rpm --define 'name foo' --define 'version 1.2.3' --eval 
'%{pypi_source}'

https://files.pythonhosted.org/packages/source/f/foo/foo-1.2.3.tar.gz

$ rpm --showrc | grep pypi_source -A3
-13: pypi_source    %{lua:
 local src = rpm.expand('%1')
 local ver = rpm.expand('%2')
 local ext = rpm.expand('%3')

Now we get:

error: Bad source: /builddir/build/SOURCES/%{pypi_source}: No such 
file or directory


when building the package.

In mock:

 sh-5.1# rpmspec -P python-asyncpg.spec | grep Source0
Source0:    %{pypi_source}

 sh-5.1# rpm --define 'name foo' --define 'version 
1.2.3' --eval '%{pypi_source}'

%{pypi_source}

 sh-5.1# rpm --showrc | grep pypi_source -A3
(empty)


The file is /usr/lib/rpm/macros.d/macros.python-srpm. None of the Lua 
macros there seem to be known to RPM, but other macros from that file 
work fine.


Is it possible that some Lua code there breaks all the other Lua 
macros from that file? I see no error, just the macros are not 
recognized, as if they don't exist.




Sounds strange. I'll look into it, but please file a bug.


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



Thanks.

So the issue was that a %{ in a macro file comment prevents the 
remainder of the macros in that file loading. I've reverted the change 
for now to consider the right thing: 
https://github.com/rpm-software-management/rpm/issues/1659


- Panu -
___
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: Gnome BZ untouched for years #1414539

[Tomáš Popela]

On Mon, Apr 26, 2021 at 4:47 PM Neal Gompa  wrote:

> On Mon, Apr 26, 2021 at 10:38 AM Michal Schorm  wrote:
> >
> > How many more years can I expect it will take to resolve or at least
> > seriously examine this following BZ?
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1414539
> >
> > Does the maintainer of the utility care ? Does he check the BZ tickets ?
> > Does the gnome-sig triage the BZs against gnome components at least once
> a year?
> >
> > Who to contact?
> > Who to turn onto ?
> >
>
> It is the position of the GNOME maintainer team that all RHBZs
> basically go to /dev/null unless they're blocker bugs for releases,
> unfortunately.
>

Also please see https://pagure.io/fedora-workstation/issue/131 -  Red Hat
Bugzilla: GNOME packages are in bad shape

Bye,
Tom
___
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: The Death of Java (packages)

[Emmanuel Seyman]

* Fabio Valentini [26/04/2021 21:19] :
>
>   I am not using any of
> them, I don't like Java or any other languages targeting the JVM, and
> don't get me started on the horrid Java ecosystem.

Thank you for all the work you've done, Fabio.

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

Fedora-Cloud-33-20210427.0 compose check report

[Fedora compose checker]

No missing expected images.

Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-33-20210426.0):

ID: 870728  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/870728
ID: 870735  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/870735

Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
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: Heads-up: RPM 4.17 alpha coming to rawhide near you (broken python-srpm-macros)

[Miro Hrončok]

On 27. 04. 21 8:41, Panu Matilainen wrote:

On 4/27/21 12:47 AM, Miro Hrončok wrote:

We see a problem with this construct:

Source0:    %{pypi_source}

It used to work:

$ rpmspec -P python-asyncpg.spec | grep Source0
Source0: 
https://files.pythonhosted.org/packages/source/a/asyncpg/asyncpg-0.22.0.tar.gz


$ rpm --define 'name foo' --define 'version 1.2.3' --eval '%{pypi_source}'
https://files.pythonhosted.org/packages/source/f/foo/foo-1.2.3.tar.gz

$ rpm --showrc | grep pypi_source -A3
-13: pypi_source    %{lua:
 local src = rpm.expand('%1')
 local ver = rpm.expand('%2')
 local ext = rpm.expand('%3')

Now we get:

error: Bad source: /builddir/build/SOURCES/%{pypi_source}: No such file or 
directory


when building the package.

In mock:

 sh-5.1# rpmspec -P python-asyncpg.spec | grep Source0
Source0:    %{pypi_source}

 sh-5.1# rpm --define 'name foo' --define 'version 1.2.3' --eval 
'%{pypi_source}'

%{pypi_source}

 sh-5.1# rpm --showrc | grep pypi_source -A3
(empty)


The file is /usr/lib/rpm/macros.d/macros.python-srpm. None of the Lua macros 
there seem to be known to RPM, but other macros from that file work fine.


Is it possible that some Lua code there breaks all the other Lua macros from 
that file? I see no error, just the macros are not recognized, as if they 
don't exist.




Sounds strange. I'll look into it, but please file a bug.


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

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

Re: The Death of Java (packages)

[Ankur Sinha]

On Mon, Apr 26, 2021 21:19:44 +0200, Fabio Valentini wrote:
> Hi everybody,
> 
> Long story short, I can no longer in good conscience be the primary
> maintainer of (most) Java packages in Fedora. I am not using any of
> them, I don't like Java or any other languages targeting the JVM, and
> don't get me started on the horrid Java ecosystem. Recently I've been
> spending 40-60 hours per week at my desk, and I just don't have the
> capacity to feel guilty for not taking care of those packages any
> longer.
> 

Thank you so much for the work you put into these packages, and I'm
really sorry I couldn't be more help.

After struggling with our Java packages for quite a bit, the neuro-sig
reached a similar conclusion---that they're just too much work or just
pretty much impossible to keep in Fedora. We've now accepted that
documenting Java tools and asking users to install them directly from
upstream is the most we can manage.

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure