Fedora-Cloud-33-20201112.0 compose check report

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-2020.0): ID: 721130 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://op

Schedule for Thursday's FPC Meeting (2020-11-12 17:00 UTC)

 Following is the list of topics that will be discussed in the FPC meeting Thursday at 2020-11-12 17:00 UTC in #fedora-meeting-1 on irc.freenode.net.  Local time information (via. uitime): = Day: Thursday == 2020-11-12 09:00 PST US/Pacific 2020-11-12 1

Re: Fedora 34 Change proposal: Remove and deprecate nscd in favour of sssd and systemd-resolved (Self-Contained Change)

On Wed, Nov 11, 2020 at 7:41 AM Pavel Březina wrote: > > On 11/5/20 1:58 PM, Nico Kadel-Garcia wrote: > > On Thu, Nov 5, 2020 at 6:39 AM Petr Menšík wrote: > >> > >> No, no, NO again. > >> > >> nscd has no important active bugs in Fedora. I am not sure what bugs are > >> mentioned, but just a few

Re: Help needed: vtk FTBFS, undefined reference to std::__detail::__to_chars_10_impl(char*, unsigned int, unsigned int)::__digits

* Jonathan Wakely: > On 10/11/20 23:24 +, Will Crawford wrote: >>On Tue, 10 Nov 2020 at 11:56, Sandro Mani wrote: >> >>/usr/bin/ld: >>> CMakeFiles/vtkIOXMLCxxTests.dir/TestXMLHyperTreeGridIO.cxx.o (symbol >>> from plugin): undefined reference to symbol >>> '_ZZNSt8__detail18__to_chars_10_impl

Re: Help needed: vtk FTBFS, undefined reference to std::__detail::__to_chars_10_impl(char*, unsigned int, unsigned int)::__digits

On 10/11/20 23:24 +, Will Crawford wrote: On Tue, 10 Nov 2020 at 11:56, Sandro Mani wrote: /usr/bin/ld: CMakeFiles/vtkIOXMLCxxTests.dir/TestXMLHyperTreeGridIO.cxx.o (symbol from plugin): undefined reference to symbol '_ZZNSt8__detail18__to_chars_10_implIjEEvPcjT_E8__digits@@LLVM_11' /usr/b

Fedora-Rawhide-20201111.n.0 compose check report

Missing expected images: Xfce raw-xz armhfp Compose PASSES proposed Rawhide gating check! All required tests passed Failed openQA tests: 6/177 (x86_64), 14/115 (aarch64) New failures (same test not failed in Fedora-Rawhide-20201110.n.0): ID: 720508 Test: x86_64 KDE-live-iso desktop_printi

Fedora-Cloud-31-20201111.0 compose check report

No missing expected images. Passed openQA tests: 7/7 (x86_64), 7/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..

Fedora-Cloud-32-20201111.0 compose check report

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-20201110.0): ID: 720360 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://op

Fedora-Cloud-33-20201111.0 compose check report

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-20201110.0): ID: 720293 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://op

Re: Proposed updates to the FESCo updates policy document

Il 11/11/20 16:56, Kevin Fenzi ha scritto: > Greetings. > > FESCo is looking to update the updates policy document that is here: > > https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ > > For the most part the updates are not changing any policy, but simply > removing old/no longer accurate

Re: Orphaned packages looking for new maintainers (see note about xinetd)​

On Wed, Nov 11, 2020 at 5:40 PM Wolfgang Ulbrich wrote: > I know where my package are listed at > https://src.fedoraproject.org/dashboard/projects :) > But... > [root@mother rave]# dnf repoquery --whatrequires sgpio > Letzte Prüfung auf abgelaufene Metadaten: vor 1:28:41 am Mi 11 Nov 2020 > 17:0

Re: Orphaned packages looking for new maintainers (see note about xinetd)​

I know where my package are listed at https://src.fedoraproject.org/dashboard/projects :) But... [root@mother rave]# dnf repoquery --whatrequires sgpio Letzte Prüfung auf abgelaufene Metadaten: vor 1:28:41 am Mi 11 Nov 2020 17:04:25 CET. [root@mother rave]# dnf repoquery --whatrequires sgpio Let

Re: What to do with - in release tag?

On 11.11.2020 17:00, Bruno Wolff III wrote: There already was a 4.4 release and the package is currently a post release snapshot and has a release of 2.20200513gitc570c61%{dist}. So in this case I think I want 3.git1%{?dist} to follow your suggestion? Yes. Also you can continue to use the clas

Re: Lightly-maintained packages (was: Summary/Minutes from today's FESCo Meeting (2020-11-11))

On Wed, Nov 11, 2020 at 06:05:20PM +0100, Miroslav Suchý wrote: > Dne 11. 11. 20 v 16:47 David Cantrell napsal(a): > > * #2475 proposal: let's develop the idea of a new repo for > >   lightly-maintained packages  (dcantrell, 15:16:41) > > For the record - the initial ticket can be found here: >

Arpwatch updated to 3.1 – testing and auditing appreciated!

I recently took maintainership of arpwatch after it was orphaned by the previous maintainer. This package has a particularly long history in Fedora, carries quite a few patches, and had seen no upstream releases in many years until late 2019. I just updated Rawhide to ship the latest upstream v

Re: What to do with - in release tag?

Maybe follow this guideline? https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_versioning_prereleases_with_tilde Although it it not clear to me if this is pre-release or post release or what it actually is. Vít Dne 11. 11. 20 v 16:09 Bruno Wolff III napsal(a): I looked

Re: Lightly-maintained packages (was: Summary/Minutes from today's FESCo Meeting (2020-11-11))

Dne 11. 11. 20 v 16:47 David Cantrell napsal(a): > * #2475 proposal: let's develop the idea of a new repo for >   lightly-maintained packages  (dcantrell, 15:16:41) For the record - the initial ticket can be found here: https://pagure.io/fesco/issue/2475 We already have "lightly-maintained pack

Fedora-Rawhide-20201110.n.0 compose check report

Missing expected images: Xfce raw-xz armhfp Compose PASSES proposed Rawhide gating check! All required tests passed Failed openQA tests: 5/177 (x86_64), 11/115 (aarch64) New failures (same test not failed in Fedora-Rawhide-20201109.n.0): ID: 719599 Test: x86_64 Workstation-live-iso deskt

Re: What to do with - in release tag?

On Wed, Nov 11, 2020 at 16:53:26 +0100, Vitaly Zaitsev via devel wrote: On 11.11.2020 16:09, Bruno Wolff III wrote: If not, should I replace the - with a . in the version or should I move git.1 into the release. This is the first tag using this naming pattern, so I don't know the next tag wil

Re: Fedora 34 Change proposal: Remove and deprecate nscd in favour of sssd and systemd-resolved (Self-Contained Change)

* Petr Menšík: >> Fedora made the decision to promote systemd-resolved as a local DNS >> cache. To me, that means that we can gradually remove other DNS caches >> from the distribution. > I maintain also dnsmasq and I doubt there is reason to remove it from > the distribution. I would oppose if

Re: Fedora 34 Change proposal: Remove and deprecate nscd in favour of sssd and systemd-resolved (Self-Contained Change)

On Sa, 07.11.20 15:33, Marius Schwarz (fedora...@cloud-foo.de) wrote: > Am 05.11.20 um 12:39 schrieb Petr Menšík: > > There is no controversy with nscd, it just caches names and nothing > > more. I think this is its advantage. Unless there is any stronger > > reason, I am against this change in ad

Proposed updates to the FESCo updates policy document

Greetings. FESCo is looking to update the updates policy document that is here: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ For the most part the updates are not changing any policy, but simply removing old/no longer accurate information (taskotron no longer exists, bodhi is alway

Re: Orphaned packages looking for new maintainers (see note about xinetd)

On Wed, Nov 11, 2020 at 3:01 PM Chris Adams wrote: > Are there replacements for the old services built in to xinetd? Not that I know of as being integrated, although writing such servers (often in perl) can often be seen in training materials about network socket programming in a few dozen lines

Re: What to do with - in release tag?

On 11.11.2020 16:09, Bruno Wolff III wrote: If not, should I replace the - with a . in the version or should I move git.1 into the release. This is the first tag using this naming pattern, so I don't know the next tag will sort properly if I keep it in the version. Version: 4.4 Release 1.git1

Re: Orphaned packages looking for new maintainers (see note about xinetd)

On Wed, 11 Nov 2020 at 10:01, Chris Adams wrote: > Once upon a time, Petr Pisar said: > > I believe it's unlikely that somobody will adopt xinetd. It was orphaned > > because its maintainer orphaned all his packages. > > Are there replacements for the old services built in to xinetd? It's a > s

Summary/Minutes from today's FESCo Meeting (2020-11-11)

= #fedora-meeting-2: FESCO (2020-11-11) = Meeting started by dcantrell at 15:00:45 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2020-11-11/fesco.2020-11-11-15.00.log.html . Meetin

Re: Fedora 34 Change proposal: Remove and deprecate nscd in favour of sssd and systemd-resolved (Self-Contained Change)

* Chris Adams: > Once upon a time, Florian Weimer said: >> Fedora made the decision to promote systemd-resolved as a local DNS >> cache. To me, that means that we can gradually remove other DNS caches >> from the distribution. > > Since when does Fedora choosing a default mean other options must

Re: What to do with - in release tag?

On Wed, Nov 11, 2020 at 4:30 PM Bruno Wolff III wrote: > > I looked at > https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/ > and didn't see dashes specifically covered. > > In my case, squashfs-tools has a new upstream release tagged 4.4-git.1 . > I'm guessing that using 4.4-gi

Re: Fedora 34 Change proposal: Remove and deprecate nscd in favour of sssd and systemd-resolved (Self-Contained Change)

* Ben Cotton: > https://fedoraproject.org/wiki/Changes/RemoveNSCD > > == Summary == > This proposal intends to replace the ''nscd'' cache for named services > with ''systemd-resolved'' for the `hosts` database and the ''sssd'' > daemon for everything else. > > == Owner == > * Name: [[User:submachi

Re: patch applied without package maintainers' approve

On 11/11/20 4:17 PM, Peter Robinson wrote: Also note there is no packaging requirements to get approval from package maintainers. https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/ "Provenpackagers should try to communicate with owners of a package in bugzilla, irc or email pri

What to do with - in release tag?

I looked at https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/ and didn't see dashes specifically covered. In my case, squashfs-tools has a new upstream release tagged 4.4-git.1 . I'm guessing that using 4.4-git.1 as the version would be at least confusing and might be prohi

Re: Fedora 34 Change proposal: Remove and deprecate nscd in favour of sssd and systemd-resolved (Self-Contained Change)

Once upon a time, Florian Weimer said: > Fedora made the decision to promote systemd-resolved as a local DNS > cache. To me, that means that we can gradually remove other DNS caches > from the distribution. Since when does Fedora choosing a default mean other options must be removed from the dis

Re: patch applied without package maintainers' approve

> I'm one of package maintainers of rdma-core. There is a patch > applied without any maintainers' review/approve. I had sent two emails > to patch committer to ask him/her to push the change to upstream. > But never get response. So someone pinged me on IRC about this, I never saw the emails beca

Re: Orphaned packages looking for new maintainers (see note about xinetd)

Once upon a time, Petr Pisar said: > I believe it's unlikely that somobody will adopt xinetd. It was orphaned > because its maintainer orphaned all his packages. Are there replacements for the old services built in to xinetd? It's a surprise, but there are still network devices for service provi

Re: Fedora 34 Change proposal: Remove and deprecate nscd in favour of sssd and systemd-resolved (Self-Contained Change)

Hi Florian, more below... On 11/11/20 11:39 AM, Florian Weimer wrote: > * Petr Menšík: >>> This proposal is about nscd, not systemd-resolved. > >> systemd-resolved is mentioned in the title and the body of proposal. So >> it seems it is about it. > > Fedora made the decision to promote systemd-

Re: Fedora 34 Change proposal: Remove and deprecate nscd in favour of sssd and systemd-resolved (Self-Contained Change)

On 11/5/20 1:58 PM, Nico Kadel-Garcia wrote: On Thu, Nov 5, 2020 at 6:39 AM Petr Menšík wrote: No, no, NO again. nscd has no important active bugs in Fedora. I am not sure what bugs are mentioned, but just a few active bugs are on glibc component in Fedora. Therefore it seems just fine no com

Fedora rawhide compose report: 20201111.n.0 changes

OLD: Fedora-Rawhide-20201110.n.0 NEW: Fedora-Rawhide-2020.n.0 = SUMMARY = Added images:0 Dropped images: 6 Added packages: 16 Dropped packages:5 Upgraded packages: 84 Downgraded packages: 0 Size of added packages: 343.10 MiB Size of dropped packages

Re: Help needed: vtk FTBFS, undefined reference to std::__detail::__to_chars_10_impl(char*, unsigned int, unsigned int)::__digits

On Wed, Nov 11, 2020 at 4:05 AM Sandro Mani wrote: > > > Can you try disabling LTO by adding: > > %global _lto_cflags %{nil} > > to your spec file and see if that helps. > > Indeed, with LTO disabled it builds, thanks for the tip! > He probably saw this, but copying in Jeff to add to his LTO lis

Re: Fedora 34 Change proposal: Remove and deprecate nscd in favour of sssd and systemd-resolved (Self-Contained Change)

* Nico Kadel-Garcia: > On Thu, Nov 5, 2020 at 6:39 AM Petr Menšík wrote: >> >> No, no, NO again. >> >> nscd has no important active bugs in Fedora. I am not sure what bugs are >> mentioned, but just a few active bugs are on glibc component in Fedora. >> Therefore it seems just fine no commits are

Re: Fedora 34 Change proposal: Remove and deprecate nscd in favour of sssd and systemd-resolved (Self-Contained Change)

* Petr Menšík: > On 11/5/20 12:49 PM, Florian Weimer wrote: >> * Petr Menšík: >> >> >> nscd has more usage downstream, leading to bugs such as: >> >> > > I have very limited understanding of sssd principles. But I think it is > not compara

Re: Help needed: vtk FTBFS, undefined reference to std::__detail::__to_chars_10_impl(char*, unsigned int, unsigned int)::__digits

Can you try disabling LTO by adding: %global _lto_cflags %{nil} to your spec file and see if that helps. Indeed, with LTO disabled it builds, thanks for the tip! Sandro ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an e

Re: Orphaned packages looking for new maintainers (see note about xinetd)

On Mon, Nov 02, 2020 at 11:25:39AM -, Michael J Gruber wrote: > > = NOTE about xinetd = > > > > Many packagers are listed as affected by xinetd. The dependency chain is: > > > > cvs (kasal, ppisar) > > cvs-inetd.noarch requires xinetd > > > > git (amahdal, besser8