[389-devel] 389 DS nightly 2019-12-24 - 96% PASS

[vashirov]

https://fedorapeople.org/groups/389ds/ci/nightly/2019/12/24/report-389-ds-base-1.4.3.0-20191224git3022f46.fc31.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

[Fedocal] Reminder meeting : Modularity Team (weekly)

[nils]

Dear all,

You are kindly invited to the meeting:
   Modularity Team (weekly) on 2019-12-24 from 15:00:00 to 16:00:00 UTC
   At fedora-meetin...@irc.freenode.net

The meeting will be about:
Meeting of the Modularity Team.

More information available at: [Modularity Team 
Docs](https://docs.pagure.org/modularity/)

The agenda for the meeting is available as flagged tickets [in the Modularity 
repository](https://pagure.io/modularity/issues?status=Open=Meeting).



Source: https://apps.fedoraproject.org/calendar/meeting/9480/

___
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

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

[Fedora compose checker]

No missing expected images.

Compose FAILS proposed Rawhide gating check!
2 of 43 required test results missing
openQA tests matching unsatisfied gating requirements shown with **GATING** 
below

Failed openQA tests: 8/155 (x86_64), 1/2 (arm)

New failures (same test not failed in Fedora-Rawhide-20191222.n.0):

ID: 501371  Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openqa.fedoraproject.org/tests/501371
ID: 501380  Test: x86_64 Server-dvd-iso server_remote_logging_server
URL: https://openqa.fedoraproject.org/tests/501380
ID: 501386  Test: x86_64 Server-dvd-iso server_cockpit_basic
URL: https://openqa.fedoraproject.org/tests/501386
ID: 501390  Test: x86_64 Server-dvd-iso server_remote_logging_client
URL: https://openqa.fedoraproject.org/tests/501390
ID: 501417  Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/501417
ID: 501426  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/501426
ID: 501434  Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/501434
ID: 501504  Test: x86_64 universal install_iscsi
URL: https://openqa.fedoraproject.org/tests/501504
ID: 501507  Test: x86_64 universal install_rescue_encrypted
URL: https://openqa.fedoraproject.org/tests/501507

Soft failed openQA tests: 87/155 (x86_64)
(Tests completed, but using a workaround for a known bug)

New soft failures (same test not soft failed in Fedora-Rawhide-20191222.n.0):

ID: 501352  Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/501352
ID: 501353  Test: x86_64 Server-boot-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/501353
ID: 501357  Test: x86_64 Server-dvd-iso install_repository_nfs_variation
URL: https://openqa.fedoraproject.org/tests/501357
ID: 501358  Test: x86_64 Server-dvd-iso install_repository_nfs_graphical
URL: https://openqa.fedoraproject.org/tests/501358
ID: 501359  Test: x86_64 Server-dvd-iso install_repository_nfsiso_variation
URL: https://openqa.fedoraproject.org/tests/501359
ID: 501360  Test: x86_64 Server-dvd-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/501360
ID: 501361  Test: x86_64 Server-dvd-iso install_repository_hd_variation
URL: https://openqa.fedoraproject.org/tests/501361
ID: 501362  Test: x86_64 Server-dvd-iso install_vnc_server
URL: https://openqa.fedoraproject.org/tests/501362
ID: 501363  Test: x86_64 Server-dvd-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/501363
ID: 501365  Test: x86_64 Server-dvd-iso install_vnc_client
URL: https://openqa.fedoraproject.org/tests/501365
ID: 501366  Test: x86_64 Server-dvd-iso install_vncconnect_client
URL: https://openqa.fedoraproject.org/tests/501366
ID: 501377  Test: x86_64 Server-dvd-iso install_updates_nfs
URL: https://openqa.fedoraproject.org/tests/501377
ID: 501382  Test: x86_64 Server-dvd-iso server_realmd_join_kickstart
URL: https://openqa.fedoraproject.org/tests/501382
ID: 501385  Test: x86_64 Server-dvd-iso install_vncconnect_server
URL: https://openqa.fedoraproject.org/tests/501385
ID: 501391  Test: x86_64 Everything-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/501391
ID: 501392  Test: x86_64 Everything-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/501392
ID: 501400  Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/501400
ID: 501405  Test: x86_64 Workstation-live-iso desktop_printing
URL: https://openqa.fedoraproject.org/tests/501405
ID: 501418  Test: x86_64 KDE-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/501418
ID: 501423  Test: x86_64 KDE-live-iso desktop_printing
URL: https://openqa.fedoraproject.org/tests/501423
ID: 501428  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/501428
ID: 501429  Test: x86_64 universal install_ext3
URL: https://openqa.fedoraproject.org/tests/501429
ID: 501430  Test: x86_64 universal install_no_swap
URL: https://openqa.fedoraproject.org/tests/501430
ID: 501431  Test: x86_64 universal install_updates_img_local
URL: https://openqa.fedoraproject.org/tests/501431
ID: 501432  Test: x86_64 universal install_shrink_ext4
URL: https://openqa.fedoraproject.org/tests/501432
ID: 501435  Test: x86_64 universal install_kickstart_firewall_disabled
URL: https://openqa.fedoraproject.org/tests/501435
ID: 501436  Test: x86_64 universal install_anaconda_text
URL: https://openqa.fedoraproject.org/tests/501436
ID: 501437  Test: x86_64 universal install_sata@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/501437
ID: 501438  Test: x86_64 universal upgrade_2_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/501438

Fedora rawhide compose report: 20191223.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20191222.n.0
NEW: Fedora-Rawhide-20191223.n.0

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

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   76.26 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   1011.71 KiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Minimal raw-xz aarch64
Path: Spins/aarch64/images/Fedora-Minimal-Rawhide-20191223.n.0.aarch64.raw.xz

= DROPPED IMAGES =
Image: Workstation raw-xz aarch64
Path: 
Workstation/aarch64/images/Fedora-Workstation-Rawhide-20191222.n.0.aarch64.raw.xz
Image: Server raw-xz aarch64
Path: Server/aarch64/images/Fedora-Server-Rawhide-20191222.n.0.aarch64.raw.xz
Image: Container_Base docker s390x
Path: 
Container/s390x/images/Fedora-Container-Base-Rawhide-20191222.n.0.s390x.tar.xz

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  cppcheck-1.90-1.fc32
Old package:  cppcheck-1.89-2.fc32
Summary:  Tool for static C/C++ code analysis
RPMs: cppcheck cppcheck-gui cppcheck-htmlreport
Size: 16.58 MiB
Size change:  926.50 KiB
Changelog:
  * Sat Dec 21 2019 Wolfgang St??ggl  - 1.90-1
  - New upstream version 1.90


Package:  hstr-2.2-1.fc32
Old package:  hstr-1.22-9.fc31
Summary:  Suggest box like shell history completion
RPMs: hstr
Size: 221.22 KiB
Size change:  20.48 KiB
Changelog:
  * Sun Dec 22 2019 Leigh Scott  - 2.2-1
  - Update to 2.2


Package:  lollypop-1.2.16-2.fc32
Old package:  lollypop-1.2.16-1.fc32
Summary:  Music player for GNOME
RPMs: lollypop
Size: 808.70 KiB
Size change:  93 B
Changelog:
  * Sun Dec 22 2019 Martin Gansser  - 1.2.16-2
  - Add RR python3-beautifulsoup4 needed for lyrics


Package:  perl-Minion-10.02-1.fc32
Old package:  perl-Minion-10.0-1.fc32
Summary:  High performance job queue for the Perl programming language
RPMs: perl-Minion
Size: 1.09 MiB
Size change:  -152 B
Changelog:
  * Sun Dec 22 2019 Emmanuel Seyman  - 10.02-1
  - Update to 10.02


Package:  perl-Test-Warnings-0.028-1.fc32
Old package:  perl-Test-Warnings-0.027-1.fc32
Summary:  Test for warnings and the lack of them
RPMs: perl-Test-Warnings
Size: 32.76 KiB
Size change:  349 B
Changelog:
  * Sun Dec 22 2019 Paul Howarth  - 0.028-1
  - Update to 0.028
- Allow for warnings->import being called after importing the "warnings" sub


Package:  spectrwm-3.3.0-1.fc32
Old package:  spectrwm-3.2.0-3.fc31
Summary:  Minimalist tiling window manager written in C
RPMs: spectrwm
Size: 697.54 KiB
Size change:  61.61 KiB
Changelog:
  * Sun Dec 22 2019 Lokesh Mandvekar  - 3.3.0-1
  - bump to v3.3.0


Package:  systemd-244.1-2.fc32
Old package:  systemd-244.1-1.fc32
Summary:  System and Service Manager
RPMs: systemd systemd-container systemd-devel systemd-journal-remote 
systemd-libs systemd-pam systemd-rpm-macros systemd-tests systemd-udev
Size: 56.81 MiB
Size change:  2.87 KiB
Changelog:
  * Sat Dec 21 2019  - 244.1-2
  - Disable service watchdogs (for systemd units)


Package:  unoconv-0.9.0-2.fc32
Old package:  unoconv-0.9-1.fc32
Summary:  A tool to convert documents from/to any format supported by 
LibreOffice
RPMs: unoconv
Size: 56.38 KiB
Size change:  -40 B
Changelog:
  * Sun Dec 22 2019 David Tardon  - 0.9.0-2
  - upload fixed tarball



= DOWNGRADED PACKAGES =___
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: How to reuild wdune ?

[Robert-André Mauchin]

On Monday, 23 December 2019 21:29:41 CET J. Scheurich wrote:
> Hi,
> 
> I got
> 
> $ fedpkg build
> 
> for wdune running, but what i need to publish it ?
> 
> So i can install it with
> 
> # yum install wdune
> 
> ?
> 
> so long
> MUFTI

Check the results of your build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=39898232

It failed because it depends on vcglib that you haven't build yet.

___
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: How to reuild wdune ?

[J. Scheurich]

Hi,

I got

$ fedpkg build

for wdune running, but what i need to publish it ?

So i can install it with

# yum install wdune

?

so long
MUFTI
___
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: How to reuild wdune ?

[Kevin Fenzi]

On Mon, Dec 23, 2019 at 07:18:24PM -, Leigh Scott wrote:
> Why don't you listen to your sponsors advise?
> 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/WHP6UKNKFX7RY7Y22CNNGWWKBBJX3JI6/
> 
> If I was your sponsor I would consider withdrawing your packager status.
> Try reverting your first commit as it's garbage, you never upload the 
> unpacked source files!
> 
> https://src.fedoraproject.org/rpms/wdune/tree/master
> 
> rm -rf wdune
> fedpkg clone wdune
> cd wdune
> git revert -1 HEAD
> git push
> 
> then do it properly
> 
> fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm
> git commit -am "Initial import (#1658153)"

Things can be overwealming at first. I also urge you to work with your
sponsor, they can help you get things back on track. :) 

Failing that, if you need more real time help, you can drop by
#fedora-devel on irc.freenode.net (
https://fedoraproject.org/wiki/Communicating_and_getting_help#IRC_for_interactive_community_support
), there's almost always someone around there who can help out.
Ask questions and be patient. 

Welcome to packaging!

kevin


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

Re: Fedora 32 System-Wide Change proposal: Use update-alternatives for /usr/bin/cc and /usr/bin/c++

[Tom Stellard]

On 12/21/2019 02:30 PM, Tomasz Kłoczko wrote:
> 
> 
> On Sat, 21 Dec 2019 at 00:37, Neal Gompa  > wrote:
> [..]
> 
> I believe it's also used by the %cmake and %meson macros.
> 
> 
> Yep.
> Look on the output of the “rpm -E %cmake” and you will find that to switch to 
> other C and C++ compilers all what you need to do is redefine %__cc and 
> %__cxx macros,

I'm not seeing this, at least with the current rawhide build, but I
patched cmake to enable this in the latest mass rebuild that I'm doing.
I'll post numbers on how effective using __cc and __cxx are once it's
complete.

-Tom

> The same is with %configure and %meson,
> 
> In other words you can switch NOW from non-root account to other compiler 
> without execution update-alternatives from root.
> 
> In other words this proposal is pointless.
> 
> kloczek
> -- 
> -- 
> Tomasz Kłoczko | Tel: 0774 1209067 | LinkedIn: *http://lnkd.in/FXPWxH*
___
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: How to reuild wdune ?

[Leigh Scott]

> Hi,
> 
> I tried the following:
> 
> $ kinit mufti11(a)FEDORAPROJECT.ORG
> rm -rf wdune
> fedpkg clone wdune
> cd wdune
> $ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm > /dev/null
> 
> $ git commit -sm "Initial import (#1658153)"
> error: gpg failed to sign the data
> fatal: failed to write commit object
> $ fedpkg push
> Everything up-to-date
> $ fedpkg build
> Could not execute build: /home/home/mufti/wdune has uncommitted
> changes.  Use git status to see details
> Try option --srpm to make scratch build from local changes.
> $
> 
> I updated the gpg keys with
> 
> curl https://getfedora.org/static/fedora.gpg | gpg --import

Why don't you listen to your sponsors advise?

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/WHP6UKNKFX7RY7Y22CNNGWWKBBJX3JI6/

If I was your sponsor I would consider withdrawing your packager status.
Try reverting your first commit as it's garbage, you never upload the unpacked 
source files!

https://src.fedoraproject.org/rpms/wdune/tree/master

rm -rf wdune
fedpkg clone wdune
cd wdune
git revert -1 HEAD
git push

then do it properly

fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm
git commit -am "Initial import (#1658153)"
___
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: How to reuild wdune ?

[Todd Zullinger]

Fabio Valentini wrote:
> On Mon, Dec 23, 2019, 17:45 J. Scheurich  wrote:
>> $ git commit
>> error: gpg failed to sign the data
>> fatal: failed to write commit object
>>
>> Same problem 8-(
>>
> Looks like you have the option to sign your git commits turned on globally,
> probably in ~/.gitconfig or something.

The --show-origin option to git config is handy for finding
where you've set the option.  E.g.:

git config --show-origin --get commit.gpgSign

-- 
Todd


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

Re: How to reuild wdune ?

[Fabio Valentini]

On Mon, Dec 23, 2019, 17:45 J. Scheurich  wrote:

>
> I tried the following:
>>
>> $ kinit muft...@fedoraproject.org
>> rm -rf wdune
>> fedpkg clone wdune
>> cd wdune
>> $ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm > /dev/null
>>
>> $ git commit -sm "Initial import (#1658153)"
>>
>
> You do not need to sign your git commits.
>
> error: gpg failed to sign the data
>> fatal: failed to write commit object
>>
>
> So the commit probably failed because git couldn't find a GPG associated
> with your email address.
>
>
> Why would you want to sign your commits with fedora GPG keys, and not your
> own key? And those are the public keys, they wouldn't help you either way
> ...
>
> I think ,my gpg key are up to date.
>
> How to proove it ?
>
> Just skip the -s argument in "git commit".
>
> $ git commit
> error: gpg failed to sign the data
> fatal: failed to write commit object
>
> Same problem 8-(
>
Looks like you have the option to sign your git commits turned on globally,
probably in ~/.gitconfig or something.

>
> so long
>
> MUFTI
> ___
> 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

Re: How to reuild wdune ?

[J. Scheurich]

I tried the following:

$ kinit muft...@fedoraproject.org 
rm -rf wdune
fedpkg clone wdune
cd wdune
$ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm >
/dev/null

$ git commit -sm "Initial import (#1658153)"


You do not need to sign your git commits.

error: gpg failed to sign the data
fatal: failed to write commit object


So the commit probably failed because git couldn't find a GPG
associated with your email address.




Why would you want to sign your commits with fedora GPG keys, and not
your own key? And those are the public keys, they wouldn't help you
either way ...


I think ,my gpg key are up to date.

How to proove it ?


Just skip the -s argument in "git commit".


$ git commit
error: gpg failed to sign the data
fatal: failed to write commit object

Same problem 8-(


so long

MUFTI

___
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: How to reuild wdune ?

[Fabio Valentini]

On Mon, Dec 23, 2019, 16:16 J. Scheurich  wrote:

> Hi,
>
> I tried the following:
>
> $ kinit muft...@fedoraproject.org
> rm -rf wdune
> fedpkg clone wdune
> cd wdune
> $ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm > /dev/null
>
> $ git commit -sm "Initial import (#1658153)"
>

You do not need to sign your git commits.

error: gpg failed to sign the data
> fatal: failed to write commit object
>

So the commit probably failed because git couldn't find a GPG associated
with your email address.

$ fedpkg push
> Everything up-to-date
>

And then without a successful commit, there's nothing to push 

$ fedpkg build
> Could not execute build: /home/home/mufti/wdune has uncommitted

changes.  Use git status to see details
> Try option --srpm to make scratch build from local changes.
>

And you can't build stuff that you haven't pushed yet.

$
>
> I updated the gpg keys with
>
> curl https://getfedora.org/static/fedora.gpg | gpg --import
>

Why would you want to sign your commits with fedora GPG keys, and not your
own key? And those are the public keys, they wouldn't help you either way
...

Just skip the -s argument in "git commit".

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

How to reuild wdune ?

[J. Scheurich]

Hi,

I tried the following:

$ kinit muft...@fedoraproject.org
rm -rf wdune
fedpkg clone wdune
cd wdune
$ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm > /dev/null

$ git commit -sm "Initial import (#1658153)"
error: gpg failed to sign the data
fatal: failed to write commit object
$ fedpkg push
Everything up-to-date
$ fedpkg build
Could not execute build: /home/home/mufti/wdune has uncommitted
changes.  Use git status to see details
Try option --srpm to make scratch build from local changes.
$

I updated the gpg keys with

curl https://getfedora.org/static/fedora.gpg | gpg --import
___
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 32 System-Wide Change proposal: Enable fstrim.timer by default

[Rex Dieter]

Ben Cotton wrote:

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

Maybe it should be obvious, but the feature page doesn't include details on 
how to manually enable(opt-in) or disable(opt-out) of the feature.  Please 
add that.

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

[Daniel P . Berrangé]

On Mon, Dec 23, 2019 at 11:01:33AM +0100, Miro Hrončok wrote:
> 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-2019-12-23.txt
> grep it for your FAS username and follow the dependency chain.
> 

> libgovirt orphan   5 weeks ago

I don't particularly want it, but I grabbed this to prevent retirement
because it is a BR of virt-viewer. It was orphaned due to FTBFS which
was a trivial issue of a TLS cert being expired in the test suite,
solved by rebase to latest version.


Regards,
Daniel
-- 
|: https://berrange.com  -o-https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o-https://fstop138.berrange.com :|
|: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
___
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: orphaning bleachbit

[Felix Schwarz]

Am 23.12.19 um 01:23 schrieb John M. Harris Jr:
> So long as Python2 remains installable, I don't see why you feel the need to 
> rip it out of the distro.

Also imho I expect that Fedora packages will receive security fixes and
serious bugs will be fixed (of course still considering that Fedora is mostly
a volunteer-driven distro). Without upstream support this is very hard to do.
Also many upstream libraries are dropping Python 2 support now.

If someone feels (s)he knows enough about the code to keep a Python 2 version
secure it is likely easier just to do an upstream port to Python 3.
I consider Python code which does not support Python 3 as "unmaintained"
(unless there is clear evidence of a Python 3 port going on).

IMHO the current Fedora policy with regards to Python 2 is very reasonable. We
will be shipping python2 in F32 for some packages as an exception. I'm willing
to maintain some of my python2 packages in Fedora so dependent packages get
some more time to migrate but ultimately upstream decided to stop supporting
Python 2 and that affects Fedora.

Felix
___
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: Port fedora for RISC-V with out compressed instructions

[David Abdurachmanov]

On Thu, Dec 19, 2019 at 11:40 AM Sreenadh S  wrote:
>
> We want to port fedora for  RISC-V with out compressed (RV64IMAFD) 
> instructions.
>
> We are from Centre for Development of Advanced Computing (C-DAC) India.
> We have implemented an Out-of order quad core RISC-V processor on FPGA.
>
> The processor is without compressed instructions.
> We want to port fedora for  RISC-V with out compressed instructions.
>
> Please share the link if it is already ported, or give the guidelines on how 
> to port.

Hi,

There seems to be a number of people who potentially want to have
Fedora/RISCV with RV64G.
Billa Surendra  already started such
efforts, thus you most likely want to join it.

Basically the process should be easy as RV64GC and RV64G share the
same ABI. I checked glibc dynamic loader code at some point and
verified (by code review) that it allows mixing RV64GC and RV64G
shared libraries. Kernel, OpenSBI and U-Boot don't care about
compression instructions. IIRC U-Boot builds with RVC by default, but
there is a config option to disable that. So simply check and rebuild
firmware blobs with RVC disabled. Then load Fedora/RISCV existing disk
image on QEMU RV64GC virt machine or SiFive Unleashed. Find the latest
disk images here:

https://dl.fedoraproject.org/pub/alt/risc-v/disk-images/fedora/rawhide/

Then rebuild toolchain (e.g. GCC) to target RV64G instead of RV64GC.
Finally start building all installed packages until you can reassembly
disk image from them. Once you have that change QEMU or hardware to
RV64G.

david

>
> Regards,
>
> Sreenadh S.
> ___
> 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

List of long term FTBFS packages to be retired in February

[Miro Hrončok]

Dear maintainers.

Based on the latest fail to build from source policy, the following packages
will be retired from Fedora 32 approximately one week before branching (February 
2020).


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


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

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

elasticsearch hubbitus, jvanek, lbazan,Fedora 24
  zbyszek
expresso  jamielinux, nodejs-sig,  Fedora 28
  patches
libocrdma ocrdma   Fedora 27
nuvola-app-google-calendarmartinkg Fedora 29
nuvola-app-groove martinkg Fedora 28
nuvola-app-logitech-media-martinkg Fedora 29
server
nuvola-app-plex   martinkg Fedora 29
nuvola-app-soundcloud martinkg Fedora 29
nuvola-app-yandex-music   martinkg Fedora 29
shim-unsigned-aarch64 pjones   Fedora 28
shim-unsigned-x64 pjones   Fedora 28

The following packages require above mentioned packages:
Depending on: expresso (1)
nodejs-chrono (maintained by: jamielinux, nodejs-sig, tomh)
nodejs-chrono-1.0.5-10.fc31.src requires npm(expresso) = 0.9.2

Affected (co)maintainers
hubbitus: elasticsearch
jamielinux: expresso
jvanek: elasticsearch
lbazan: elasticsearch
martinkg: nuvola-app-logitech-media-server, nuvola-app-plex, nuvola-app-groove, 
nuvola-app-google-calendar, nuvola-app-soundcloud, nuvola-app-yandex-music

nodejs-sig: expresso
ocrdma: libocrdma
patches: expresso
pjones: shim-unsigned-aarch64, shim-unsigned-x64
tomh: expresso
zbyszek: elasticsearch


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

Re: Build complete, but result generic error

[Fabio Valentini]

On Mon, Dec 23, 2019, 11:27 Guido Aulisi  wrote:

> Il giorno lun 23 dic 2019 alle ore 09:24 Guido Aulisi
>  ha scritto:
> >
> > Hi,
> > Koji reports that build [0] is complete, but it is marked with this
> error:
> > GenericError: cannot update build 1424540, state: COMPLETE
> >
> > It's not selectable in Bodhi.
> > Do I have to run it again?
> >
> > Thanks
> > Ciao
> > Guido
> >
> > [0]: https://koji.fedoraproject.org/koji/buildinfo?buildID=1424540
>
> I manually tagged this build with tag f31-updates-candidate, and now I
> can see this update in bodhi.
> Is this sufficient, do I have to add other tags (f31-signing-pending)?
>

-updates-candidate should be enough IIRC.

I think this is related to the issue where rawhide updates aren't getting
pushed through bodhi since yesterday. And according to the infra ticket,
it's probably a message bus problem.

https://pagure.io/fedora-infrastructure/issue/8477#comment-617932

Fabio


> Guido
> fas: tartina
> ___
> 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

Re: Build complete, but result generic error

[Guido Aulisi]

Il giorno lun 23 dic 2019 alle ore 09:24 Guido Aulisi
 ha scritto:
>
> Hi,
> Koji reports that build [0] is complete, but it is marked with this error:
> GenericError: cannot update build 1424540, state: COMPLETE
>
> It's not selectable in Bodhi.
> Do I have to run it again?
>
> Thanks
> Ciao
> Guido
>
> [0]: https://koji.fedoraproject.org/koji/buildinfo?buildID=1424540

I manually tagged this build with tag f31-updates-candidate, and now I
can see this update in bodhi.
Is this sufficient, do I have to add other tags (f31-signing-pending)?

Guido
fas: tartina
___
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

[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-2019-12-23.txt
grep it for your FAS username and follow the dependency chain.

Package  (co)maintainers   Status Change

ExchangeIRorphan   5 weeks ago
MochiKit  orphan   1 weeks ago
apache-logging-parent mizdebsk, orphan 5 weeks ago
apachetop orphan, robert   1 weeks ago
apt-cacher-ng orphan   5 weeks ago
archaius  orphan   5 weeks ago
archmage  lbazan, orphan   4 weeks ago
audit-viewer  mitr, orphan 4 weeks ago
avalon-logkit jerboaa, mizdebsk, orphan4 weeks ago
binclock  lbalhar, orphan  1 weeks ago
buildnumber-maven-plugin  orphan   4 weeks ago
camotics  orphan   5 weeks ago
cduce orphan   5 weeks ago
clapham   orphan   5 weeks ago
csstidy   orphan   5 weeks ago
delve go-sig, orphan   5 weeks ago
dzen2 bstinson, dcantrel, fale,3 weeks ago
  lupinix, orphan
eclipse-anyedit   eclipse-sig, orphan, swagiaal5 weeks ago
eclipse-checkstyleakurtakov, eclipse-sig, orphan   5 weeks ago
eclipse-color-theme   eclipse-sig, orphan  5 weeks ago
eclipse-dltk  akurtakov, eclipse-sig,  5 weeks ago
  kdaniel, orphan, rgrunber
eclipse-epic  eclipse-sig, orphan  5 weeks ago
eclipse-m2e-antlr eclipse-sig, mizdebsk, orphan5 weeks ago
eclipse-m2e-cxf   eclipse-sig, mizdebsk, orphan5 weeks ago
eclipse-m2e-maven-dependency- mizdebsk, orphan 5 weeks ago
plugin
eclipse-m2e-modello   eclipse-sig, mizdebsk, orphan5 weeks ago
eclipse-m2e-plexuseclipse-sig, mizdebsk, orphan5 weeks ago
eclipse-m2e-sisu  eclipse-sig, mizdebsk, orphan5 weeks ago
eclipse-m2e-takarimizdebsk, orphan 5 weeks ago
eclipse-nls   orphan   5 weeks ago
eclipse-pdt   eclipse-sig, orphan  5 weeks ago
eclipse-quickrex  eclipse-sig, orphan  5 weeks ago
eclipse-sgx   orphan   5 weeks ago
exercism  go-sig, orphan   0 weeks ago
fabricorphan   5 weeks ago
ferm  orphan, slankes  5 weeks ago
giis  orphan   5 weeks ago
gipfelorphan   5 weeks ago
glob2 cheese, orphan   5 weeks ago
glusterd2 kkeithle, orphan 5 weeks ago
gns3-gui  orphan   5 weeks ago
gns3-net-converterorphan   5 weeks ago
gns3-server   orphan   5 weeks ago
golang-github-10gen-openssl   go-sig, jchaloup, mskalick,  5 weeks ago
  orphan
golang-github-codahale-   go-sig, orphan   0 weeks ago
aesnicheck
graphite-web  jamielinux, orphan, piotrp   5 weeks ago
guestfs-browser   orphan   5 weeks ago
hystrix   orphan   4 weeks ago
i3-ipc   

Re: orphaning bleachbit

[Miro Hrončok]

On 23. 12. 19 1:23, John M. Harris Jr wrote:

On Sunday, December 22, 2019 4:56:52 AM MST Miro Hrončok wrote:

On 22. 12. 19 12:01, John M. Harris Jr wrote:


On Sunday, December 22, 2019 3:11:51 AM MST Zbigniew Jędrzejewski-Szmek
wrote:



1 was rejected because there was no hope for a python3 port because of
lack of development.



This is exactly the scenario that makes no sense to deny. If the package
is still maintained, regardless of lack of changes to the software, why
simply throw out working software?



Because the maintainers of its dependencies won't maintain them just for a
decade old dead software. Please, stop spreading this FUD about FESCo
outright denying requests for Python 2 exceptions. In a half year old
thread about a package that was retired 4 months ago because it wasn't
installable - with coordination from the maintainer.


So long as Python2 remains installable, I don't see why you feel the need to
rip it out of the distro.


Because the maintainers of the Python 2 packages don't want to maintain them 
past Python 2 EOL. That includes me.


This is not the first time I'm answering this question to you. You seem to ask 
it again and again. May I suggest you write the answer down and look it up next 
time you have the tendency to ask again? That should prevent us to do this over 
and over again.


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

Build complete, but result generic error

[Guido Aulisi]

Hi,
Koji reports that build [0] is complete, but it is marked with this error:
GenericError: cannot update build 1424540, state: COMPLETE

It's not selectable in Bodhi.
Do I have to run it again?

Thanks
Ciao
Guido

[0]: https://koji.fedoraproject.org/koji/buildinfo?buildID=1424540
___
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