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

2023-02-06 Thread Vít Ondruch


Dne 06. 02. 23 v 1:13 Georg Sauthoff napsal(a):

Hello,

On Thu, Feb 02, 2023 at 02:45:23PM -0300, Mathias Zavala wrote:

I’m sorry for not answering sooner! I’ll be glad to receive help with the
current state of the package. Thanks in advance

you are a datamash Fedora package maintainer?

Judging from the FTBFS 
mail/Bugzilla/https://src.fedoraproject.org/rpms/datamash it
looks like jhladky (Jiri Hladky) currently is the sole maintainer?

Perhaps Co-maintainers aren't displayed corrently there?

Btw, what is the canonical way to look up all the maintainers of a given
Fedora package?



You are looking at the right place. Or you can use the API:


~~~

$ curl https://src.fedoraproject.org/api/0/rpms/datamash
{
  "access_groups": {
    "admin": [],
    "collaborator": [],
    "commit": [],
    "ticket": []
  },
  "access_users": {
    "admin": [],
    "collaborator": [],
    "commit": [],
    "owner": [
  "jhladky"
    ],
    "ticket": []
  },
  "close_status": [],
  "custom_keys": [],
  "date_created": "1503079151",
  "date_modified": "1569590838",
  "description": "The datamash package",
  "full_url": "https://src.fedoraproject.org/rpms/datamash";,
  "fullname": "rpms/datamash",
  "id": 24246,
  "milestones": {},
  "name": "datamash",
  "namespace": "rpms",
  "parent": null,
  "priorities": {},
  "tags": [],
  "url_path": "rpms/datamash",
  "user": {
    "full_url": "https://src.fedoraproject.org/user/jhladky";,
    "fullname": "Jirka Hladky",
    "name": "jhladky",
    "url_path": "user/jhladky"
  }
}

~~~


Vít




A quick google search didn't point me in the right direction ...


Anyhow, you (or someone with the sufficient permissions) may add me as a
Co-Maintainer for the datamash package such that I can help out with
that package in the future.

See also:
https://docs.fedoraproject.org/en-US/fesco/Policy_for_encouraging_comaintainers_of_packages/

Best regards,
Georg


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


Re: F38 proposal: Rpmautospec by Default (System-Wide Change proposal)

2023-02-06 Thread Vít Ondruch
I have just learned the hard way that `fedpkg import` does not work with 
`rpmautospec` and that is show stopper for me. I have reported ticket here:


https://pagure.io/rpkg/issue/655

And won't try rpmautospec again until this is resolved.


Vít


Dne 30. 12. 22 v 20:01 Ben Cotton napsal(a):

https://fedoraproject.org/wiki/Changes/Rpmautospec_by_Default

This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.

== Summary ==
Rpmautospec (`%autorelease` and `%autochangelog`) is recommended as
the default approach.
Packaging Guidelines and other documentation are adjusted to describe
this approach first.
Various tools that provide spec file templates are adjusted.

== Owner ==
* Name: [[User:Nphilipp| Nils Philippsen]], [[User:Zbyszek| Zbigniew
Jędrzejewski-Szmek]]
* Email: nphilipp - at - redhat.com, zbyszek - at - in.waw.pl


== Detailed Description ==

{{admon/note|Brief reminder about rpmautospec|
The spec file contains:

Version: 1.2.3
Release: %autorelease
...
%changelog
%autochangelog

Rpmautospec uses git history. Whenever the package is built
(`.src.rpm` is generated), rpmautospec tooling will replace the
`%autorelease` macro with the number of commits since the last commit
that changed the `Version` field, and the `%autochangelog` macro with
a text generated from `git log`.
For details see the
[https://docs.pagure.org/fedora-infra.rpmautospec/principle.html
docs].
}}

Rpmautospec has been deployed in Fedora since F35
([[Changes/rpmautospec]]), and 3423/23045 packages use it (15%).
But it is still a "second-class citizen": most documentation doesn't
mention it, and many packagers know that it exists but don't use it in
their packages. We think that it's reasonable to switch to
`%autorelease`+`%autochangelog` for almost all packages and that
Packaging Guidelines and various packaging howtos should recommend
that approach to packagers. The "traditional" approach of
manually-managed `Release` and `%changelog` will remain valid and will
be documented as a fallback.

This change is targeted at Fedora 38, but it will actually apply to
all releases. The goal is to update the Packaging Guidelines and other
prominent documentation and tools now, and other docs and tools
possibly at a later time. Changing packages is out of scope.

It is worth mentioning that `rust2rpm` uses
`%autorelease`+`%autochangelog` since a few releases, so most rust
packages have switched. (Generally, rust spec files are recreated
using the generator for each new version, so the switch would happen
whenever a new version is packaged unless the packager opts out.)

== Feedback ==

* Thread on fedora-devel in August 2022:
[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/T6J2WGIMRCTW77QTH4D7HPNS6KUGDQOQ/
rpmautospec by default]
** open issues: a bunch have been fixed.
** maintenance: Nils will add some co-maintainers.
** compatibility with rpmdevtools, fedpkg/rpkg, fedora-review: see
Scope section.

== Benefit to Fedora ==
Various packaging workflows become smoother for packagers and contributors:

* packagers don't need to touch the `Release` field on updates
* packagers describe changes just once in the git commit message, the
`%changelog` entry is autogenerated
* patches to the spec file can be cherry-picked between branches
without trivial conflicts
* pull requests on src.fedoraproject.org can be merged without trivial conflicts
* in workflows that regenerate the spec file (rust2rpm, pip2rpm, …)
`%changelog` section doesn't need to be copied over

== Scope ==
* Proposal owners:
** provide pull requests to Packaging Guidelines and other docs to
make `%autorelease`+`%autochangelog` the default
** implement fixes for issues reported by packagers
** make semi-regular releases of rpmautospec
([https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/K5EA5OGRX2BCZ353C7S4MQVZTSH2BH63/
0.3.1 was released on November 17th, and should be deployed to
production in about two weeks])

* Other developers:
** provide pull requests to other docs as appropriate
** accept the changes to documentation
** update other spec file generators (pip2rpm, others?)

* Somebody (TBD):
** `fedora-review` — https://pagure.io/rpkg/issue/641
** `fedpkg import` — with https://pagure.io/rpkg/c/3087dd7, the
command will fail. A replacement workflow that instead restores
`%autorelease`+`%autochangelog` in the file committed to dist-git
needs to be implemented.

* Related work
** https://pagure.io/rpkg/c/3087dd7
** https://src.fedoraproject.org/rpms/fedora-packager/pull-request/4


* Release engineering: [https://pagure.io/releng/issues #Releng issue number]

* Policies and guidelines: a list of places to be updated
** https://docs.fedoraproject.org/en-US/packaging-guidelines/#changelogs
** https://docs.fedoraproject.org/

Fedora rawhide compose report: 20230206.n.0 changes

2023-02-06 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20230205.n.0
NEW: Fedora-Rawhide-20230206.n.0

= SUMMARY =
Added images:3
Dropped images:  2
Added packages:  2
Dropped packages:3
Upgraded packages:   119
Downgraded packages: 0

Size of added packages:  59.91 KiB
Size of dropped packages:122.35 KiB
Size of upgraded packages:   1.59 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -18.35 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Cloud_Base raw-xz ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20230206.n.0.ppc64le.raw.xz
Image: Cloud_Base qcow2 ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20230206.n.0.ppc64le.qcow2
Image: Xfce raw-xz aarch64
Path: Spins/aarch64/images/Fedora-Xfce-Rawhide-20230206.n.0.aarch64.raw.xz

= DROPPED IMAGES =
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20230205.n.0.iso
Image: Container_Base docker aarch64
Path: 
Container/aarch64/images/Fedora-Container-Base-Rawhide-20230205.n.0.aarch64.tar.xz

= ADDED PACKAGES =
Package: budgie-desktop-defaults-0.3-1.fc38
Summary: Budgie Desktop Defaults for Fedora
RPMs:budgie-desktop-defaults
Size:14.69 KiB

Package: python-pyrate-limiter-2.8.5-1.fc38
Summary: The request rate limiter using Leaky-bucket algorithm
RPMs:python3-pyrate-limiter
Size:45.22 KiB


= DROPPED PACKAGES =
Package: rust-ammonia-3.1.4-3.fc38
Summary: HTML Sanitization
RPMs:rust-ammonia+default-devel rust-ammonia-devel
Size:49.99 KiB

Package: rust-custom_derive-0.1.7-15.fc38
Summary: Macro that enables the use of custom derive attributes
RPMs:rust-custom_derive+default-devel rust-custom_derive+std-devel 
rust-custom_derive-devel
Size:35.48 KiB

Package: rust-linkify-0.4.0-8.fc38
Summary: Finds URLs and email addresses in plain text
RPMs:rust-linkify+default-devel rust-linkify-devel
Size:36.88 KiB


= UPGRADED PACKAGES =
Package:  ProDy-2.4.0-2.fc38
Old package:  ProDy-2.3.1-2.fc38
Summary:  Application for protein structure, dynamics and sequence analysis
RPMs: python3-ProDy
Size: 31.40 MiB
Size change:  9.36 MiB
Changelog:
  * Sun Feb 05 2023 Antonio Trande  - 2.4.0-1
  - Release 2.4.0

  * Sun Feb 05 2023 Antonio Trande  - 2.4.0-2
  - Change required packages version


Package:  amsynth-1.13.2-1.fc38
Old package:  amsynth-1.13.0-2.fc38
Summary:  A classic synthesizer with dual oscillators
RPMs: amsynth amsynth-data dssi-amsynth-plugin lv2-amsynth-plugin 
vst-amsynth-plugin
Size: 3.12 MiB
Size change:  -1.05 KiB
Changelog:
  * Sun Feb 05 2023 Guido Aulisi  - 1.13.2-1
  - Update to 1.13.2


Package:  auryn-0.8.2-19.fc38
Old package:  auryn-0.8.2-15.fc38
Summary:  Plastic Recurrent Network Simulator
RPMs: auryn-doc auryn-mpich auryn-mpich-devel auryn-openmpi 
auryn-openmpi-devel
Size: 7.41 MiB
Size change:  -1.94 MiB
Changelog:
  * Fri Feb 03 2023 Benjamin A. Beasley  - 0.8.2-19
  - Leaf package: drop ix86 support


Package:  bpfmon-2.51-3.fc38
Old package:  bpfmon-2.51-2.fc38
Summary:  Traffic monitor for BPF expression/iptables rule
RPMs: bpfmon
Size: 130.40 KiB
Size change:  422 B
Changelog:
  * Sun Feb 05 2023 Boian Bonev  - 2.51-3
  - Rebuilt for yascreen 1.96


Package:  bsd-games-2.17-71.fc38
Old package:  bsd-games-2.17-70.fc38
Summary:  Collection of text-based games
RPMs: bsd-games
Size: 6.01 MiB
Size change:  509 B
Changelog:
  * Sun Feb 05 2023 Florian Weimer  - 2.17-71
  - Fix C99 compatibility issue in hunt (#2152550)


Package:  clifm-1.10-1.fc38
Old package:  clifm-1.7-3.fc38
Summary:  Shell-like, command line terminal file manager
RPMs: clifm
Size: 1.48 MiB
Size change:  154.87 KiB
Changelog:
  * Sun Feb 05 2023 Jonathan Wright  - 1.10-1
  - update to 1.10


Package:  coin-or-Bcp-1.4.4-11.fc38
Old package:  coin-or-Bcp-1.4.4-10.fc38
Summary:  Branch-Cut-Price Framework
RPMs: coin-or-Bcp coin-or-Bcp-devel coin-or-Bcp-doc
Size: 17.14 MiB
Size change:  439.39 KiB
Changelog:
  * Sun Feb 05 2023 Florian Weimer  - 1.4.4-11
  - Port configure script to C99


Package:  coin-or-FlopC++-1.2.5-10.fc38
Old package:  coin-or-FlopC++-1.2.5-9.fc38
Summary:  Algebraic modeling language
RPMs: coin-or-FlopC++ coin-or-FlopC++-devel coin-or-FlopC++-doc
Size: 6.13 MiB
Size change:  213.83 KiB
Changelog:
  * Sun Feb 05 2023 Florian Weimer  - 1.2.5-10
  - Port configure script to C99


Package:  coin-or-OS-2.10.3-5.fc38
Old package:  coin-or-OS-2.10.3-4.fc38
Summary:  Optimization Services
RPMs: coin-or-OS coin-or-OS-devel coin-or-OS-doc
Size: 44.97 MiB
Size change:  13.16 KiB
Changelog:
  * Sun Feb 05 2023 Florian Weimer  - 2.10.3-5
  - Port configure script to C99


Package:  combblas-2.0.0-1.fc38
Old package:  combblas-1.6.2-0.18.beta2

Re: Orphaned packages looking for new maintainers

2023-02-06 Thread Richard W.M. Jones
On Tue, Jan 31, 2023 at 02:13:11PM -0700, Jerry James wrote:
> On Tue, Jan 31, 2023 at 2:14 AM Richard W.M. Jones  wrote:
> >
> > On Mon, Jan 30, 2023 at 11:36:52AM +0100, Miro Hrončok wrote:
> > > ocaml-dose3   orphan 2 weeks 
> > > ago
> > > ocaml-mccsorphan 2 weeks 
> > > ago
> > > ocaml-opam-file-formatorphan 2 weeks 
> > > ago
> >
> > > Affected (co)maintainers (either directly or via packages' dependencies):
> > > andyli: ocaml-dose3, ocaml-opam-file-format, ocaml-mccs
> >
> > Jerry, I guess we still need these?  If so I will take over co-maintenance.
> 
> We do indeed.  Feel free to add me as comaintainer if you like.

I have finally got around to taking these three.  I have added
you as a comaintainer ("admin" if that's right?)

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.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, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: F38 proposal: Rpmautospec by Default (System-Wide Change proposal)

2023-02-06 Thread Neil Hanlon
On Mon, Feb 6, 2023, 12:44 Vít Ondruch  wrote:

> I have just learned the hard way that `fedpkg import` does not work with
> `rpmautospec` and that is show stopper for me. I have reported ticket here:
>
> https://pagure.io/rpkg/issue/655


I ran into this myself and found its a bit less of an issue than it seems.
If you build the srpm with mock, the srpm will work with fedpkg import.

Confusingly, srpms resulting from fedpkg mockbuild are not built with mock,
but with rpmbuild directly, which results in this error.


>
> And won't try rpmautospec again until this is resolved.


>
> Vít
>
>
> Dne 30. 12. 22 v 20:01 Ben Cotton napsal(a):
> > https://fedoraproject.org/wiki/Changes/Rpmautospec_by_Default
> >
> > This document represents a proposed Change. As part of the Changes
> > process, proposals are publicly announced in order to receive
> > community feedback. This proposal will only be implemented if approved
> > by the Fedora Engineering Steering Committee.
> >
> > == Summary ==
> > Rpmautospec (`%autorelease` and `%autochangelog`) is recommended as
> > the default approach.
> > Packaging Guidelines and other documentation are adjusted to describe
> > this approach first.
> > Various tools that provide spec file templates are adjusted.
> >
> > == Owner ==
> > * Name: [[User:Nphilipp| Nils Philippsen]], [[User:Zbyszek| Zbigniew
> > Jędrzejewski-Szmek]]
> > * Email: nphilipp - at - redhat.com, zbyszek - at - in.waw.pl
> >
> >
> > == Detailed Description ==
> >
> > {{admon/note|Brief reminder about rpmautospec|
> > The spec file contains:
> > 
> > Version: 1.2.3
> > Release: %autorelease
> > ...
> > %changelog
> > %autochangelog
> > 
> > Rpmautospec uses git history. Whenever the package is built
> > (`.src.rpm` is generated), rpmautospec tooling will replace the
> > `%autorelease` macro with the number of commits since the last commit
> > that changed the `Version` field, and the `%autochangelog` macro with
> > a text generated from `git log`.
> > For details see the
> > [https://docs.pagure.org/fedora-infra.rpmautospec/principle.html
> > docs].
> > }}
> >
> > Rpmautospec has been deployed in Fedora since F35
> > ([[Changes/rpmautospec]]), and 3423/23045 packages use it (15%).
> > But it is still a "second-class citizen": most documentation doesn't
> > mention it, and many packagers know that it exists but don't use it in
> > their packages. We think that it's reasonable to switch to
> > `%autorelease`+`%autochangelog` for almost all packages and that
> > Packaging Guidelines and various packaging howtos should recommend
> > that approach to packagers. The "traditional" approach of
> > manually-managed `Release` and `%changelog` will remain valid and will
> > be documented as a fallback.
> >
> > This change is targeted at Fedora 38, but it will actually apply to
> > all releases. The goal is to update the Packaging Guidelines and other
> > prominent documentation and tools now, and other docs and tools
> > possibly at a later time. Changing packages is out of scope.
> >
> > It is worth mentioning that `rust2rpm` uses
> > `%autorelease`+`%autochangelog` since a few releases, so most rust
> > packages have switched. (Generally, rust spec files are recreated
> > using the generator for each new version, so the switch would happen
> > whenever a new version is packaged unless the packager opts out.)
> >
> > == Feedback ==
> >
> > * Thread on fedora-devel in August 2022:
> > [
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/T6J2WGIMRCTW77QTH4D7HPNS6KUGDQOQ/
> > rpmautospec by default]
> > ** open issues: a bunch have been fixed.
> > ** maintenance: Nils will add some co-maintainers.
> > ** compatibility with rpmdevtools, fedpkg/rpkg, fedora-review: see
> > Scope section.
> >
> > == Benefit to Fedora ==
> > Various packaging workflows become smoother for packagers and
> contributors:
> >
> > * packagers don't need to touch the `Release` field on updates
> > * packagers describe changes just once in the git commit message, the
> > `%changelog` entry is autogenerated
> > * patches to the spec file can be cherry-picked between branches
> > without trivial conflicts
> > * pull requests on src.fedoraproject.org can be merged without trivial
> conflicts
> > * in workflows that regenerate the spec file (rust2rpm, pip2rpm, …)
> > `%changelog` section doesn't need to be copied over
> >
> > == Scope ==
> > * Proposal owners:
> > ** provide pull requests to Packaging Guidelines and other docs to
> > make `%autorelease`+`%autochangelog` the default
> > ** implement fixes for issues reported by packagers
> > ** make semi-regular releases of rpmautospec
> > ([
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/K5EA5OGRX2BCZ353C7S4MQVZTSH2BH63/
> > 0.3.1 was released on November 17th, and should be deployed to
> > production in about two weeks])
> >
> > * Other developers:
> > ** provide pull requests to other docs as appropriate
> > ** accept the chang

libvirt uninstallable (was: Re: Improving Fedora boot time when libvirt is installed)

2023-02-06 Thread Richard W.M. Jones

So I think related to this thread, libvirt is now uninstallable in
Rawhide:

DEBUG util.py:443:  Error: 
DEBUG util.py:443:   Problem: problem with installed package 
fedora-release-38-0.23.noarch
DEBUG util.py:443:- package 
iscsi-initiator-utils-6.2.1.4-8.git2a8f9d8.fc38.x86_64 requires (fedora-release 
> 38-0.23 if fedora-release), but none of the providers can be installed
DEBUG util.py:443:- package 
libvirt-daemon-driver-storage-iscsi-9.0.0-2.fc38.x86_64 requires 
iscsi-initiator-utils, but none of the providers can be installed
DEBUG util.py:443:- package 
libvirt-daemon-driver-storage-9.0.0-2.fc38.x86_64 requires 
libvirt-daemon-driver-storage-iscsi = 9.0.0-2.fc38, but none of the providers 
can be installed
DEBUG util.py:443:- package libvirt-daemon-kvm-9.0.0-2.fc38.x86_64 requires 
libvirt-daemon-driver-storage = 9.0.0-2.fc38, but none of the providers can be 
installed
DEBUG util.py:443:- conflicting requests

I don't really understand the change that led to this:

https://src.fedoraproject.org/rpms/iscsi-initiator-utils/c/1e689cd0c6667eca838c85975a1b7a070209e5ad?branch=rawhide

Why was this line added?

+ Requires: (fedora-release > 38-0.23 if fedora-release)

I suppose it's related to this change in fedora-release:

https://src.fedoraproject.org/rpms/fedora-release/c/096fc7da49de5655db7aad17057e32191f2afe59?branch=rawhide

Did you mean >= in the conditional?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
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: libvirt uninstallable (was: Re: Improving Fedora boot time when libvirt is installed)

2023-02-06 Thread Gordon Messmer

On 2023-02-06 07:27, Richard W.M. Jones wrote:

Why was this line added?

+ Requires: (fedora-release > 38-0.23 if fedora-release)

I suppose it's related to this change in fedora-release:

https://src.fedoraproject.org/rpms/fedora-release/c/096fc7da49de5655db7aad17057e32191f2afe59?branch=rawhide



Yes.



Did you mean >= in the conditional?



Also yes.

https://src.fedoraproject.org/rpms/iscsi-initiator-utils/pull-request/11
___
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


Summary/Minutes from today's Fedora Flatpak Packaging SIG Meeting (2023-02-06)

2023-02-06 Thread Kalev Lember

=
#fedora-meeting: Fedora Flatpak Packaging SIG
=


Meeting started by kalev at 15:00:13 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting/2023-02-06/flatpak-sig.2023-02-06-15.00.log.html
.



Meeting summary
---
* Init process  (kalev, 15:00:13)

* Announcements  (kalev, 15:03:46)
  * gstreamer1-plugins-ugly-free and jxl-pixbuf-loader packages added to
the flatpak runtime  (kalev, 15:05:05)
  * longstanding Cheese issue with camera detection fixed, was due to
gstreamer1-plugins-good needing to be built differently in the
flatpak runtime  (kalev, 15:09:23)
  * libreoffice update done that was blocked by a java build issue
(kalev, 15:09:51)
  * new flatpak packages currently in testing: klavaro, remmina,
gtkhash, exaile, howl, exfalso, audacious  (kalev, 15:10:06)
  * would be useful if people could test new flatpaks and leave karma in
bodhi and report any issues to bugzilla  (kalev, 15:11:52)
  * flatpak-sig group created  (kalev, 15:12:33)
  * new fedmsg bot in irc channel  (kalev, 15:13:03)
  * flatpak 1.15.2 released  (kalev, 15:13:40)
  * LINK: https://github.com/flatpak/flatpak/releases/tag/1.15.2
(kalev, 15:13:41)

* IRC bot  (kalev, 15:14:10)
  * most people find the fedmsg bot too verbose and effectively killed
all communication in the channel  (kalev, 15:16:58)
  * ACTION: Kalev to do an ansible PR to drop the bot from the channel
(kalev, 15:17:34)

* How to test Fedora flatpaks  (kalev, 15:20:32)
  * ACTION: Kalev to start a wiki page with testing instructions
(kalev, 15:24:25)
  * LINK: https://fedoraproject.org/wiki/SIGs/Flatpak/Testing
(travier, 15:25:18)

* libmodulemd1  (kalev, 15:26:37)
  * yselkowitz[m] to look into fixing libmodulemd1 FTBFS  (kalev,
15:40:02)
  * Owen to talk to Jan to see how far along fedmod replacement is
(kalev, 15:40:28)
  * ACTION: tpopela to to talk to Jan to see how far along fedmod
replacement is :-)  (OwenTaylor[m], 15:41:04)
  * LINK: https://koji.fedoraproject.org/koji/taskinfo?taskID=96366742 -
btw. the build succeeded on aarch64..  (tpopela[m], 15:42:47)

* place to track issues  (kalev, 15:44:14)
  * LINK: https://gitlab.com/fedora/sigs   (travier, 15:46:04)

Meeting ended at 15:59:50 UTC.




Action Items

* Kalev to do an ansible PR to drop the bot from the channel
* Kalev to start a wiki page with testing instructions
* tpopela to to talk to Jan to see how far along fedmod replacement is
  :-)




Action Items, by person
---
* **UNASSIGNED**
  * Kalev to do an ansible PR to drop the bot from the channel
  * Kalev to start a wiki page with testing instructions
  * tpopela to to talk to Jan to see how far along fedmod replacement is
:-)




People Present (lines said)
---
* kalev (110)
* travier (19)
* zodbot (14)
* AllanDay[m] (9)
* tpopela[m] (7)
* bcotton (6)
* FelipeBorges[m] (5)
* OwenTaylor[m] (5)
* yselkowitz[m] (5)
* JanGrulich[m] (1)




Generated by `MeetBot`_ 0.4

.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
___
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


List of long term FTBFS packages to be retired this week and orphaned now

2023-02-06 Thread Miro Hrončok

Dear maintainers.

Based on the current fail to build from source policy, the following packages
should be retired from Fedora 38 approximately one week before branching.

5 weekly reminders are required, hence the retirement will happen
approximately this week, i.e. around 2023-02-08.
Since this is unfortunately after the branching,
packages will be retired on rawhide and f38.

This is the 5th reminder. I apologize for starting this process a bit later 
than required.


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


I plan to orphan the packages now, so maintainers who want to fix them can take 
them, and rerun the check later this week.
It is not enough to unorphan a package to save it from retirement, it must also 
be built in rawhide.
In case you want to postpone a retirement in some of the packages by a few 
days, email me (personally) ASAP.


The packages in rawhide were not successfully built at least since Fedora 35.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
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.

If you see a package that can be rebuilt, please do so.

Package(co)maintainers
==
ArpON   fab, sagarun
IQmol   jussilehtola
bowtie  jaruga, verdurin
btkbdd  lkundrak
cave9   jonathanspw
ccrypt  fab
cjdns   sdgathman
erlpmd  peter
free42  brouhaha
goddi   fab, go-sig
golang-github-adroll-goamz  eclipseo, go-sig
golang-github-aphistic-sweeteclipseo, go-sig
golang-github-aws-sdk-2-0.24eclipseo, go-sig
golang-github-cheekybits-genny  eclipseo, go-sig
golang-github-cockroachdb-gostdlib  eclipseo, go-sig
golang-github-cosmos72-gomacro  go-sig, qulogic
golang-github-dave-dst  eclipseo, go-sig
golang-github-docker-licensing  eclipseo, go-sig
golang-github-gdamore-optopia   fab, go-sig
golang-github-gopherjs  eclipseo, go-sig, jchaloup
golang-github-jung-kurt-gofpdf  eclipseo, go-sig
golang-github-latex eclipseo, go-sig
golang-github-maruel-panicparse eclipseo, go-sig
golang-github-maruel-panicparse-2   eclipseo, go-sig
golang-github-mattermost-xml-roundtrip-validatoreclipseo, go-sig
golang-github-mholt-certmagic-0.8   eclipseo, go-sig
golang-gonum-1-plot eclipseo, go-sig
golang-helm-3   dcavalca, go-sig
golang-istio-pkgeclipseo, go-sig
golang-sigs-k8s-application eclipseo, go-sig
golang-sigs-k8s-controller-runtime  eclipseo, go-sig
ipmiutilarcress
irssi-xmpp  lbazan, maha
kguitar davidcornette
libmobi avsej
libmodulemd1sgallagh
libndn-cxx  susmit
libyami kwizart
libyami-utils   kwizart
llvm10  petersen, sergesanspaille
llvm9.0 jistone, petersen, tstellar
lucidlife   pgordon
maven-scm   mizdebsk, trawets
nallchkr
nodejs-tape fab, patches
openas2 sdgathman
opencl-utilslupinix
ortporphan, sdgathman
percona-xtrabackup  orphan, slaanesh
phasex  tartina
php-doctrine-common remi, siwinski
php-hamcrestremi
php-laminas-code  

Re: Summary/Minutes from today's Fedora Flatpak Packaging SIG Meeting (2023-02-06)

2023-02-06 Thread Miro Hrončok

On 06. 02. 23 17:14, Kalev Lember wrote:


* libmodulemd1  (kalev, 15:26:37)
   * yselkowitz[m] to look into fixing libmodulemd1 FTBFS  (kalev,
     15:40:02)
   * Owen to talk to Jan to see how far along fedmod replacement is
     (kalev, 15:40:28)
   * ACTION: tpopela to to talk to Jan to see how far along fedmod
     replacement is 😄  (OwenTaylor[m], 15:41:04)
   * LINK: https://koji.fedoraproject.org/koji/taskinfo?taskID=96366742 -
     btw. the build succeeded on aarch64..  (tpopela[m], 15:42:47)


BTW I saw yselkowitz merging their own PR that fixes this, but nobody built it. 
The package is now orphaned and looking for a new maintainer, but it will be 
retired anyway this week unless somebody actually builds it.


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


Re: Summary/Minutes from today's Fedora Flatpak Packaging SIG Meeting (2023-02-06)

2023-02-06 Thread Yaakov Selkowitz
On Mon, 2023-02-06 at 17:25 +0100, Miro Hrončok wrote:
> On 06. 02. 23 17:14, Kalev Lember wrote:
> > 
> > * libmodulemd1  (kalev, 15:26:37)
> >    * yselkowitz[m] to look into fixing libmodulemd1 FTBFS  (kalev,
> >  15:40:02)
> >    * Owen to talk to Jan to see how far along fedmod replacement is
> >  (kalev, 15:40:28)
> >    * ACTION: tpopela to to talk to Jan to see how far along fedmod
> >  replacement is 😄  (OwenTaylor[m], 15:41:04)
> >    * LINK: https://koji.fedoraproject.org/koji/taskinfo?taskID=96366742 -
> >  btw. the build succeeded on aarch64..  (tpopela[m], 15:42:47)
> 
> BTW I saw yselkowitz merging their own PR that fixes this, but nobody built
> it. 
> The package is now orphaned and looking for a new maintainer, but it will be
> retired anyway this week unless somebody actually builds it.

It's taken and built now.

-- 
Yaakov Selkowitz
Principal Software Engineer - Platform Enablement
Red Hat, Inc.
___
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: libvirt uninstallable (was: Re: Improving Fedora boot time when libvirt is installed)

2023-02-06 Thread Zbigniew Jędrzejewski-Szmek
On Mon, Feb 06, 2023 at 07:56:50AM -0800, Gordon Messmer wrote:
> On 2023-02-06 07:27, Richard W.M. Jones wrote:
> > Why was this line added?
> > 
> > + Requires: (fedora-release > 38-0.23 if fedora-release)
> > 
> > I suppose it's related to this change in fedora-release:
> > 
> > https://src.fedoraproject.org/rpms/fedora-release/c/096fc7da49de5655db7aad17057e32191f2afe59?branch=rawhide
> 
> 
> Yes.
> 
> 
> > Did you mean >= in the conditional?
> 
> 
> Also yes.
> 
> https://src.fedoraproject.org/rpms/iscsi-initiator-utils/pull-request/11

My bad. I suggested '>'. Usually this would work because there'd be a dist tag,
but fedora-release doesn't have the dist tag.

There's another issue: the dependency should be on fedora-release-common
instead -> 
https://src.fedoraproject.org/rpms/iscsi-initiator-utils/pull-request/12.

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


Re: List of long term FTBFS packages to be retired this week and orphaned now

2023-02-06 Thread Stuart D Gathman

On Mon, 6 Feb 2023, Miro Hrončok wrote:

I plan to orphan the packages now, so maintainers who want to fix them can 
take them, and rerun the check later this week.
It is not enough to unorphan a package to save it from retirement, it must 
also be built in rawhide.
In case you want to postpone a retirement in some of the packages by a few 
days, email me (personally) ASAP.


I finally found some voodoo to get cjdns-21.1 to build in f37.  Working
on rawhide.

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


Fedora 38 mass branching postpone for 1 day

2023-02-06 Thread Tomas Hrcka
Hello, the mass branching of Fedora Linux 38 was planned to happen on
2023-02-07.
Due to traveling from FOSDEM and the re-signing of rawhide with a new
key we will postpone the branching to 2023-02-08.

Sorry for the inconvenience

Tomas Hrcka
Fedora release engineering
___
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, 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