Re: Expect nag email if you are maintaining a package in fedora with important/critical flaw open against it

[Huzaifa Sidhpurwala]

On 2/21/19 12:55 PM, J. Scheurich wrote:
> 
>> Really nothing else to say here, apart from $SUBJECT.
>>
>> Expect nag email if you are maintaining a package in fedora with
>> important/critical flaw open against it
> | ... Red Hat Product Security Team
> 
> Is this security related or can i nag about  the  FE-NEEDSPONSOR flag in
> wdune ?
> 
This is related to https://pagure.io/fesco/issue/2090#comment-554987

-- 
Huzaifa Sidhpurwala / Red Hat Product Security Team
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Expect nag email if you are maintaining a package in fedora with important/critical flaw open against it

[J. Scheurich]

Really nothing else to say here, apart from $SUBJECT.

Expect nag email if you are maintaining a package in fedora with 
important/critical flaw open against it

| ... Red Hat Product Security Team

Is this security related or can i nag about  the  FE-NEEDSPONSOR flag in
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Expect nag email if you are maintaining a package in fedora with important/critical flaw open against it

[Huzaifa Sidhpurwala]

Hello,

Really nothing else to say here, apart from $SUBJECT.

Thanks! 
-- 
Huzaifa Sidhpurwala / Red Hat Product Security Team
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Schedule for Thursday's FPC Meeting (2019-02-21 17:00 UTC)

[James Antill]

 Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2019-02-21 17:00 UTC in #fedora-meeting-1 on 
irc.freenode.net.

 Local time information (via. uitime):

= Day: Thursday ==
2019-02-21 09:00 PST  US/Pacific
2019-02-21 12:00 EST  --> US/Eastern <--
2019-02-21 17:00 GMT  Europe/London 
2019-02-21 17:00 UTC  UTC   
2019-02-21 18:00 CET  Europe/Berlin 
2019-02-21 18:00 CET  Europe/Paris  
2019-02-21 22:30 IST  Asia/Calcutta 
 New Day: Friday -
2019-02-22 01:00 HKT  Asia/Hong_Kong
2019-02-22 01:00 +08  Asia/Singapore
2019-02-22 02:00 JST  Asia/Tokyo
2019-02-22 03:00 AEST Australia/Brisbane


 Links to all tickets below can be found at: 

https://pagure.io/packaging-committee/issues?status=Open=meeting

= Followups =

#topic #719 Simplify packaging of forge-hosted projects  
.fpc 719
https://pagure.io/packaging-committee/issue/719

#topic #845 Wiki deprecation status  
.fpc 845
https://pagure.io/packaging-committee/issue/845

= Open Floor = 

 For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at:

https://pagure.io/packaging-committee/issues?status=Open=meeting

 If you would like to add something to this agenda, you can:
  * Reply to this e-mail
  * File a new ticket at: https://pagure.io/packaging-committee
  * E-mail me directly
  * Bring it up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1678447] perl-Time-HiRes-1.9760 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
perl-Time-HiRes-1.9760-1.fc29 has been pushed to the Fedora 29 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2019-0d373389e7

-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1679360] New: perl-Devel-PPPort-3.44 is available

[bugzilla]

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

Bug ID: 1679360
   Summary: perl-Devel-PPPort-3.44 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.44
Current version/release in rawhide: 3.43-2.fc30
URL: http://search.cpan.org/dist/Devel-PPPort/

Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Introducing packit

[Tomas Tomecek]

Hello,

at DevConf.cz, we have introduced a new project: packit [1] [2].

I started a Fesco ticket [3] recently to get it approved but the
consensus was to start a devel@ thread instead and discuss it here.
So... Here we go!

TL;DR What's packit?
* Packaging automation: get latest bits into Fedora rawhide with the
minimum amount of manual steps.
* Upstream integration: let upstream know how their project stands in Fedora.
* Source-git [4]

That's a very brief intro. I spent some time on updating our readme
[2] and creating this fedora wiki page about packit [5].

Please read those documents and give us feedback: either in this
thread or feel free to create new github issues.

[1] https://www.youtube.com/watch?v=KpF27v6K4Oc
[2] https://github.com/packit-service/packit
[3] https://pagure.io/fesco/issue/2084
[4] https://github.com/packit-service/packit#ehm-whats-source-git
[5] https://fedoraproject.org/wiki/Packit

Thank you,

Tomas & the packit team
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: how about retire package that are FTBFS more than 3 releases ?

[Zbigniew Jędrzejewski-Szmek]

On Wed, Feb 20, 2019 at 08:24:30PM +, Sérgio Basto wrote:
> Hi,
> 
> how about retire package that are FTBFS more than 3 releases ?  
> 
> kde-plasma-activitymanager: FTBFS since F23 and should be retired [1] 
> 
> [1]
> https://apps.fedoraproject.org/packages/kde-plasma-activitymanager/bugs
> 
> Since we are retire orphan packages for more than x time , why not also
> take care of packages that are FTBFS for more than y releases ? 

That's the plan. But so far notifications not been sent out (apart
from the bugzilla mails), and we decided to only retire packages after
direct messages to maintainers. See https://pagure.io/fesco/issue/1973.

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

how about retire package that are FTBFS more than 3 releases ?

[Sérgio Basto]

Hi,

how about retire package that are FTBFS more than 3 releases ?  

kde-plasma-activitymanager: FTBFS since F23 and should be retired [1] 

[1]
https://apps.fedoraproject.org/packages/kde-plasma-activitymanager/bugs

Since we are retire orphan packages for more than x time , why not also
take care of packages that are FTBFS for more than y releases ? 

Best regards, 
-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Ditch RPM in favor of DPKG

[Sérgio Basto]

On Wed, 2019-02-20 at 20:18 +, Sérgio Basto wrote:
> On Wed, 2019-02-20 at 16:33 +0100, Dridi Boukelmoune wrote:
> > On Wed, Feb 20, 2019 at 4:30 PM Panu Matilainen <
> > pmati...@redhat.com>
> > wrote:
> > > 
> > > On 2/20/19 5:19 PM, Sérgio Basto wrote:
> > > > On Wed, 2019-02-20 at 11:46 +0100, Dridi Boukelmoune wrote:
> > > > > No, that was a bad joke from my end, what I need is proper
> > > > > apt
> > > > > in
> > > > > Fedora to use sbuild.
> > > > 
> > > > If you also do the review-request for apt [1] it would be great
> > > > dh-python also welcomed :) [2]
> > > > The problem is apt is in use by apt-rpm and was not retired yet
> > > > ,
> > > > we
> > > > need use another name , my propose is apt-debian .
> > > 
> > > Just FWIW, the fact that apt-rpm is still in Fedora is against
> > > the
> > > direct recommendation of the last upstream maintainer (as in,
> > > me).
> > > 
> > > It's been dead for ten years and is totally useless in todays
> > > Fedora
> > > with rich dependencies and all. Short of somebody stepping up to
> > > revive
> > > the upstream project, the only responsible action would be
> > > retiring
> > > it.
> > 
> > Oh, if upstream says so, I will look up the procedure to ask for a
> > package to be retired. That's a first for me...
> 
> That is not easy , the current procedure is ask for orphan it , if
> maintainer doesn't reply , we need open a un reponsive process for
> the
> maintainer , wait a lot of time , orphan the package , take the
> package
> and retire it . 

https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

> -- 
> Sérgio M. B.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: 
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Are the s390x builders healthy?

[Kevin Fenzi]

On 2/20/19 12:08 PM, Kaleb Keithley wrote:
> I'm trying to build Ceph again for f31 after the branching.
> 
> It built before the branching, eight days ago.
> 
> The x86_64[1] part of number two below got further than either of the two
> examples below before I killed it. I'm guessing it would have finished
> successfully if I had let it. I have another running now to confirm.
> 
> But I'm getting strange errors on s390x.
> 
> One, e.g. (
> https://kojipkgs.fedoraproject.org//work/tasks/6799/32926799/build.log)
> 
> BUILDSTDERR: {standard input}: Assembler messages:
> BUILDSTDERR: {standard input}:464309: Warning: end of file not at end
> of a line; newline inserted
> BUILDSTDERR: {standard input}:465519: Error: invalid operands (*UND*
> and .gcc_except_table sections) for `-'
> BUILDSTDERR: c++: fatal error: Killed signal terminated program cc1plus
> BUILDSTDERR: compilation terminated.
> 
> An earlier one 
> (https://kojipkgs.fedoraproject.org//work/tasks/3857/32923857/build.log)
> 
> BUILDSTDERR: {standard input}: Error: .size expression for
> _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16StringConstraintESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE7_M_copyINSF_20_Reuse_or_alloc_nodeEEEPSt13_Rb_tree_nodeIS9_EPKSJ_PSt18_Rb_tree_node_baseRT_
> does not evaluate to a constant
> BUILDSTDERR: c++: fatal error: Killed signal terminated program cc1plus
> BUILDSTDERR: compilation terminated.
> 
> Bad disk? Out of disk space? Any thoughts?

Nope and nope. ;)

I did fix 2 (related) issues this morning however:

The f31 tag didn't specify that mock was supposed to use the old chroot,
not the new systemd-nspawn one. Related to that, some of the s390x
builders had thousands of old machines in machinectl list. I cleared all
those out.

So, please try another build now and if it still fails, we can look
again. Hopefully it's fixed by the above.

kevin




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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Are the s390x builders healthy?

[Dan Horák]

On Wed, 20 Feb 2019 15:08:24 -0500
Kaleb Keithley  wrote:

> I'm trying to build Ceph again for f31 after the branching.
> 
> It built before the branching, eight days ago.
> 
> The x86_64[1] part of number two below got further than either of the
> two examples below before I killed it. I'm guessing it would have
> finished successfully if I had let it. I have another running now to
> confirm.
> 
> But I'm getting strange errors on s390x.
> 
> One, e.g. (
> https://kojipkgs.fedoraproject.org//work/tasks/6799/32926799/build.log)
> 
> BUILDSTDERR: {standard input}: Assembler messages:
> BUILDSTDERR: {standard input}:464309: Warning: end of file not at end
> of a line; newline inserted
> BUILDSTDERR: {standard input}:465519: Error: invalid operands (*UND*
> and .gcc_except_table sections) for `-'
> BUILDSTDERR: c++: fatal error: Killed signal terminated program
> cc1plus BUILDSTDERR: compilation terminated.
> 
> An earlier one
> (https://kojipkgs.fedoraproject.org//work/tasks/3857/32923857/build.log)
> 
> BUILDSTDERR: {standard input}: Error: .size expression for
> _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16StringConstraintESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE7_M_copyINSF_20_Reuse_or_alloc_nodeEEEPSt13_Rb_tree_nodeIS9_EPKSJ_PSt18_Rb_tree_node_baseRT_
> does not evaluate to a constant
> BUILDSTDERR: c++: fatal error: Killed signal terminated program
> cc1plus BUILDSTDERR: compilation terminated.
> 
> Bad disk? Out of disk space? Any thoughts?

this usually means out of memory when compiling big C++ projects, c++
is killed by the kernel. So either you need to make the build
less-parallel, you can reduce the size of the debuginfo (the s/-g/-g1/
trick) or there need to be more memory added to the builders.

Please post the link to the build task, not to the logs, next time.


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

Re: Ditch RPM in favor of DPKG

[Sérgio Basto]

On Wed, 2019-02-20 at 16:33 +0100, Dridi Boukelmoune wrote:
> On Wed, Feb 20, 2019 at 4:30 PM Panu Matilainen 
> wrote:
> > 
> > On 2/20/19 5:19 PM, Sérgio Basto wrote:
> > > On Wed, 2019-02-20 at 11:46 +0100, Dridi Boukelmoune wrote:
> > > > No, that was a bad joke from my end, what I need is proper apt
> > > > in
> > > > Fedora to use sbuild.
> > > 
> > > If you also do the review-request for apt [1] it would be great
> > > dh-python also welcomed :) [2]
> > > The problem is apt is in use by apt-rpm and was not retired yet ,
> > > we
> > > need use another name , my propose is apt-debian .
> > 
> > Just FWIW, the fact that apt-rpm is still in Fedora is against the
> > direct recommendation of the last upstream maintainer (as in, me).
> > 
> > It's been dead for ten years and is totally useless in todays
> > Fedora
> > with rich dependencies and all. Short of somebody stepping up to
> > revive
> > the upstream project, the only responsible action would be retiring
> > it.
> 
> Oh, if upstream says so, I will look up the procedure to ask for a
> package to be retired. That's a first for me...

That is not easy , the current procedure is ask for orphan it , if
maintainer doesn't reply , we need open a un reponsive process for the
maintainer , wait a lot of time , orphan the package , take the package
and retire it . 

-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Ditch RPM in favor of DPKG

[Sérgio Basto]

On Wed, 2019-02-20 at 16:31 +0100, Dridi Boukelmoune wrote:
> On Wed, Feb 20, 2019 at 4:20 PM Sérgio Basto 
> wrote:
> > 
> > On Wed, 2019-02-20 at 11:46 +0100, Dridi Boukelmoune wrote:
> > > No, that was a bad joke from my end, what I need is proper apt in
> > > Fedora to use sbuild.
> > 
> > If you also do the review-request for apt [1] it would be great
> > dh-python also welcomed :) [2]
> 
> I don't do the reviews, I submitted the packages :)

Yes you did the the review requests [1] if you have time and will you
may do the same for  apt-debian and dh-python , please . 


[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1678623 
https://bugzilla.redhat.com/show_bug.cgi?id=1678619


-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Are the s390x builders healthy?

[Kaleb Keithley]

I'm trying to build Ceph again for f31 after the branching.

It built before the branching, eight days ago.

The x86_64[1] part of number two below got further than either of the two
examples below before I killed it. I'm guessing it would have finished
successfully if I had let it. I have another running now to confirm.

But I'm getting strange errors on s390x.

One, e.g. (
https://kojipkgs.fedoraproject.org//work/tasks/6799/32926799/build.log)

BUILDSTDERR: {standard input}: Assembler messages:
BUILDSTDERR: {standard input}:464309: Warning: end of file not at end
of a line; newline inserted
BUILDSTDERR: {standard input}:465519: Error: invalid operands (*UND*
and .gcc_except_table sections) for `-'
BUILDSTDERR: c++: fatal error: Killed signal terminated program cc1plus
BUILDSTDERR: compilation terminated.

An earlier one 
(https://kojipkgs.fedoraproject.org//work/tasks/3857/32923857/build.log)

BUILDSTDERR: {standard input}: Error: .size expression for
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16StringConstraintESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE7_M_copyINSF_20_Reuse_or_alloc_nodeEEEPSt13_Rb_tree_nodeIS9_EPKSJ_PSt18_Rb_tree_node_baseRT_
does not evaluate to a constant
BUILDSTDERR: c++: fatal error: Killed signal terminated program cc1plus
BUILDSTDERR: compilation terminated.

Bad disk? Out of disk space? Any thoughts?

thanks,


[1]https://kojipkgs.fedoraproject.org//work/tasks/3856/32923856/build.log

--


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

Re: Dead packages are still in rawhide tree

[Adam Williamson]

On Wed, 2019-02-20 at 20:17 +0100, Tomasz Kłoczko wrote:
> SO for example few days ago mongodb has been officially removed from Fedora
> and in git repo is only dead.package file:
> https://src.fedoraproject.org/rpms/mongodb/tree/master
> 
> However binary and source packages are still in public repository:
> https://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/SRPMS/Packages/m/
> 
> The same situation is with few hundreds of other packages.

There has not been a successful Rawhide compose since 20190217.n.0, and
the mirrors contain the content from the most recent successful
compose. Any changes made since the 20190217.n.0 compose started will
not be reflected in the mirror content yet.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: libravatar is in fedorainfracloud!

[John Harris]

On Wednesday, February 20, 2019 5:49:13 AM EST Stephen John Smoogen wrote:
> On Wed, 20 Feb 2019 at 00:07, John Harris  wrote:
> 
> >
> >
> > On Tuesday, February 19, 2019 11:46:16 PM EST Michal Novotny wrote:
> > 
> > > Hello!
> > >
> > >
> > >
> > > maybe you know that around April 2018, there was an announcement that
> > > libravatar service (a service for serving user avatars) is shutting
> 
> 
> 
> > Awesome! I'm glad we won't be losing libravatar, and I couldn't be
> > happier
> > that it's supported by Fedora's Infra.
> >
> >
> 
> 
> I would like to clarify this as quickly as possible. Fedora
> Infrastructure's support is only to give out hardware resources to the
> this project. We do not have any fixing abilities other than rebooting
> the server if it gets stuck. People having problems like libravatars'
> avatars or login problems etc will need to contact the libravatar
> organization versus #fedora-admin or the Fedora Infrastructure ticket
> system.
> 
> 
> -- 
> Stephen J Smoogen.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Haha, I could definitely see some confusion coming from that. Sorry for my 
wording.

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

signature.asc
Description: This is a digitally signed message part.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Dead packages are still in rawhide tree

[Tomasz Kłoczko]

SO for example few days ago mongodb has been officially removed from Fedora
and in git repo is only dead.package file:
https://src.fedoraproject.org/rpms/mongodb/tree/master

However binary and source packages are still in public repository:
https://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/SRPMS/Packages/m/

The same situation is with few hundreds of other packages.

kloczek
-- 
Tomasz Kłoczko | 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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora 30 Mass Branching

[Todd Zullinger]

Hi,

Mohan Boddu wrote:
> Fedora 30 has now been branched,

Thanks, to you and the releng team. :)

> please be sure to do a git pull --rebase to pick up the
> new branch

A simple 'git fetch' should suffice to pick up the f30
branch.  Depending on the state of one's repository, the
'git pull --rebase' could cause an unexpected conflict to
resolve (though that will be waiting for them whenever they
do eventually pull).

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

Re: PSA: Bodhi cannot associate bugs with updates right now

[Randy Barlow]

On Wed, 2019-02-20 at 10:19 +0100, Milan Crha wrote:
> I've been affected of this, even I didn't know what happened, because
> the web UI didn't show any error message or a clue what was wrong.
> The
> 'Submit' button just spin for few seconds and then nothing happened,
> which had been quite frustrating.
> 
> Could the web UI be changed to claim all errors when it encounters
> any,
> instead of being just quiet and broken with no reason given?

Hi Milan, I agree. I've filed two issues to track this. The first is
for the web form and the second is for the API/CLI:

https://github.com/fedora-infra/bodhi/issues/3035
https://github.com/fedora-infra/bodhi/issues/3036


signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

pypy

[Antonette Caldwell]

Hi all

I also included this on the python-devel page.

I commented on https://bugzilla.redhat.com/show_bug.cgi?id=1673127 that I will 
be working
on building pypy. So far, I was able to build pypy and pypy3 on rawhide, but 
this is my
first time creating the package. I copied the spec from both of the rpms/pypy 
packages[1],
but I wanted to know if I will have to create new spec, since I can see there 
are changes
between the 6.0.0 and 7.0.0 versions.

Here's what I have done so far from building pypy on rawhide

pypy
A build of pypy (with jit) on x86_64
[Timer] Timings:
[Timer] annotate --- 990.8 s
[Timer] rtype_lltype --- 1797.3 s
[Timer] pyjitpl_lltype --- 2112.1 s
[Timer] backendopt_lltype --- 400.0 s
[Timer] stackcheckinsertion_lltype --- 995.6 s
[Timer] database_c --- 907.0 s
[Timer] source_c --- 413.2 s
[Timer] compile_c --- 1274.7 s
[Timer] build_cffi_imports --- 16.7 s
[Timer] ===
[Timer] Total: --- 8907.5 s

A build of pypy without jit on x86_64
[Timer] Timings:
[Timer] annotate --- 1233.1 s
[Timer] rtype_lltype --- 1554.2 s
[Timer] backendopt_lltype --- 407.9 s
[Timer] stackcheckinsertion_lltype --- 147.9 s
[Timer] database_c --- 698.6 s
[Timer] source_c --- 304.9 s
[Timer] compile_c --- 700.5 s
[Timer] build_cffi_imports --- 10.2 s
[Timer] ===
[Timer] Total:

pypy3
A build of pypy with jit on x86_64

[translation:info] usession directory: /tmp/usession-py3.5-0
[Timer] Timings:
[Timer] annotate --- 260.5 s
[Timer] rtype_lltype --- 342.1 s
[Timer] pyjitpl_lltype --- 560.0 s
[Timer] backendopt_lltype --- 106.2 s
[Timer] stackcheckinsertion_lltype --- 53.4 s
[Timer] database_c --- 232.3 s
[Timer] source_c --- 101.7 s
[Timer] compile_c --- 547.3 s
[Timer] build_cffi_imports --- 17.9 s
[Timer] ===
[Timer] Total: --- 2221.5 s

[1] https://src.fedoraproject.org/rpms/pypy/blob/master/f/pypy.spec

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

Re: F30 System-Wide Change proposal: Move Gold Into A SubpackageOf Binutils

[Petr Pisar]

On 2019-02-19, Ben Cotton  wrote:
> https://fedoraproject.org/wiki/Changes/BINUTILS_GOLD
>
>== Summary ==
> Move the GOLD linker from the main binutils package into its own sub-package.
>
>== Owner ==
[...]
>== Detailed Description ==
[...]
>== Benefit to Fedora ==
[...]
>== Scope ==
[...]
>== Upgrade/compatibility impact ==
[...]
>== How To Test ==
> No special hardware is needed, but a environment capable of building
> packages is desirable.
> First install the binutils package (if not already installed) and make
> sure that both ld.bfd and ld.gold are in the search path.
> Then try uninstalling the binutils-gold sub-package.  This should
> remove ld.gold.  Try reinstalling it, which should restore ld.gold.
>
>== User Experience ==
[...]
>== Dependencies ==
[...]
>== Contingency Plan ==
[...]
>== Documentation ==
[...]

Please advertize the new sub-package name, binutils-gold, in a more
prominent place, e.g. in the Summary.

IMHO the most important part of Change's message is a package name where
the ld.gold executable will be moved to. The overlong Change page
mentions it only once and that's in the middle of the How To Test
section.

Thank you.

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

Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

[Petr Pisar]

On 2019-02-19, Petr Pisar  wrote:
> I have a few packages that use "virtual provides" provided by multiple
> subpackages to allow users to select an implementation that best fits
> his needs. See perl-Archive-Extract for an example.
>
> How would you cope with this use case?
>
If the virtual provides exist in one source package only, one can detect
this case simply by the fact that they are provided by more than one
binary package. I think the new RPM feature should ignore these
non-uniq Provides.

Another case is when the virtual provides exist in more independent
source packages. Since rpmbuild see only the currently being built
package, it would break the dependency. Is it possible to introduce
a regualar expression based inhibitor like %__exclude_requires to
control what dependency symbols this new feature should ignore?

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

Re: Ditch RPM in favor of DPKG

[Dridi Boukelmoune]

On Wed, Feb 20, 2019 at 4:30 PM Panu Matilainen  wrote:
>
> On 2/20/19 5:19 PM, Sérgio Basto wrote:
> > On Wed, 2019-02-20 at 11:46 +0100, Dridi Boukelmoune wrote:
> >> No, that was a bad joke from my end, what I need is proper apt in
> >> Fedora to use sbuild.
> >
> > If you also do the review-request for apt [1] it would be great
> > dh-python also welcomed :) [2]
> > The problem is apt is in use by apt-rpm and was not retired yet , we
> > need use another name , my propose is apt-debian .
>
> Just FWIW, the fact that apt-rpm is still in Fedora is against the
> direct recommendation of the last upstream maintainer (as in, me).
>
> It's been dead for ten years and is totally useless in todays Fedora
> with rich dependencies and all. Short of somebody stepping up to revive
> the upstream project, the only responsible action would be retiring it.

Oh, if upstream says so, I will look up the procedure to ask for a
package to be retired. That's a first for me...

Thanks,
Dridi
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Ditch RPM in favor of DPKG

[Dridi Boukelmoune]

On Wed, Feb 20, 2019 at 4:20 PM Sérgio Basto  wrote:
>
> On Wed, 2019-02-20 at 11:46 +0100, Dridi Boukelmoune wrote:
> > No, that was a bad joke from my end, what I need is proper apt in
> > Fedora to use sbuild.
>
> If you also do the review-request for apt [1] it would be great
> dh-python also welcomed :) [2]

I don't do the reviews, I submitted the packages :)

But if you submit it, I will gladly do the review.

> The problem is apt is in use by apt-rpm and was not retired yet , we
> need use another name , my propose is apt-debian .

None of the 3 maintainers of apt-rpm have replied to this thread yet.

What they can do if they insist in keeping apt-rpm in Fedora is to
rename the source package:

https://fedoraproject.org/wiki/Package_Renaming_Process#Re-review_required

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

Re: Ditch RPM in favor of DPKG

[Panu Matilainen]

On 2/20/19 5:19 PM, Sérgio Basto wrote:

On Wed, 2019-02-20 at 11:46 +0100, Dridi Boukelmoune wrote:

No, that was a bad joke from my end, what I need is proper apt in
Fedora to use sbuild.


If you also do the review-request for apt [1] it would be great
dh-python also welcomed :) [2]
The problem is apt is in use by apt-rpm and was not retired yet , we
need use another name , my propose is apt-debian .


Just FWIW, the fact that apt-rpm is still in Fedora is against the 
direct recommendation of the last upstream maintainer (as in, me).


It's been dead for ten years and is totally useless in todays Fedora 
with rich dependencies and all. Short of somebody stepping up to revive 
the upstream project, the only responsible action would be retiring it.


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

Re: Fedora Atomic Host Two Week Release Announcement: 29.20190219.0

[Robert Fairley]

In this release, two major bugfixes are included:

1. runc container escape to host filesystem (CVE-2019-5736) [1], fixed with
runc RPM version  1.0.0-68.dev.git6635b4f.fc29
2. rpm-ostree labeling of /home symlink to /var/home [2], fixed with
rpm-ostree RPM version 2019.2-1.fc29

To reiterate, Atomic Host systems are protected from the runc exploit due
to two lines of defense: SELinux, and /usr being mounted as read-only (see
[3]). Thus, existing Atomic Host systems should not be affected.

The kernel update to 4.20.3-200.fc29, which introduced bugs that blocked
the 20190204 release [4], is now being tracked at [5] and [6]. Since we
have confirmed the ppc64le image boots with nested kvm/qemu virtualization
on Power9 hardware, we have decided to release.

An example of the diff between this and the previous released version
(for x86_64) is:
ostree diff commit old:
cdcbea2ccac7804770be806befd30895457de080d1525ee6050a5bebdfeefeb7
ostree diff commit new:
d00adf110907f93f6cdd05deda0e2878c9bd71c74e0c4c2e9a5250d2f4cc8868
Upgraded:
  checkpolicy 2.8-2.fc29 -> 2.8-3.fc29
  cockpit-bridge 185-1.fc29 -> 187-1.fc29
  cockpit-docker 185-1.fc29 -> 187-1.fc29
  cockpit-networkmanager 185-1.fc29 -> 187-1.fc29
  cockpit-system 185-1.fc29 -> 187-1.fc29
  container-selinux 2:2.77-1.git2c57a17.fc29 -> 2:2.81-2.git484806a.fc29
  crypto-policies 20181026-1.gitd42aaa6.fc29 -> 20190211-2.gite3eacfc.fc29
  curl 7.61.1-6.fc29 -> 7.61.1-9.fc29
  dbus 1:1.12.10-1.fc29 -> 1:1.12.12-1.fc29
  dbus-common 1:1.12.10-1.fc29 -> 1:1.12.12-1.fc29
  dbus-daemon 1:1.12.10-1.fc29 -> 1:1.12.12-1.fc29
  dbus-libs 1:1.12.10-1.fc29 -> 1:1.12.12-1.fc29
  dbus-tools 1:1.12.10-1.fc29 -> 1:1.12.12-1.fc29
  docker 2:1.13.1-62.git9cb56fd.fc29 -> 2:1.13.1-65.git1185cfd.fc29
  docker-common 2:1.13.1-62.git9cb56fd.fc29 -> 2:1.13.1-65.git1185cfd.fc29
  docker-rhel-push-plugin 2:1.13.1-62.git9cb56fd.fc29 ->
2:1.13.1-65.git1185cfd.fc29
  elfutils-default-yama-scope 0.174-5.fc29 -> 0.176-1.fc29
  elfutils-libelf 0.174-5.fc29 -> 0.176-1.fc29
  elfutils-libs 0.174-5.fc29 -> 0.176-1.fc29
  file 5.34-7.fc29 -> 5.34-11.fc29
  file-libs 5.34-7.fc29 -> 5.34-11.fc29
  geolite2-city 20181204-1.fc29 -> 20190205-1.fc29
  geolite2-country 20181204-1.fc29 -> 20190205-1.fc29
  glib2 2.58.2-1.fc29 -> 2.58.3-1.fc29
  gnutls 3.6.5-2.fc29 -> 3.6.6-1.fc29
  gpgme 1.11.1-3.fc29 -> 1.12.0-1.fc29
  iproute 4.18.0-3.fc29 -> 4.20.0-1.fc29
  iproute-tc 4.18.0-3.fc29 -> 4.20.0-1.fc29
  kernel 4.19.15-300.fc29 -> 4.20.8-200.fc29
  kernel-core 4.19.15-300.fc29 -> 4.20.8-200.fc29
  kernel-modules 4.19.15-300.fc29 -> 4.20.8-200.fc29
  libcurl 7.61.1-6.fc29 -> 7.61.1-9.fc29
  libidn2 2.0.5-2.fc29 -> 2.1.1a-1.fc29
  libpng 2:1.6.34-6.fc29 -> 2:1.6.34-7.fc29
  libreport-filesystem 2.9.7-2.fc29 -> 2.10.0-1.fc29
  libselinux 2.8-4.fc29 -> 2.8-6.fc29
  libselinux-utils 2.8-4.fc29 -> 2.8-6.fc29
  libsemanage 2.8-4.fc29 -> 2.8-8.fc29
  libsepol 2.8-2.fc29 -> 2.8-3.fc29
  libsolv 0.7.2-1.fc29 -> 0.7.2-2.fc29
  libxcrypt 4.4.2-3.fc29 -> 4.4.3-2.fc29
  libyaml 0.2.1-2.fc29 -> 0.2.1-5.fc29
  linux-firmware 20181219-89.git0f22c852.fc29 ->
20190213-93.git710963fe.fc29
  lua-libs 5.3.5-2.fc29 -> 5.3.5-3.fc29
  nss 3.41.0-3.fc29 -> 3.42.1-1.fc29
  nss-softokn 3.41.0-3.fc29 -> 3.42.1-1.fc29
  nss-softokn-freebl 3.41.0-3.fc29 -> 3.42.1-1.fc29
  nss-sysinit 3.41.0-3.fc29 -> 3.42.1-1.fc29
  nss-util 3.41.0-3.fc29 -> 3.42.1-1.fc29
  oci-umount 2:2.3.4-2.git87f9237.fc29 -> 2:2.5-1.gitc3cda1f.fc29
  openssh 7.9p1-3.fc29 -> 7.9p1-4.fc29
  openssh-clients 7.9p1-3.fc29 -> 7.9p1-4.fc29
  openssh-server 7.9p1-3.fc29 -> 7.9p1-4.fc29
  p11-kit 0.23.14-2.fc29 -> 0.23.15-1.fc29
  p11-kit-trust 0.23.14-2.fc29 -> 0.23.15-1.fc29
  policycoreutils 2.8-8.fc29 -> 2.8-17.fc29
  policycoreutils-python-utils 2.8-8.fc29 -> 2.8-17.fc29
  polkit 0.115-4.2.fc29 -> 0.115-4.3.fc29
  polkit-libs 0.115-4.2.fc29 -> 0.115-4.3.fc29
  python2-libselinux 2.8-4.fc29 -> 2.8-6.fc29
  python2-libsemanage 2.8-4.fc29 -> 2.8-8.fc29
  python2-policycoreutils 2.8-8.fc29 -> 2.8-17.fc29
  python2-pyOpenSSL 18.0.0-3.fc29 -> 19.0.0-1.fc29
  python3 3.7.2-1.fc29 -> 3.7.2-4.fc29
  python3-dateutil 1:2.7.0-3.fc29 -> 1:2.7.5-1.fc29
  python3-jsonschema 2.6.0-5.fc29 -> 2.6.0-6.fc29
  python3-libs 3.7.2-1.fc29 -> 3.7.2-4.fc29
  python3-libselinux 2.8-4.fc29 -> 2.8-6.fc29
  python3-libsemanage 2.8-4.fc29 -> 2.8-8.fc29
  python3-policycoreutils 2.8-8.fc29 -> 2.8-17.fc29
  python3-pyOpenSSL 18.0.0-3.fc29 -> 19.0.0-1.fc29
  rpm-ostree 2018.10-1.fc29 -> 2019.2-1.fc29
  rpm-ostree-libs 2018.10-1.fc29 -> 2019.2-1.fc29
  runc 2:1.0.0-66.dev.gitbbb17ef.fc29 -> 2:1.0.0-68.dev.git6635b4f.fc29
  selinux-policy 3.14.2-47.fc29 -> 3.14.2-49.fc29
  selinux-policy-targeted 3.14.2-47.fc29 -> 3.14.2-49.fc29
  systemd 239-8.gite339eae.fc29 -> 239-11.git4dc7dce.fc29
  systemd-container 239-8.gite339eae.fc29 -> 239-11.git4dc7dce.fc29
  systemd-libs 239-8.gite339eae.fc29 -> 239-11.git4dc7dce.fc29
  systemd-pam 239-8.gite339eae.fc29 -> 239-11.git4dc7dce.fc29
  systemd-udev 

Re: Ditch RPM in favor of DPKG

[Sérgio Basto]

On Wed, 2019-02-20 at 11:46 +0100, Dridi Boukelmoune wrote:
> No, that was a bad joke from my end, what I need is proper apt in
> Fedora to use sbuild.

If you also do the review-request for apt [1] it would be great 
dh-python also welcomed :) [2]
The problem is apt is in use by apt-rpm and was not retired yet , we
need use another name , my propose is apt-debian . 

Thanks,

[1]
https://copr-dist-git.fedorainfracloud.org/cgit/sergiomb/debs/apt.git/tree/apt.spec?h=master

[2] 
https://copr-dist-git.fedorainfracloud.org/cgit/sergiomb/debs/dh-python.git/tree/


> Dridi
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: 
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Modularity] Team IRC meeting minutes (2019-02-19)

[Nils Philippsen]

#fedora-meeting-3: Weekly Meeting of the Modularity Team



Meeting started by nils at 15:00:11 UTC.

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-3/2019-02-19/modularity.2019-02-19-15.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-3/2019-02-19/modularity.2019-02-19-15.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-3/2019-02-19/modularity.2019-02-19-15.00.log.html


Meeting summary
---
* Roll Call  (nils, 15:00:11)

* Agenda  (nils, 15:01:58)
  * #112 Discussion: Module lifecycles  (nils, 15:01:58)
  * #115 Discussion: Stream branch ownership for packages & modules
(nils, 15:01:58)

* #112 Discussion: Module lifecycles  (nils, 15:05:12)
  * LINK: https://pagure.io/modularity/issue/112   (nils, 15:05:12)
  * LINK: https://pagure.io/fesco/issue/2027   (nils, 15:05:12)
  * ACTION: asamalik to send out a complete proposal and close the
ticket  (nils, 15:24:39)

* #115 Discussion: Stream branch ownership for packages & modules
  (nils, 15:24:50)
  * LINK: https://pagure.io/modularity/issue/115   (nils, 15:24:50)
  * LINK: https://pagure.io/fesco/issue/2028   (nils, 15:24:50)
  * ACTION: asamalik to send out a complete proposal  (nils, 15:39:54)

Meeting ended at 15:45:18 UTC.




Action Items

* asamalik to send out a complete proposal and close the ticket
* asamalik to send out a complete proposal




Action Items, by person
---
* asamalik
  * asamalik to send out a complete proposal and close the ticket
  * asamalik to send out a complete proposal
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* nils (55)
* asamalik (43)
* zodbot (19)
* ignatenkobrain (11)
* mizdebsk (10)
* langdon (7)
* contyk (3)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
-- 
Nils Philippsen"Those who would give up Essential Liberty to
Software Engineer   purchase a little Temporary Safety, deserve neither
Red Hat Liberty nor Safety."  --  Benjamin Franklin, 1759
PGP fingerprint:C4A8 9474 5C4C ADE3 2B8F  656D 47D8 9B65 6951 3011


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

Re: Question about gcc test suite failures

[Jakub Jelinek]

On Wed, Feb 20, 2019 at 03:04:51PM +0100, Tomasz Kłoczko wrote:
> OK. Jakub so what kind of method you are using to recognise that something
> is wrong with gcc/gdb/binutils if none of those packages test suites seems
> may exit with non-zero exit code and some failures are perfectly OK?
> (Or maybe logic of the suite should be negated?)
> Do you have some sort of script/tool extracting results from build logs? or
> it is some other method?
> Syntax of the content /^==*TESTING/,/^==*TESTING END/p' looks a  bit
> complicated ..
> How to trace those results in more or less automated way?

It is intentionally a manual process.
For koji, my current script is:
#!/bin/sh
vr=`echo $2 | sed 's,/,-,'`
mkdir -p ~/tool-test/$1/$vr
for arch in i686 x86_64 armv7hl ppc64 ppc64le aarch64 s390 s390x ppc; do
  ar=`echo $arch | sed 's/armv7hl/armhfp/;s/i686/i386/'`
  wget 
http://kojipkgs.fedoraproject.org/packages/$1/$2/data/logs/$arch/build.log -O 
~/tool-test/$1/$vr/$ar
  if [ ! -s ~/tool-test/$1/$vr/$ar ]; then rm ~/tool-test/$1/$vr/$ar; continue; 
fi
  sed -n -i -e '/^==*TESTING/,/^==*TESTING END/p' ~/tool-test/$1/$vr/$ar
done
which populates the directories, and then I just
diff -uprN ~/tool-test/gcc/9.0.1-0.{3,4}.fc30 
and use my own judgement of what is and what isn't a blocker and what needs
to be fixed even if it is not a blocker.

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

Fedora 30 Mass Branching

[Mohan Boddu]

Hi All,

Fedora 30 has now been branched, please be sure to do a git pull
--rebase to pick up the new branch, as an additional reminder
rawhide/f31 has been completely isolated from previous releases, so
this means that anything you do for f30 you also have to do in the
master branch and do a build there. There will be a Fedora 30 compose
and it'll appear in
http://dl.fedoraproject.org/pub/fedora/linux/development/30/ once
complete. Please be sure to check it out. Bodhi is currently not
active for Fedora 30, it will be enabled in couple of weeks time when we hit
Beta change freeze point in the Fedora 30 schedule[1].

Mohan Boddu.

[1] https://fedoraproject.org/wiki/Releases/30/Schedule
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org

Fedora 30 Mass Branching

[Mohan Boddu]

Hi All,

Fedora 30 has now been branched, please be sure to do a git pull
--rebase to pick up the new branch, as an additional reminder
rawhide/f31 has been completely isolated from previous releases, so
this means that anything you do for f30 you also have to do in the
master branch and do a build there. There will be a Fedora 30 compose
and it'll appear in
http://dl.fedoraproject.org/pub/fedora/linux/development/30/ once
complete. Please be sure to check it out. Bodhi is currently not
active for Fedora 30, it will be enabled in couple of weeks time when we hit
Beta change freeze point in the Fedora 30 schedule[1].

Mohan Boddu.

[1] https://fedoraproject.org/wiki/Releases/30/Schedule
___
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://getfedora.org/code-of-conduct.html
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Question about gcc test suite failures

[Tomasz Kłoczko]

On Wed, 20 Feb 2019 at 14:51, Jakub Jelinek  wrote:
[..]

> The aim is to avoid regressions, not zero FAIL rate, which e.g. for the
> guality testcase is not really possible as the testing matrix is too large
> for debug info coverage, -O levels x targets x ISA choices x GDB issues
> and it is impossible to encode that into xfails.
> Plus, the rpm builds test both normally and with additional
> -fstack-protector-strong as that is what the whole distro does, while
> normally the latter isn't included.  So, some FAILs might be once with
> normal options and once with -fstack-protector-strong, other tests only
> FAIL
> with the latter e.g. when testing asan and having UB in the test to test it
> how asan handles it and -fstack-protector-strong may stand in a way of
> that.
> There are some flakey tests too (mostly in the go testsuite).
>
> So, I have a directory with years of testsuite results from koji/brew
> builds, essentially build logs from all the architectures massaged through
> sed -n -e '/^==*TESTING/,/^==*TESTING END/p'
> and compare that regularly for new builds.
>

OK. Jakub so what kind of method you are using to recognise that something
is wrong with gcc/gdb/binutils if none of those packages test suites seems
may exit with non-zero exit code and some failures are perfectly OK?
(Or maybe logic of the suite should be negated?)
Do you have some sort of script/tool extracting results from build logs? or
it is some other method?
Syntax of the content /^==*TESTING/,/^==*TESTING END/p' looks a  bit
complicated ..
How to trace those results in more or less automated way?

kloczek
-- 
Tomasz Kłoczko | 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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Question about gcc test suite failures

[Jakub Jelinek]

On Wed, Feb 20, 2019 at 02:31:37PM +0100, Tomasz Kłoczko wrote:
> Recently I've been trying to trace some gcc issue so I've downloaded my gcc
> src.rpm to try to build my own package.
> During review build log I found a lot of test suite failures.
> Initially I've been thinking that something is wrong with my devel env so
> I've peaked on official gcc build logs and I found that I have even less
> such failures than number of such issues on rawhide builders.

The aim is to avoid regressions, not zero FAIL rate, which e.g. for the
guality testcase is not really possible as the testing matrix is too large
for debug info coverage, -O levels x targets x ISA choices x GDB issues
and it is impossible to encode that into xfails.
Plus, the rpm builds test both normally and with additional
-fstack-protector-strong as that is what the whole distro does, while
normally the latter isn't included.  So, some FAILs might be once with
normal options and once with -fstack-protector-strong, other tests only FAIL
with the latter e.g. when testing asan and having UB in the test to test it
how asan handles it and -fstack-protector-strong may stand in a way of that.
There are some flakey tests too (mostly in the go testsuite).

So, I have a directory with years of testsuite results from koji/brew
builds, essentially build logs from all the architectures massaged through
sed -n -e '/^==*TESTING/,/^==*TESTING END/p'
and compare that regularly for new builds.

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

Question about gcc test suite failures

[Tomasz Kłoczko]

Recently I've been trying to trace some gcc issue so I've downloaded my gcc
src.rpm to try to build my own package.
During review build log I found a lot of test suite failures.
Initially I've been thinking that something is wrong with my devel env so
I've peaked on official gcc build logs and I found that I have even less
such failures than number of such issues on rawhide builders.

Mine package:

$ grep ^FAIL: -c gcc.out
780

Vs. official:
$ curl -s
https://kojipkgs.fedoraproject.org//work/tasks/681/32910681/build.log |
grep -c FAIL:
1114

Some of those failures seems are expected as I'm able to find in my build
log fragments like:

=== gnat Summary for unix/ ===

# of expected passes2976
# of expected failures  23
# of unsupported tests  3

However I found other like:

=== gcc Summary for unix/ ===

# of expected passes143765
# of unexpected failures101
# of unexpected successes   25
# of expected failures  554
# of unsupported tests  2225

Did all those unexpected failures are symptoms some not finished
modifications and/or not updated test units or those failures says that
something really is wrong with gcc?

At the moment I'm not sure but I think that similar situation is with
binutils but I think that generally during my build I saw a lot of
failures. All together all those tests have been ignored and package build
was successful.

kloczek
-- 
Tomasz Kłoczko | 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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

authselect: owning configuration files under /etc/authselect

[Pavel Březina]

Hello list,
Igor suggested in authselect pull request that authselect should own 
configuration files in /etc/authselect.


See: https://src.fedoraproject.org/rpms/authselect/pull-request/5

More specifically:
+ %ghost %{_sysconfdir}/authselect/dconf-db
+ %ghost %{_sysconfdir}/authselect/dconf-locks
+ %ghost %{_sysconfdir}/authselect/fingerprint-auth
+ %ghost %{_sysconfdir}/authselect/nsswitch.conf
+ %ghost %{_sysconfdir}/authselect/password-auth
+ %ghost %{_sysconfdir}/authselect/postlogin
+ %ghost %{_sysconfdir}/authselect/smartcard-auth
+ %ghost %{_sysconfdir}/authselect/system-auth
+ %ghost %{_sysconfdir}/authselect/user-nsswitch.conf

This makes perfect sense, however if authselect owns these files and 
admin then uninstalls authselect, the system will be locked out because 
pam configuration was removed.


I do not know any way how to own these files and yet leave them 
untouched after uninstallation, thus I see only two solutions:


1) Do not own these files at all.
2) Remove symlinks to /etc/authselect/* and restore these files to their 
original location (i.e. /etc/nsswitch.conf, /etc/pam.d/*).


Which do you prefer? Is there other way to do this?

Thank you,
Pavel.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1678623] Review Request: strip-nondeterminism - File non-deterministic information stripper

[bugzilla]

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



--- Comment #4 from Dridi Boukelmoune  ---
I'm ok with epel7, I would have objected to maintain it for epel6 myself :)

And the packlist question is exactly why I asked for perl-experienced
co-maintainers for this package, sbuild and apt. I can dig that kind of
problems but it will take me much more time when the midden hits the windmill.

-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: koji & s390x - [Errno 111] Connection refused

[Stephen John Smoogen]

On Wed, 20 Feb 2019 at 03:14, Lumir Balhar  wrote:
>
> I've created a fedora-infra issue:
> https://pagure.io/fedora-infrastructure/issue/7580

There was a configuration error that mizdebsk found and fixed. The
problem should be fixed now.


>
> On 2/20/19 8:44 AM, Lumir Balhar wrote:
> > Hello.
> >
> > I am building python-cassandra-driver in Koji and my last two attempts
> > failed on s390x with error: URLError:  > Connection refused>
> >
> > I found also other builds with the same issue:
> >
> > * https://koji.fedoraproject.org/koji/taskinfo?taskID=32919248
> > * https://koji.fedoraproject.org/koji/taskinfo?taskID=32918607
> > * https://koji.fedoraproject.org/koji/taskinfo?taskID=32919840
> > * https://koji.fedoraproject.org/koji/taskinfo?taskID=32920470 (noarch
> > package)
> > * https://koji.fedoraproject.org/koji/taskinfo?taskID=32920521
> > * https://koji.fedoraproject.org/koji/taskinfo?taskID=32920386
> > * https://koji.fedoraproject.org/koji/taskinfo?taskID=32918406
> >
> > Could please anybody take a look on that?
> >
> > Thank you. Lumír
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org



-- 
Stephen J Smoogen.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: libravatar is in fedorainfracloud!

[Stephen John Smoogen]

On Wed, 20 Feb 2019 at 00:07, John Harris  wrote:
>
> On Tuesday, February 19, 2019 11:46:16 PM EST Michal Novotny wrote:
> > Hello!
> >
> > maybe you know that around April 2018, there was an announcement that
> > libravatar service (a service for serving user avatars) is shutting

> Awesome! I'm glad we won't be losing libravatar, and I couldn't be happier
> that it's supported by Fedora's Infra.
>

I would like to clarify this as quickly as possible. Fedora
Infrastructure's support is only to give out hardware resources to the
this project. We do not have any fixing abilities other than rebooting
the server if it gets stuck. People having problems like libravatars'
avatars or login problems etc will need to contact the libravatar
organization versus #fedora-admin or the Fedora Infrastructure ticket
system.


-- 
Stephen J Smoogen.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Ditch RPM in favor of DPKG

[Dridi Boukelmoune]

On Wed, Feb 20, 2019 at 11:04 AM Akarshan Biswas
 wrote:
>
> > I know how important RPM is to the Fedora Project, but it breaks everything 
> > downstream and we'd be better off using DPKG as we should have from day one.
>
> Doesn't we have flatpaks for that purpose?

No, that was a bad joke from my end, what I need is proper apt in
Fedora to use sbuild.

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

[Bug 1678915] perl-Test-Timer-2.10 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-Test-Timer-2.10-1.fc31
   ||perl-Test-Timer-2.10-1.fc30
 Resolution|--- |RAWHIDE
Last Closed||2019-02-20 10:41:15



-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: Ditch RPM in favor of DPKG

[Akarshan Biswas]

> I know how important RPM is to the Fedora Project, but it breaks everything 
> downstream and we'd be better off using DPKG as we should have from day one.

Doesn't we have flatpaks for that purpose?



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

[Bug 1678889] perl-Daemon-Control-0.001009 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-Daemon-Control-0.00100
   ||9-1.fc31
   ||perl-Daemon-Control-0.00100
   ||9-1.fc30
 Resolution|--- |RAWHIDE
Last Closed||2019-02-20 09:54:47



-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: Review request

[Petr Pisar]

On Tue, Feb 19, 2019 at 08:30:00PM +0100, Robert-André Mauchin wrote:
> Can a kind soul help with a review?
> 
> Review Request: perl-File-Rsync - Perl module interface to rsync
> https://bugzilla.redhat.com/show_bug.cgi?id=1678884
> 
Done. Almost perfect.

-- Petr


signature.asc
Description: PGP signature
___
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: Adding zstd support for mksquashfs

[Fabio Valentini]

On Wed, Feb 20, 2019, 10:24 J. Scheurich  wrote:

> On Wed, 20 Feb 2019 10:15:13 +0100
> Roberto Ragusa  wrote:
>
>
> > squashfs is now supporting the interesting zstd compression algorithm,
> > but the mksquashfs tool in Fedora doesn't support zstd.
> ...
> > Which is the correct way to get this into Fedora?
>
> You have to create a RPM package


> https://docs.fedoraproject.org/en-US/packaging-guidelines/
>
> and use the review process
>

That's not really true, since the package in question already exists in
fedora and would only need an update.

Either poke the current maintainer to update it to a git master snapshot in
rawhide, or submit a pull request against the package yourself (you don't
even need to be an approved packager for that, and pagure also supports
remote PRs from, for example, GitHub).

Fabio


> https://fedoraproject.org/wiki/Package_Review_Process
>
> It can be take time to get fedora sponsored...
>
> 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://getfedora.org/code-of-conduct.html
> 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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Adding zstd support for mksquashfs

[J. Scheurich]

On Wed, 20 Feb 2019 10:15:13 +0100
Roberto Ragusa  wrote:


> squashfs is now supporting the interesting zstd compression algorithm,
> but the mksquashfs tool in Fedora doesn't support zstd.
...
> Which is the correct way to get this into Fedora?

You have to create a RPM package

https://docs.fedoraproject.org/en-US/packaging-guidelines/

and use the review process

https://fedoraproject.org/wiki/Package_Review_Process

It can be take time to get fedora sponsored...

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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: PSA: Bodhi cannot associate bugs with updates right now

[Milan Crha]

On Tue, 2019-02-19 at 18:32 -0500, Randy Barlow wrote:
> Bodhi 3.13.2 has been deployed to production just now, which should
> address the above issue. You should again be able to associate bugs
> with updates. Apologies for the issue!

Hi,
I've been affected of this, even I didn't know what happened, because
the web UI didn't show any error message or a clue what was wrong. The
'Submit' button just spin for few seconds and then nothing happened,
which had been quite frustrating.

Could the web UI be changed to claim all errors when it encounters any,
instead of being just quiet and broken with no reason given?
Thanks and bye,
Milan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1678875] perl-DBIx-Class-Schema-Config-0.001012 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-DBIx-Class-Schema-Conf
   ||ig-0.001012-1.fc31
   ||perl-DBIx-Class-Schema-Conf
   ||ig-0.001012-1.fc30
 Resolution|--- |RAWHIDE
Last Closed||2019-02-20 09:18:47



-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Adding zstd support for mksquashfs

[Roberto Ragusa]

Hi,

squashfs is now supporting the interesting zstd compression algorithm,
but the mksquashfs tool in Fedora doesn't support zstd.
The upstream code does, it is in the master branch, but there have not
been releases for years (version 4.3 since fedora 19).

https://sourceforge.net/p/squashfs/code/commit_browser

I tried compiling it and it went fine after adding a couple of
#include 
not actually related to zstd.

Which is the correct way to get this into Fedora?

Regards.
-- 
   Roberto Ragusamail at robertoragusa.it
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Orphaned packages that will be retired (and everything will most likely burn)

[Till Maas]

On Fri, Feb 15, 2019 at 04:28:17PM +0100, Vít Ondruch wrote:
> 
> Dne 15. 02. 19 v 14:22 Emmanuel Seyman napsal(a):
> > * Hans de Goede [15/02/2019 12:09] :
> >> And automatic scripts really just should hand it over to the first 
> >> co-maintainer
> >> in the list.
> 
> 
> As long as we have no idea if the other maintainers are active, I am
> strongly against the automation. I've been there. Followed nor
> responsive policy just to find out later that instead of orphaning the
> package, next inactive maintainer became owner. Very frustrating 

The advantage is that this will clean up the co-maintainer list
eventually.

Kind regards
Till
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1678447] perl-Time-HiRes-1.9760 is available

[bugzilla]

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



--- Comment #2 from Fedora Update System  ---
perl-Time-HiRes-1.9760-1.fc29 has been submitted as an update to Fedora 29.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-0d373389e7

-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1678623] Review Request: strip-nondeterminism - File non-deterministic information stripper

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 CC||ppi...@redhat.com



--- Comment #3 from Petr Pisar  ---
(In reply to Sergio Monteiro Basto from comment #2)
> BUILDSTDERR: Installed (but unpackaged) file(s) found:
> BUILDSTDERR:   
> /usr/lib64/perl5/vendor_perl/auto/File/StripNondeterminism/.packlist
> 
See . I.e. if you
use NO_PACKLIST=1, you have to buil-require perl(ExtUtils::MakeMaker) >= 6.76.

-- 
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: koji & s390x - [Errno 111] Connection refused

[Lumir Balhar]

I've created a fedora-infra issue: 
https://pagure.io/fedora-infrastructure/issue/7580


On 2/20/19 8:44 AM, Lumir Balhar wrote:

Hello.

I am building python-cassandra-driver in Koji and my last two attempts 
failed on s390x with error: URLError: Connection refused>


I found also other builds with the same issue:

* https://koji.fedoraproject.org/koji/taskinfo?taskID=32919248
* https://koji.fedoraproject.org/koji/taskinfo?taskID=32918607
* https://koji.fedoraproject.org/koji/taskinfo?taskID=32919840
* https://koji.fedoraproject.org/koji/taskinfo?taskID=32920470 (noarch 
package)

* https://koji.fedoraproject.org/koji/taskinfo?taskID=32920521
* https://koji.fedoraproject.org/koji/taskinfo?taskID=32920386
* https://koji.fedoraproject.org/koji/taskinfo?taskID=32918406

Could please anybody take a look on that?

Thank you. Lumír 

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