[Bug 1867838] perl-Time-HiRes-1.9764 is available

2020-08-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1867838

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-Time-HiRes-1.9764-458.
   ||fc33



--- Comment #1 from Petr Pisar  ---
A bug-fix release suitable for Fedora ≥ 32.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1867838] perl-Time-HiRes-1.9764 is available

2020-08-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1867838

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|ppi...@redhat.com   |
   Doc Type|--- |If docs needed, set a value




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1867809] perl-Devel-PPPort-3.59 is available

2020-08-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1867809

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-Devel-PPPort-3.59-1.fc
   ||33
 Resolution|--- |RAWHIDE
Last Closed||2020-08-11 05:38:59



--- Comment #1 from Petr Pisar  ---
Major changes. Safer for Rawhide only.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1867692] libsane-airscan-0.99.12-1.fc33: airscan driver crashes in mock: file airscan-wsdd.c: line 1696 (wsdd_cleanup): assertion failed: (ll_empty(_finding_list))

2020-08-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1867692

Zdenek Dohnal  changed:

   What|Removed |Added

   Priority|unspecified |medium
   Severity|unspecified |high



--- Comment #4 from Zdenek Dohnal  ---
Hi Petr,

thanks for the reproducer, I'm now able to reproduce with following steps:

$ mock -r fedora-33-x86_64 init
$ mock -r fedora-33-x86_64 install sane-backends
$ mock -r fedora-33-x86_64 install sane-backends-drivers-scanners
$ mock -r fedora-33-x86_64 shell
 sh-5.0# scanimage
Output format is not set, using pnm as a default.
Segmentation fault (core dumped)

I'll try the latest version, if it helps.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Zanata removal is soon, please finish migration

2020-08-10 Thread Jean-Baptiste Holcroft
Dear project maintainers,

there is still a bunch of project that did not migrated to Weblate yet.
Zanata will be removed in a few weeks now, it's time to finish your migration 
to Weblate.

It basically is a few questions to answer to allow me to do the first 
configuration.
Requirements: store pot file in your repository

If you are not using Github and don't want to allow Weblate to write in your 
repository, you'll do the merge requests yourself.

Here is the list of projects: please comment directly in the related link.

candlepin   
https://github.com/candlepin/subscription-manager/commit/d802e5634d3d6eb5ebfd17e6817dbaaa3545fce3
certmonger  https://pagure.io/certmonger/issue/141
classified-ads  https://github.com/operatornormal/classified-ads/issues/8
docker-anaconda-addon   https://bugzilla.redhat.com/show_bug.cgi?id=1785029
fedora-modularity-translations  
https://github.com/fedora-modularity/ModulemdTranslationHelpers/issues/5
fedora-podcast  https://pagure.io/g11n/issue/56
fedora-software https://github.com/misli/fedora-software/issues/19
freeipa https://pagure.io/freeipa/issue/8159
gfs2-utils  https://bugzilla.redhat.com/show_bug.cgi?id=1787299
gss-ntlmssp https://pagure.io/gssntlmssp/issue/15
hivex   https://bugzilla.redhat.com/show_bug.cgi?id=1787302
ibus-chewinghttps://github.com/definite/ibus-chewing/issues/150
im-chooser  https://pagure.io/im-chooser/issue/1
imsettings  
https://bitbucket.org/tagoh/imsettings/issues/4/please-migrate-to-the-new-fedora
libguestfs  https://bugzilla.redhat.com/show_bug.cgi?id=1787301
libuser https://pagure.io/libuser/issue/43
mediawriter https://github.com/FedoraQt/MediaWriter/issues/224
mlocate https://pagure.io/mlocate/issue/49
newthttps://pagure.io/newt/issue/12
oscap-anaconda-addonhttps://bugzilla.redhat.com/show_bug.cgi?id=1785030
pam_krb5https://pagure.io/pam_krb5/issue/3
passwd  https://pagure.io/passwd/issue/2
plymouthhttps://gitlab.freedesktop.org/plymouth/plymouth/issues/93
python-fedora   https://github.com/fedora-infra/python-fedora/issues/224
python-meh  https://github.com/rhinstaller/python-meh/issues/25
python-simpleline   
https://github.com/rhinstaller/python-simpleline/issues/63
rhel-comps  https://bugzilla.redhat.com/show_bug.cgi?id=1789350
selinux https://github.com/SELinuxProject/selinux/issues/198
setroubleshoot  https://github.com/fedora-selinux/setroubleshoot/issues/89
system-config-kdump https://bugzilla.redhat.com/show_bug.cgi?id=1789353
system-config-kickstart 
https://github.com/rhinstaller/system-config-kickstart/issues/8
systemd https://github.com/systemd/systemd/issues/14531
tvtime  
udisks  https://github.com/storaged-project/udisks/issues/719
usermodehttps://pagure.io/usermode/issue/5
v4l-utils   https://bugzilla.kernel.org/show_bug.cgi?id=206251
virt-top
volume_key  https://pagure.io/volume_key/issue/21


Please keep me in CC if you answer here

I'm sometimes in IRC as jibec on #devel and #fedora-fr

Jean-Baptiste // jibecfed
___
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


[Bug 1867809] perl-Devel-PPPort-3.59 is available

2020-08-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1867809

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|jples...@redhat.com,|
   |ppi...@redhat.com   |
   Doc Type|--- |If docs needed, set a value




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Re: PostgreSQL 13 - Fedora 33 Self-Contained Change proposal

2020-08-10 Thread Bruno Wolff III

On Tue, Jul 07, 2020 at 15:16:22 -0400,
 Ben Cotton  wrote:

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

== Summary ==
Update of PostgreSQL (`postgresql` and `libpq` components) in Fedora
from version 12 to version 13 in the non-modular (main) builds.


They are going to release 13beta3 on Thursday, so we aren't going to see 
a 13 release until very close to Fedora 33's release.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: LTO and the F33 mass rebuild

2020-08-10 Thread Jeff Law
On Sun, 2020-08-09 at 12:02 +0200, Fabio Valentini wrote:
> On Sun, Aug 9, 2020 at 12:03 AM Jeff Law  wrote:
> > So I've done two passes over the F33 build failures here:
> > 
> > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html
> 
> Hi Jeff,
> 
> Thanks for looking at the failures, it's really appreciated!
> 
> Be aware that the f33-failures.html page is not complete though, since
> packages for which there was an attempted rebuild *after* the mass
> rebuild are removed from the list, whether the builds succeeded or
> not. So it's possible that you missed builds that fail for LTO-related
> issues, just because they're no longer showing up in the list. The
> list of bugs blocking the F33FTBFS bug in bugzilla [0] might be
> helpful here. And the f33-need-rebuild list [1] should give you a
> complete picture of everything that has not successfully been rebuilt
> for f33 yet.
> 
> Fabio
> 
> [0]: https://bugzilla.redhat.com/show_bug.cgi?id=1803234
> [1]: https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html
I've gone through the f33-need-rebuild page and taken care of a variety of
things.  I've got a half-dozen packages left (openblas, arm-none-eabi-gcc-cs,
cross-gcc gdb and radamsa).  Otherwise if I haven't taken the BZ, then I don't
currently see the failure as being LTO related.

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


[389-devel] 389 DS nightly 2020-08-11 - 95% PASS

2020-08-10 Thread vashirov
https://fedorapeople.org/groups/389ds/ci/nightly/2020/08/11/report-389-ds-base-1.4.4.4-20200810gitea39a99.fc32.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org


Re: Fedora 33 Mass Branching

2020-08-10 Thread Tom Stellard

On 8/9/20 3:16 PM, Mohan Boddu wrote:

Hello All,

Fedora 33 will be branched from rawhide on August 11th 2020 as per the
Fedora 33 schedule[1]. The process takes about a day and everything
should be ready by August 12th 2020. You can still be able to build
packages normally until then, but after the mass branching, rawhide
and F33 will be separated.



How will this affect any outstanding side-tags that inherit from the f33 
tag?  Will we need to re-tag the packages into an f34-based side-tag?


-Tom


We will send another email once the branching is done.

Thanks,
Mohan Boddu.

[1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html
___
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
___
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


___
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


[Bug 1867838] New: perl-Time-HiRes-1.9764 is available

2020-08-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1867838

Bug ID: 1867838
   Summary: perl-Time-HiRes-1.9764 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Time-HiRes
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 1.9764
Current version/release in rawhide: 1.9760-440.fc32
URL: http://search.cpan.org/dist/Time-HiRes/

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


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


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


Based on the information from anitya:
https://release-monitoring.org/project/3466/


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Fedora rawhide compose report: 20200810.n.0 changes

2020-08-10 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20200809.n.0
NEW: Fedora-Rawhide-20200810.n.0

= SUMMARY =
Added images:1
Dropped images:  0
Added packages:  3
Dropped packages:5
Upgraded packages:   91
Downgraded packages: 0

Size of added packages:  7.39 MiB
Size of dropped packages:9.93 MiB
Size of upgraded packages:   6.67 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Workstation live aarch64
Path: 
Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20200810.n.0.iso

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: ansible-collection-ansible-netcommon-1.1.2-1.fc33
Summary: Ansible Network Collection for Common Code
RPMs:ansible-collection-ansible-netcommon
Size:165.75 KiB

Package: ansible-collection-community-general-1.0.0-1.fc33
Summary: Modules and plugins supported by Ansible community
RPMs:ansible-collection-community-general
Size:1.60 MiB

Package: easyrpg-player-0.6.2.1-4.fc33
Summary: Game interpreter for RPG Maker 2000/2003 and EasyRPG games
RPMs:easyrpg-player
Size:5.63 MiB


= DROPPED PACKAGES =
Package: glpi-9.4.6-2.fc33
Summary: Free IT asset management software
RPMs:glpi
Size:8.95 MiB

Package: iipsrv-1.1.0-3.0.fc33
Summary: Light-weight streaming for viewing and zooming of ultra 
high-resolution images
RPMs:iipsrv iipsrv-httpd-fcgi
Size:891.69 KiB

Package: php-elvanto-litemoji-2.0.1-3.fc33
Summary: Conversion of unicode, HTML and shortcode emoji
RPMs:php-elvanto-litemoji
Size:26.57 KiB

Package: php-scssphp-scssphp-1.0.8-2.fc33
Summary: Compiler for SCSS
RPMs:php-scssphp-scssphp
Size:74.66 KiB

Package: php-true-punycode-2.1.1-10.fc33
Summary: A Bootstring encoding of Unicode for IDNA
RPMs:php-true-punycode
Size:13.98 KiB


= UPGRADED PACKAGES =
Package:  CubicSDR-0.2.5-9.20200226gitd2f9333.fc33
Old package:  CubicSDR-0.2.5-7.20200226gitd2f9333.fc33
Summary:  Cross-Platform Software-Defined Radio Panadapter
RPMs: CubicSDR
Size: 5.58 MiB
Size change:  9.05 KiB
Changelog:
  * Sat Aug 08 2020 Scott Talbert  - 0.2.5-8.20200226gitd2f9333
  - Rebuild for wxWidgets 3.1.4

  * Sun Aug 09 2020 Scott Talbert  - 0.2.5-9.20200226gitd2f9333
  - Rebuild for wxWidgets 3.1.4 (for real)


Package:  R-R.rsp-0.44.0-1.fc33
Old package:  R-R.rsp-0.43.2-4.fc33
Summary:  Dynamic Generation of Scientific Reports
RPMs: R-R.rsp
Size: 1.53 MiB
Size change:  -4.13 KiB
Changelog:
  * Sun Aug 09 2020 Elliott Sales de Andrade  - 
0.44.0-1
  - Update to latest version (rhbz#1855381)


Package:  R-devtools-2.3.1-1.fc33
Old package:  R-devtools-2.1.0-3.fc33
Summary:  Tools to Make Developing R Packages Easier
RPMs: R-devtools
Size: 357.40 KiB
Size change:  19.01 KiB
Changelog:
  * Sun Aug 09 2020 Elliott Sales de Andrade  - 
2.3.1-1
  - Update to latest version (rhbz#1823027)


Package:  R-ggplot2-3.3.2-1.fc33
Old package:  R-ggplot2-3.2.1-4.fc33
Summary:  Create Elegant Data Visualisations Using the Grammar of Graphics
RPMs: R-ggplot2
Size: 3.87 MiB
Size change:  129.27 KiB
Changelog:
  * Sun Aug 02 2020 Elliott Sales de Andrade  - 
3.2.1-5
  - Add R-profvis to BuildRequires

  * Mon Aug 03 2020 Elliott Sales de Andrade  - 
3.3.2-1
  - Update to latest version (rhbz#1810676)


Package:  R-gh-1.1.0-1.fc33
Old package:  R-gh-1.0.1-6.fc33
Summary:  GitHub API
RPMs: R-gh
Size: 122.42 KiB
Size change:  62.14 KiB
Changelog:
  * Sun Aug 09 2020 Elliott Sales de Andrade  - 
1.1.0-1
  - Update to latest version (rhbz#1838485)


Package:  R-magick-2.4.0-1.fc33
Old package:  R-magick-2.4.0-1.fc33~bootstrap
Summary:  Advanced Graphics and Image-Processing in R
RPMs: R-magick
Size: 23.41 MiB
Size change:  9.20 KiB

Package:  R-pdftools-2.3.1-4.fc33
Old package:  R-pdftools-2.3.1-3.fc33
Summary:  Text Extraction, Rendering and Converting of PDF Documents
RPMs: R-pdftools
Size: 514.04 KiB
Size change:  -105 B
Changelog:
  * Sun Aug 09 2020 Elliott Sales de Andrade  - 
2.3.1-4
  - Re-enable full checks


Package:  R-pillar-1.4.6-2.fc33
Old package:  R-pillar-1.4.4-3.fc33
Summary:  Coloured Formatting for Columns
RPMs: R-pillar
Size: 193.96 KiB
Size change:  -2.56 KiB
Changelog:
  * Sun Aug 09 2020 Elliott Sales de Andrade  - 
1.4.6-1
  - Update to latest version (rhbz#1855466)

  * Sun Aug 09 2020 Elliott Sales de Andrade  - 
1.4.6-2
  - Re-enable checks


Package:  R-rsvg-2.1-4.fc33
Old package:  R-rsvg-2.1-3.fc33
Summary:  Render SVG Images into PDF, PNG, PostScript, or Bitmap Arrays
RPMs: R-rsvg
Size: 1.25 MiB
Size change:  342 B
Changelog:
  * Sun Aug 09 2020 Elliott Sales de Andrade  - 2.1-4
  - Enable full checks again


Package:  R-tibble-3.0.3-1.fc33~bootstrap
Old package:  R-tibble

Re: ARM: Installed (but unpackaged) file(s) found: /usr/bin/....gdb-index-9pY4kY

2020-08-10 Thread Jeff Law
On Tue, 2020-08-04 at 21:36 +0200, Florian Weimer wrote:
> * Jeff Law:
> 
> > Actually, isn't it "just" 234MB.  Still I'm surprised why that failed.  Do 
> > we
> > have more than one build running at a time on those boxes?
> 
> It's a 32-bit build.  I assume it's not the first large allocation.
> (FWIW, GDB always prints “virtual memory exhausted”, even if the malloc
> failure has a different cause.)
> 
> Does LTO produce more complicated debugging information?  Then maybe
> disabling LTO on armhfp is a workaround.  There's also a way to disable
> debuginfo package generation altogether, something along these lines
> (untested):
It doesn't really make it more complicated, but it does scramble it in fun an
interesting ways.  I'd hazard a guess it changed things in such a way as to
confuse the bits that add the index.

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


[Bug 1867810] New: perl-Mojolicious-8.58 is available

2020-08-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1867810

Bug ID: 1867810
   Summary: perl-Mojolicious-8.58 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Mojolicious
  Keywords: FutureFeature, Triaged
  Assignee: emman...@seyman.fr
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr,
perl-devel@lists.fedoraproject.org,
robinlee.s...@gmail.com, yan...@declera.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 8.58
Current version/release in rawhide: 8.51-1.fc33
URL: https://metacpan.org/release/Mojolicious

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


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


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


Based on the information from anitya:
https://release-monitoring.org/project/5966/


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1867809] New: perl-Devel-PPPort-3.59 is available

2020-08-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1867809

Bug ID: 1867809
   Summary: perl-Devel-PPPort-3.59 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Devel-PPPort
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 3.59
Current version/release in rawhide: 3.58-1.fc33
URL: http://search.cpan.org/dist/Devel-PPPort/

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


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


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


Based on the information from anitya:
https://release-monitoring.org/project/5760/


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Re: Help needed to fix a FTBFS (shaderc)

2020-08-10 Thread Leigh Scott
> On Mon, Aug 10, 2020 at 6:55 PM Leigh Scott  wrote:
> 
> Initially that was the bad thing, but the upstream project appears to
> have split those two libraries out, I'd prefer to keep tracking
> upstream in rawhide, maybe we can get upstream to address the lack of
> ABI in the disaster that is glslang.
> 
> Dave.
Agreed, shaderc has been patched to work with the new version.
There aren't the many packages using glslang.

dolphin-emu-0:5.0.12247-1.fc33.src
ffmpeg-0:4.3.1-5.fc33.src
libplacebo-0:2.72.0-2.fc33.src
mangohud-0:0.4.1-3.fc33.src
shaderc-0:2020.1-1.fc33.src
vulkan-validation-layers-0:1.2.148.0-1.fc33.src
___
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


Testing request: OpenConnect VPN with 2FA on Rawhide

2020-08-10 Thread Adam Williamson
Hi folks! Sending this with fairly wide distribution in the hopes of
finding someone with appropriate configuration.

There's a proposed blocker bug for F33:
https://bugzilla.redhat.com/show_bug.cgi?id=1830343

which reports a hang in the GNOME Shell VPN auth flow when trying to
connect to an OpenConnect VPN with a 2FA configuration where - if I
understand the report correctly - the user enters their ID and the
first factor first, then the server prompts for the second factor; at
the point where the second factor is entered, nm-openconnect-auth-
dialog hangs, and the connection never completes. There's a video
demonstrating the issue in the bug.

We're concerned about this as a potential blocker issue, but we're not
sure how many people have a potentially affected VPN config, and if so,
whether the bug is reproducible on them all. So if you have what you
think is a similar VPN config - using OpenConnect with 2FA - it'd be
great if you could test it on Fedora Rawhide, using a virtual machine
obviously unless you already run Rawhide or are very comfortable with
very pre-release operating systems :)

If you try it, please do report your results along with details of your
VPN config back here and/or to the bug report. Thanks!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Help needed to fix a FTBFS (shaderc)

2020-08-10 Thread David Airlie
On Mon, Aug 10, 2020 at 6:55 PM Leigh Scott  wrote:
>
> > On Mon, Aug 10, 2020 at 2:57 AM Leigh Scott  > wrote:
> >
> > Yeah glslang sucks in terms of providing a stable API, I think
> > upstream would need to address these things,
> >
> > Though I hadn't realised it would FTBFS things that badly.
> >
> > Dave.
>
> Can we revert back to the old version please?, it builds fine.
> Here's a working spec file  
> https://leigh123linux.fedorapeople.org/pub/SPECS/glslang.spec
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=49015264
>
> TBH it looks like you were having a bad cmake day :-)

Initially that was the bad thing, but the upstream project appears to
have split those two libraries out, I'd prefer to keep tracking
upstream in rawhide, maybe we can get upstream to address the lack of
ABI in the disaster that is glslang.

Dave.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Proposal to Add: Log In/Out Blocker Criteria

2020-08-10 Thread Adam Williamson
On Tue, 2020-08-04 at 14:47 +0200, Kamil Paral wrote:
> On Tue, Aug 4, 2020 at 8:50 AM Geoffrey Marr  wrote:
> 
> > At today's blocker review meeting[0], we ran across a bug[1] that we
> > believe is bad enough to warrant blocker status, but as the criteria
> > currently stand, does not violate any particular criterion. The bug in
> > question has to do with logging out of one user account and logging into
> > another account that has already been accessed before during that boot. The
> > criterion listed in the bug[2] doesn't seem to fit, as it is more focused
> > on what happens after the system is booted (which does work in the case of
> > this bug). There is a Final criterion[3] that covers switching between two
> > accounts, where the data in the account switched out of is retained, but
> > that is not the case presented here (as this bug has to do with "logging
> > in/out" of accounts, not "switching" as they are defined technically).
> > Intellectually, we believe this type of bug should violate the criteria, as
> > it seems a common use-case, and so we are bringing it up as a possible
> > addition as there is nothing that currently covers this kind of bug.
> > 
> > The new criterion could look something like "A system with multiple user
> > accounts must be able to log in and out of said accounts as presented by
> > all release-blocking desktops in their default configuration."
> > 
> 
> Actually, I'd make this even simpler. We already have a Beta criterion
> related to logging out (among others):
> https://fedoraproject.org/wiki/Fedora_33_Beta_Release_Criteria#Shutdown.2C_reboot.2C_logout
> 
> So let's just include logging in as well, and we're done:
> "Shutting down, rebooting, logging in and logging out must work using
> standard console commands and the mechanisms offered (if any) by all
> release-blocking desktops."
> 
> We'd also update the "Work?" footnote:
> "Similar to the Basic criterion for shutting down, shutdown and reboot
> mechanisms must take storage volumes down cleanly and correctly request a
> shutdown or reboot from the system firmware. Logging in must transfer the
> user from the login screen/prompt to his/her working environment, and
> logging out must return the user to the environment from which they logged
> in, working as expected."
> 
> This sufficiently covers the discussed bug and seems to fit naturally into
> the existing criterion. One unclear area might be what the console console
> used for logging in is. We can either explicitly say that for logging in we
> don't require any specific console command, or we can note that the most
> likely command to get covered by this is "su". We can also not define it
> and leave that up to blocker discussion, if such a situation occurs in the
> future. I'd lean towards the last option, but all sound fine to me.

As mentioned in the IRC meeting today, I have a small nit with this:
the criterion as it exists right now is conceptually intended as a
"Stopping The Session" criterion. It covers three things which are all,
broadly, ways to stop the current session. If we stick "logging in"
into it in this way, we lose that conceptual clarity and it potentially
makes the overall...idea...of the criterion more muddy and hard to
read.

On the whole I feel like considering all requirements related to log
in, log out, shutdown, restart, and user switch together we should be
able to come up with a better option either than a standalone new
criterion (Geoff's proposal) or this add-on to the "end session"
criterion (Kamil's proposal), but I think either proposal would be
*okay* if we don't get the time to come up with something better. Just
wanted to flag that up for discussion.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Fedora 33 System-Wide Change proposal: systemd-resolved

2020-08-10 Thread Michael Catanzaro


On Tue, Aug 4, 2020 at 9:08 am, Michael Catanzaro 
 wrote:
Zbigniew, do you agree that we should remove the script if and only 
if it is generated by NetworkManager? Otherwise, the change is only 
partially-implemented for users upgrading from F32 and earlier.


We agreed to go with this approach. /etc/resolv.conf will be moved to 
/etc/resolv.conf.orig-with-nm on upgrade to F33 if the 'Generated by 
NetworkManager' comment is present. If you've gone to the trouble to 
prevent NetworkManager from managing this file, it's likely you've also 
removed the comment. If not, you can either remove the comment before 
upgrade, or recover your previous configuration from the 
/etc/resolv.conf.orig-with-nm backup file after upgrade, and hopefully 
have only a small blip in your upgrade experience. This will make the 
upgrade work properly for the 99% of users who don't mess with the 
defaults and should not be too difficult for those who do.


Michael

___
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


[Bug 1862926] Upgrade perl-Hash-Merge to 0.302

2020-08-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1862926

Tom "spot" Callaway  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |RAWHIDE
Last Closed||2020-08-10 16:43:44



--- Comment #1 from Tom "spot" Callaway  ---
0.302 in rawhide.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Box2D

2020-08-10 Thread Gwyn Ciesla via devel
I'm updating Box2D in rawhide to 2.4.0 today. I can't find any consumers, but 
I'm notifying anyway because I'm an upstanding citizen, yadda, yadda.

-- 
Gwyn Ciesla
she/her/hers
 
in your fear, seek only peace 
in your fear, seek only love
-d. bowie

Sent with ProtonMail Secure Email.

signature.asc
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


[Bug 1867692] libsane-airscan-0.99.12-1.fc33: airscan driver crashes in mock: file airscan-wsdd.c: line 1696 (wsdd_cleanup): assertion failed: (ll_empty(_finding_list))

2020-08-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1867692

Petr Pisar  changed:

   What|Removed |Added

Summary|perl-Image-Sane-5-5.fc33|libsane-airscan-0.99.12-1.f
   |FTBFS: airscan driver   |c33: airscan driver crashes
   |crashes in mock: file   |in mock: file
   |airscan-wsdd.c: line 1696   |airscan-wsdd.c: line 1696
   |(wsdd_cleanup): assertion   |(wsdd_cleanup): assertion
   |failed: |failed:
   |(ll_empty(_finding_lis |(ll_empty(_finding_lis
   |t)) |t))




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1867692] perl-Image-Sane-5-5.fc33 FTBFS: airscan driver crashes in mock: file airscan-wsdd.c: line 1696 (wsdd_cleanup): assertion failed: (ll_empty(_finding_list))

2020-08-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1867692



--- Comment #3 from Petr Pisar  ---
The Perl t/options.t test calls:

const SANE_Device **device_list;
sane_get_devices (_list, 0);

I checked sane_get_devices() in backend/dll.c that the only thing it does with
the first argument is assigning to the dereferenced pointer. Thus
perl-Sane-Image uses the interface correctly.

I can reproduce the crash with a scanimage tool of sane-backends:

# scanimage 
Output format is not set, using pnm as a default.
Segmentation fault (core dumped)

I hope this reproducer is good enough for you.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Re: LTO and the F33 mass rebuild

2020-08-10 Thread Jeff Law
On Mon, 2020-08-10 at 09:59 +0200, Miro Hrončok wrote:
> On 09. 08. 20 0:02, Jeff Law wrote:
> > For any package which was failing and LTO appeared to be a factor, I've 
> > assigned
> > the package's associated FTBFS BZ to me to address the LTO component.  Some 
> > of
> > those I've already fixed and either closed the BZ or handed it back to the
> > default assignee for non-LTO issues that need to be resolved.
> > 
> > Thus if you have a package on the failing packages list and its still 
> > failing,
> > it's unlikely to be an LTO issue.  I don't mind if you reach out, but start 
> > from
> > the assumption LTO isn't the triggering event.  You can use %define 
> > _lto_cflags
> > %{nil} in your .spec file to disable LTO for testing purposes.
> 
> Thank you Jeff so very much for doing this!
> 
> I've assigned https://bugzilla.redhat.com/show_bug.cgi?id=1865257 to you as 
> well 
> in the spirit of what you've said. The failure is workarounded with %global 
> _lto_cflags %{nil} now.
Thanks.
jeff
___
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


Metrics: Package updates each release and package review time

2020-08-10 Thread Justin W. Flory (he/him)
Hi all,

CommOps received a request to build metrics for (1) what packages are
updated every Fedora release, and (2) how long on average package
reviews take; however, we do not have capacity to take this request. Per
discussion at Nest, I am following up on Fedora Infrastructure list to
explore if there is capacity elsewhere for this work.

The ticket with this request was opened by Brian Exelbierd in March
2018. The CommOps team first approached this work two years ago, but our
volunteer team does not have capacity to meet this request:

https://pagure.io/fedora-commops/issue/144

At Nest, we briefly discussed with cverna in the CommOps metrics hack
session that this request is more likely a question of which system to
query and how (versus building new tooling or collecting new data).

I was actioned to open a discussion on the Infrastructure mailing list
to explore if this is of interest to the Fedora Packaging community. If
so, the C.P.E. team may be able to redirect this request to the right place.

I am closing the CommOps ticket once I send this mail, but I am happy to
move the request to a new Pagure issue in a different repo if someone is
interested in taking up this request.

Thanks!

-- 
Cheers,
Justin W. Flory (he/him)
https://jwf.io
TZ=America/New_York



signature.asc
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


[Bug 1867692] perl-Image-Sane-5-5.fc33 FTBFS: airscan driver crashes in mock: file airscan-wsdd.c: line 1696 (wsdd_cleanup): assertion failed: (ll_empty(_finding_list))

2020-08-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1867692

Petr Pisar  changed:

   What|Removed |Added

 CC||zdoh...@redhat.com
  Component|perl-Image-Sane |sane-airscan
   Assignee|ppi...@redhat.com   |zdoh...@redhat.com
Summary|perl-Image-Sane-5-5.fc33|perl-Image-Sane-5-5.fc33
   |FTBFS: t/options.t test |FTBFS: airscan driver
   |crashes with SIGABRT|crashes in mock: file
   ||airscan-wsdd.c: line 1696
   ||(wsdd_cleanup): assertion
   ||failed:
   ||(ll_empty(_finding_lis
   ||t))



--- Comment #2 from Petr Pisar  ---
If I comment out the driver name in /etc/sane.d/dll.d/airscan, the crash
disappear. Reassigning to sane-airscan.
I will try to come up with a Perl-free reproducer.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Re: ppc64le copr

2020-08-10 Thread Silvie Chlupova
Hi Dave,
at this point, we still don't have working ppc64le workers. Please see this
issue https://pagure.io/fedora-infrastructure/issue/9059. Unfortunately, I
can't give you better information at the moment.

Silvie Chlupova

On Mon, Aug 10, 2020 at 3:46 PM Dave Love 
wrote:

> What's the state of ppc64le in copr?  Is it coming back and, if so, is
> there a timescale for that?  Sorry I can't find the info about it from a
> while back, but I thought things were meant to be restored by August.
> It would definitely be more useful to me than s390x...
> ___
> 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
>
___
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


[Bug 1867692] perl-Image-Sane-5-5.fc33 FTBFS: t/options.t test crashes with SIGABRT

2020-08-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1867692

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED



--- Comment #1 from Petr Pisar  ---
This happens only in mock tool (and in Koji). It does not happen in a virtual
machine. The test crashes like this:

# perl -Iblib/{lib,arch} t/options.t 
ok 1 - use Image::Sane;
ok 2 - get_version
file airscan-wsdd.c: line 1696 (wsdd_cleanup): assertion failed:
(ll_empty(_finding_list))
Aborted (core dumped)

While it should continue like this:

$ perl -Iblib/{lib,arch} t/options.t
ok 1 - use Image::Sane;
ok 2 - get_version
ok 3 - get_devices
[...]

I suspect a new mock behavior regarding a network isolation (e.g. getaddrinfo()
started to return EAI_AGAIN instead of EAI_NONAME|EAI_NODATA) that manifests in
the new airscan driver.

strace output:
[...]
openat(AT_FDCWD, "/etc/sane.d/airscan.d/",
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or
directory)
[...]
socket(AF_NETLINK, SOCK_RAW|SOCK_CLOEXEC, NETLINK_ROUTE) = 137
bind(137, {sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, 12) = 0
getsockname(137, {sa_family=AF_NETLINK, nl_pid=-1837056385,
nl_groups=}, [12]) = 0
sendto(137, {{len=20, type=RTM_GETLINK, flags=NLM_F_REQUEST|NLM_F_DUMP,
seq=1597070627, pid=0}, {ifi_family=AF_UNSPEC, ...}}, 20, 0,
{sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, 12) = 20
[...]
recvmsg(137, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=},
msg_namelen=12, msg_iov=[{iov_base={{len=72, type=RTM_NEWADDR,
flags=NLM_F_MULTI, seq=1597070628, pid=2457910911}, {ifa_family=AF_INET6,
ifa_prefixlen=128, ifa_flags=IFA_F_PERMANENT, ifa_scope=RT_SCOPE_HOST,
ifa_index=if_nametoindex("lo")}, [{{nla_len=20, nla_type=IFA_ADDRESS},
inet_pton(AF_INET6, "::1")}, {{nla_len=20, nla_type=IFA_CACHEINFO},
{ifa_prefered=4294967295, ifa_valid=4294967295, cstamp=2491564,
tstamp=2491564}}, {{nla_len=8, nla_type=IFA_FLAGS}, IFA_F_PERMANENT}]},
iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 72
recvmsg(137, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=},
msg_namelen=12, msg_iov=[{iov_base={{len=20, type=NLMSG_DONE,
flags=NLM_F_MULTI, seq=1597070628, pid=2457910911}, 0}, iov_len=4096}],
msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 20
close(137)  = 0
write(134, "W", 1)  = 1
getresuid([0], [0], [0])= 0
getresgid([0], [0], [0])= 0
socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC, 0) = 137
connect(137, {sa_family=AF_UNIX, sun_path="/run/dbus/system_bus_socket"}, 29) =
-1 ENOENT (No such file or directory)
close(137)  = 0
write(134, "W", 1)  = 1
write(1, "file airscan-wsdd.c: line 1696 (wsdd_cleanup): assertion failed:
(ll_empty(_finding_list))\n", 96file airscan-wsdd.c: line 1696
(wsdd_cleanup): assertion failed: (ll_empty(_finding_list))
) = 96
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], [], 8) = 0
getpid()= 432
gettid()= 432
tgkill(432, 432, SIGABRT)   = 0


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1867692] New: perl-Image-Sane-5-5.fc33 FTBFS: t/options.t test crashes with SIGABRT

2020-08-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1867692

Bug ID: 1867692
   Summary: perl-Image-Sane-5-5.fc33 FTBFS: t/options.t test
crashes with SIGABRT
   Product: Fedora
   Version: rawhide
   URL: https://koschei.fedoraproject.org/package/perl-Image-S
ane?collection=f33
Status: NEW
 Component: perl-Image-Sane
  Assignee: ppi...@redhat.com
  Reporter: ppi...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



perl-Image-Sane-5-5.fc33 fails to build in Fedora 33, because a test crashes:

t/options.t  
All 2 subtests passed 
t/pod.t  ok
Test Summary Report
---
t/options.t  (Wstat: 134 Tests: 2 Failed: 0)
  Non-zero wait status: 134
  Parse errors: No plan found in TAP output

A difference between passing and failing build root is at
. An upgrade of sane-backends
from 1.0.30-3.fc33 to 1.0.30-4.fc33 is suspicious.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


ppc64le copr

2020-08-10 Thread Dave Love
What's the state of ppc64le in copr?  Is it coming back and, if so, is
there a timescale for that?  Sorry I can't find the info about it from a
while back, but I thought things were meant to be restored by August.
It would definitely be more useful to me than s390x...
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Fedora 33 System-Wide Change proposal: Fedora-Retired-Packages

2020-08-10 Thread Jaroslav Mracek
On Thu, Jun 25, 2020 at 9:09 PM Miroslav Suchý  wrote:

> Dne 24. 06. 20 v 4:40 Przemek Klosowski via devel napsal(a):
> > dnf -C list extras
>
> How do I skip packages which are installed from @@commandline? Is there
> anything else than "grep -v"?
>
>
I am sorry but this is not an easy task with DNF CLI and too specific.
`grep` would be the best option. Or you can set up your own script using
DNF API. I can help with that.

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


random doxygen issues in rawhide?

2020-08-10 Thread Fabio Valentini
Hi everybody,

I've seen some doxygen issues similar to this one in other packages,
but editorconfig seems to produce it quite regularly (though not
reproducibly). It happened once on ppc64le and once on x86_64 in
koschei:

error: Could not create output directory
/builddir/build/BUILD/editorconfig-core-c-0.12.3/ppc64le-redhat-linux-gnu/doc/man
Doxygen version used: 1.8.18
Exiting...
gmake[2]: *** [doc/CMakeFiles/doc.dir/build.make:88:
doc/html/index.html] Error 1
gmake[2]: *** Waiting for unfinished jobs

This seems really strange. Maybe it's a race condition?

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


Orphaned packages looking for new maintainers

2020-08-10 Thread Miro Hrončok

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.

Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://churchyard.fedorapeople.org/orphans-2020-08-10.txt
grep it for your FAS username and follow the dependency chain.

For human readable dependency chains, see https://packager.fedorainfracloud.org/
For all orphaned packages, see https://packager.fedorainfracloud.org/orphan

Package  (co)maintainers   Status Change

amftools  churchyard, orphan   3 weeks ago
anchorman orphan   5 weeks ago
beaconorphan   5 weeks ago
carto nodejs-sig, orphan   4 weeks ago
cinnamon-themes   jcpunk, orphan   5 weeks ago
closure-compiler  orphan   3 weeks ago
coreboot-utilsorphan, peter0 weeks ago
dbus-java orphan   0 weeks ago
emacs-lua orphan   3 weeks ago
ember-media   orphan   5 weeks ago
foo2zjs   orphan   5 weeks ago
fst   orphan   0 weeks ago
gabedit   itamarjp, orphan, rathann,   4 weeks ago
  scitech_sig
gallery3-openid   orphan   5 weeks ago
gdb-heap  orphan, siddhesh 5 weeks ago
gfal2-utilandreamanzi, gbitzes, orphan 3 weeks ago
gimp-normalmaporphan   4 weeks ago
gloobus-preview   orphan   5 weeks ago
gnome-mud orphan   5 weeks ago
gnusim8085orphan   4 weeks ago
golang-github-calmh-dugo-sig, orphan   4 weeks ago
golang-github-calmh-xdr   go-sig, orphan   4 weeks ago
golang-github-chmduquesne-go-sig, orphan   4 weeks ago
rollinghash
golang-github-d4l3k-messagediff   go-sig, orphan   4 weeks ago
golang-github-jackpal-gateway go-sig, orphan   4 weeks ago
golang-github-syncthing-notifygo-sig, orphan   4 weeks ago
golang-github-thejerf-suture  go-sig, orphan   4 weeks ago
golang-github-vitrun-qart go-sig, orphan   4 weeks ago
gr-iioorphan   5 weeks ago
grig  orphan   5 weeks ago
gspiceui  orphan   5 weeks ago
gtkmathview   orphan   5 weeks ago
hdfview   neuro-sig, orphan0 weeks ago
hip   orphan   3 weeks ago
inception orphan   5 weeks ago
iptux orphan   5 weeks ago
jake  nodejs-sig, orphan, piotrp   4 weeks ago
js-jquery-iframe-transportorphan   0 weeks ago
js-jquery-knoborphan   0 weeks ago
js-jquery-qrcode  orphan   0 weeks ago
js-tag-it orphan   0 weeks ago
kosmtik   nodejs-sig, orphan   4 weeks ago
libgssh   orphan   4 weeks ago
libmatthew-java   orphan   0 weeks ago
libscsorphan   3 weeks ago
liquibase awood, orphan0 weeks ago
lodashnodejs-sig, orphan   4 weeks ago
lua-copas orphan 

Re: Help needed to fix a FTBFS (shaderc)

2020-08-10 Thread Leigh Scott
> On Mon, Aug 10, 2020 at 2:57 AM Leigh Scott  wrote:
> 
> Yeah glslang sucks in terms of providing a stable API, I think
> upstream would need to address these things,
> 
> Though I hadn't realised it would FTBFS things that badly.
> 
> Dave.

Can we revert back to the old version please?, it builds fine.
Here's a working spec file  
https://leigh123linux.fedorapeople.org/pub/SPECS/glslang.spec

https://koji.fedoraproject.org/koji/taskinfo?taskID=49015264

TBH it looks like you were having a bad cmake day :-)
___
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


[Bug 1865207] perl-IO-Async: FTBFS in Fedora rawhide/f33: Failed test '->failure [3] gives EAI_NONAME or EAI_NODATA'

2020-08-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1865207

Paul Howarth  changed:

   What|Removed |Added

 CC||p...@city-fan.org



--- Comment #6 from Paul Howarth  ---
I think something must have changed in glibc in Rawhide and how it behaves when
networking is disabled. I had a very similar issue with the proftpd test suite:
https://github.com/proftpd/proftpd/pull/1075


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Orphaned packages looking for new maintainers

2020-08-10 Thread Miro Hrončok

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.

Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://churchyard.fedorapeople.org/orphans-2020-08-10.txt
grep it for your FAS username and follow the dependency chain.

For human readable dependency chains, see https://packager.fedorainfracloud.org/
For all orphaned packages, see https://packager.fedorainfracloud.org/orphan

Package  (co)maintainers   Status Change

amftools  churchyard, orphan   3 weeks ago
anchorman orphan   5 weeks ago
beaconorphan   5 weeks ago
carto nodejs-sig, orphan   4 weeks ago
cinnamon-themes   jcpunk, orphan   5 weeks ago
closure-compiler  orphan   3 weeks ago
coreboot-utilsorphan, peter0 weeks ago
dbus-java orphan   0 weeks ago
emacs-lua orphan   3 weeks ago
ember-media   orphan   5 weeks ago
foo2zjs   orphan   5 weeks ago
fst   orphan   0 weeks ago
gabedit   itamarjp, orphan, rathann,   4 weeks ago
  scitech_sig
gallery3-openid   orphan   5 weeks ago
gdb-heap  orphan, siddhesh 5 weeks ago
gfal2-utilandreamanzi, gbitzes, orphan 3 weeks ago
gimp-normalmaporphan   4 weeks ago
gloobus-preview   orphan   5 weeks ago
gnome-mud orphan   5 weeks ago
gnusim8085orphan   4 weeks ago
golang-github-calmh-dugo-sig, orphan   4 weeks ago
golang-github-calmh-xdr   go-sig, orphan   4 weeks ago
golang-github-chmduquesne-go-sig, orphan   4 weeks ago
rollinghash
golang-github-d4l3k-messagediff   go-sig, orphan   4 weeks ago
golang-github-jackpal-gateway go-sig, orphan   4 weeks ago
golang-github-syncthing-notifygo-sig, orphan   4 weeks ago
golang-github-thejerf-suture  go-sig, orphan   4 weeks ago
golang-github-vitrun-qart go-sig, orphan   4 weeks ago
gr-iioorphan   5 weeks ago
grig  orphan   5 weeks ago
gspiceui  orphan   5 weeks ago
gtkmathview   orphan   5 weeks ago
hdfview   neuro-sig, orphan0 weeks ago
hip   orphan   3 weeks ago
inception orphan   5 weeks ago
iptux orphan   5 weeks ago
jake  nodejs-sig, orphan, piotrp   4 weeks ago
js-jquery-iframe-transportorphan   0 weeks ago
js-jquery-knoborphan   0 weeks ago
js-jquery-qrcode  orphan   0 weeks ago
js-tag-it orphan   0 weeks ago
kosmtik   nodejs-sig, orphan   4 weeks ago
libgssh   orphan   4 weeks ago
libmatthew-java   orphan   0 weeks ago
libscsorphan   3 weeks ago
liquibase awood, orphan0 weeks ago
lodashnodejs-sig, orphan   4 weeks ago
lua-copas orphan 

Re: LTO and the F33 mass rebuild

2020-08-10 Thread Miro Hrončok

On 09. 08. 20 0:02, Jeff Law wrote:

For any package which was failing and LTO appeared to be a factor, I've assigned
the package's associated FTBFS BZ to me to address the LTO component.  Some of
those I've already fixed and either closed the BZ or handed it back to the
default assignee for non-LTO issues that need to be resolved.

Thus if you have a package on the failing packages list and its still failing,
it's unlikely to be an LTO issue.  I don't mind if you reach out, but start from
the assumption LTO isn't the triggering event.  You can use %define _lto_cflags
%{nil} in your .spec file to disable LTO for testing purposes.


Thank you Jeff so very much for doing this!

I've assigned https://bugzilla.redhat.com/show_bug.cgi?id=1865257 to you as well 
in the spirit of what you've said. The failure is workarounded with %global 
_lto_cflags %{nil} now.


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


[Test-Announce] Re: 2020-08-10 @ 15:00 UTC - Fedora QA Meeting

2020-08-10 Thread Geoffrey Marr
Hey Adam, all,

I think it would be a good idea to discuss the proposal to add/modify log
in/out criteria [0] at this meeting so that we can have an answer for the
bug[1] that spawned the idea come the blocker review meeting right after
this meeting.

Geoff Marr
IRC: coremodule

[0]
https://lists.fedorahosted.org/archives/list/t...@lists.fedoraproject.org/thread/PTRPHWTMVEKLTCMVDBGIWYYMYVIBAJYB/
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1861700

On Sun, Aug 9, 2020 at 7:19 PM Adam Williamson 
wrote:

> # Fedora Quality Assurance Meeting
> # Date: 2020-08-10
> # Time: 15:00 UTC
> (https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
> # Location: #fedora-meeting on irc.freenode.net
>
> Greetings testers!
>
> We didn't meet for a couple of weeks, so let's get together and check
> in on where we're at and what we have planned. I don't have much for
> the agenda this week, so it might be a short meeting.
>
> If anyone has any other items for the agenda, please reply to this
> email and suggest them! Thanks.
>
> == Proposed Agenda Topics ==
>
> 1. Previous meeting follow-up
> 2. Fedora 33 status
> 3. Test Day / community event status
> 4. Open floor
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
> http://www.happyassassin.net
> ___
> test-announce mailing list -- test-annou...@lists.fedoraproject.org
> To unsubscribe send an email to
> test-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/test-annou...@lists.fedoraproject.org
>
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-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/test-annou...@lists.fedoraproject.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