Making Fedora secure - Package exit policy for security

[Huzaifa Sidhpurwala]

Hi All,

I was asked to bring this issue[1] to the developer community before
FESCO makes a decision.

In several instances[2] there exists packages in Fedora, in which
package-maintainers did not patch security issues, for multiple reasons
including 1. non-responsive maintainer 2. issue hard to patch 3. no one
cares?

This is a risk for the distribution, our users and community as a whole
and not to mentioned bad PR :)

I would like to propose the following:


1. If a CRITICAL or IMPORTANT security issue is open against a package
in Fedora-X and by the time X is EOL and the issue is not addressed,
proactively remove the package from X+1
2. If a MODERATE or LOW security issue is open against a package in
Fedora -X and by the time X+! is EOL, the issue is not addressed, remove
it from X+2

Note:
1. Once pkg is patches, it can be rebuild and re-introduced into the distro
2. X/X+1 is the best boundary to remove the insecure packages imo, since
inbetween removals are not possible due to the way mirrors work.
3. Maintain a list somewhere (automated maybe) of the list of packages
removed and why.
4. Have a list of critical pkg, which cannot be removed which will break
the distro.

The above is not set in stone, but is open for discussion. Let me know
what you guys think!

In the end, i would like you leave you all with this parting link:
https://sensorstechforum.com/arch-linux-aur-repository-found-contain-malware/

[1] https://pagure.io/fesco/issue/1935
[2]
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW_status=ASSIGNED=Fedora=SecurityTracking%2C%20_type=allwords_id=9076731=changeddate%2Cpriority%2Cbug_id=Fedora_based_on=_format=advanced



-- 
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/message/ZCM54WM3WYZAJ3MXAOXJHLZCUGZONN3F/

[Bug 1610065] New: perl-HTTP-Tiny-0.074 is available

[bugzilla]

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

Bug ID: 1610065
   Summary: perl-HTTP-Tiny-0.074 is available
   Product: Fedora
   Version: rawhide
 Component: perl-HTTP-Tiny
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com



Latest upstream release: 0.074
Current version/release in rawhide: 0.070-417.fc29
URL: http://search.cpan.org/dist/HTTP-Tiny/

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

-- 
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/message/X4RAEOKPJRFVNHEQ3L7BW63U2PXK53IW/

Re: Intent to retire python-svg

[Robert Brown]

Julien,

I'd be happy to take some ownership.  Any info?

Thanks

On Mon, Jul 30, 2018, 4:15 PM Julien Enselme  wrote:

> Hi all,
>
> I intend to retire python-svg. Tests are failing on Python 3.7 for a
> reason I cannot figure, there was no commit during the last year and
> according to `repoquery --whatrequires python2-svgwrite` and `repoquery
> --whatrequires python3-svgwrite` nothing uses it anymore.
>
> If you want to maintain it, please step up.
>
> Regards,
> --
> Julien Enselme
> http://www.jujens.eu/
> ___
> 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/message/CMRWUNE776D4GDENV673PUOUPQFJFZLH/
>
___
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/message/TBHUZPFPGTYIDE3U6JPNSWZUXR7KRU3H/

[Fedocal] Reminder meeting : Modularity Office Hours

[nils]

Dear all,

You are kindly invited to the meeting:
   Modularity Office Hours on 2018-07-31 from 10:00:00 to 11:00:00 US/Eastern
   At fedora-modular...@chat.freenode.net

The meeting will be about:
This is where you ask the Fedora Modularity Team questions (and we try to 
answer them)!

Join us on [IRC](irc://chat.freenode.net/#fedora-modularity): 
#fedora-modularity on [FreeNode](https://freenode.net)


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

___
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/message/H7UAWZNCPICTFW5YOLODWAALEBVOYCQW/

Re: dokuwiki packagers unresponsive

[Sérgio Basto]

On Mon, 2018-07-30 at 23:07 +0200, Peter 'Pessoft' Kolínek wrote:
> On 2018-07-27 17:08, Matthias Runge wrote:
> > On Fri, Jul 27, 2018 at 02:51:25AM +0100, Sérgio Basto wrote:
> > > On Thu, 2018-07-26 at 21:43 -0400, Solomon Peachy wrote:
> > > > On Thu, Jul 26, 2018 at 09:09:25PM +0200, Peter 'Pessoft'
> > > > Kolínek
> > > > wrote:
> > > > > I'd like to fix some issues (including security problems)
> > > > > which are
> > > > > for
> > > > > a long time present in dokuwiki package. Maintainers of the
> > > > > dokuwiki
> > > > > however seem unresponsive.
> > > > 
> > > > It's worth stating that "some issues" is a euphamism for "the
> > > > package has been fundamentally broken since Fedora 24."
> > > > 
> > > >   https://bugzilla.redhat.com/show_bug.cgi?id=1372948
> > > 
> > > 
> > > The main admin (togdog) usually give permission to commit if you
> > > ask
> > > him , at least did to me .
> > 
> > Right, I can second that. It worked for me as well.
> > 
> > With pagure in place, you could also submit pull requests to
> > improve
> > the situation.
> > 
> 
> I've already submitted a pull request for dokuwiki circa a month
> ago: 
> https://src.fedoraproject.org/rpms/dokuwiki/pull-request/2
> Also for topdog's other package ike 10 days ago: 
> https://src.fedoraproject.org/rpms/ike/pull-request/1
> 
> @Matthias, Sérgio: Do you know at which month approximately you had
> a 
> response from topdog?

For php-facedetect was in 2016-05 (deduced by my first commit) and in
dpkg 2013-02 (but I'm not sure if was him that gave me permissions) 


> On fedmsg I can see last entries invoked by topdog 11 months ago.
> 
> Thanks for your input.
> 
> Peter
> 
> 
> Freehosting PIPNI - http://www.pipni.cz/
> ___
> 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_guidelin
> es
> List Archives: https://lists.fedoraproject.org/archives/list/devel@li
> sts.fedoraproject.org/message/RKG4ENGCEXGG5S2GYTJUCDTILL4XAXRY/
-- 
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/message/ILTAL4Q5XHVN3XYLQY6TXMBDJUYW3UP2/

Re: dokuwiki packagers unresponsive

[Peter 'Pessoft' Kolínek]

On 2018-07-27 17:08, Matthias Runge wrote:

On Fri, Jul 27, 2018 at 02:51:25AM +0100, Sérgio Basto wrote:

On Thu, 2018-07-26 at 21:43 -0400, Solomon Peachy wrote:
> On Thu, Jul 26, 2018 at 09:09:25PM +0200, Peter 'Pessoft' Kolínek
> wrote:
> > I'd like to fix some issues (including security problems) which are
> > for
> > a long time present in dokuwiki package. Maintainers of the
> > dokuwiki
> > however seem unresponsive.
>
> It's worth stating that "some issues" is a euphamism for "the
> package has been fundamentally broken since Fedora 24."
>
>   https://bugzilla.redhat.com/show_bug.cgi?id=1372948


The main admin (togdog) usually give permission to commit if you ask
him , at least did to me .


Right, I can second that. It worked for me as well.

With pagure in place, you could also submit pull requests to improve
the situation.



I've already submitted a pull request for dokuwiki circa a month ago: 
https://src.fedoraproject.org/rpms/dokuwiki/pull-request/2
Also for topdog's other package ike 10 days ago: 
https://src.fedoraproject.org/rpms/ike/pull-request/1


@Matthias, Sérgio: Do you know at which month approximately you had a 
response from topdog?

On fedmsg I can see last entries invoked by topdog 11 months ago.

Thanks for your input.

Peter


Freehosting PIPNI - http://www.pipni.cz/
___
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/message/RKG4ENGCEXGG5S2GYTJUCDTILL4XAXRY/

Fedora testing-20180730.0 compose check report

[Fedora compose checker]

No missing expected images.

Passed openQA tests: 2/2 (x86_64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/message/6PFTM6QDNAJ7HDIOHS52H3JV2BMA6LOR/

[Bug 1609256] perl-CPAN-Perl-Releases-3.72 is available

[bugzilla]

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



--- Comment #4 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.72-1.fc28 has been pushed to the Fedora 28 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-2018-29e957c41c

-- 
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/message/3ECTYNBX7ASCOW2X6V6U3LKJJ4DVLZF3/

[Bug 1606925] perl-CPAN-Perl-Releases-3.70 is available

[bugzilla]

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



--- Comment #8 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.72-1.fc28 has been pushed to the Fedora 28 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-2018-29e957c41c

-- 
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/message/AUDY7TNEKEJRCCOBWY7RDKLWUIELXAQ6/

Intent to retire python-svg

[Julien Enselme]

Hi all,

I intend to retire python-svg. Tests are failing on Python 3.7 for a
reason I cannot figure, there was no commit during the last year and
according to `repoquery --whatrequires python2-svgwrite` and `repoquery
--whatrequires python3-svgwrite` nothing uses it anymore.

If you want to maintain it, please step up.

Regards,
-- 
Julien Enselme
http://www.jujens.eu/


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/message/CMRWUNE776D4GDENV673PUOUPQFJFZLH/

[Bug 1609221] License 'public domain' is not valid

[bugzilla]

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



--- Comment #5 from Tom "spot" Callaway  ---
(In reply to Dave Olsthoorn from comment #4)
> Maybe the confusion is because of this:
> https://metacpan.org/changes/distribution/DBIx-Simple#L26
> 
> It seems the versions after 1.32 are not released into the public domain
> anymore, but released under "any(OSI)" (as the change log indicates).

Looks like you're right. From 1.32:

=head1 LICENSE

There is no license. This software was released into the public domain. Do with
it what you want, but on your own risk. The author disclaims any
responsibility.



However, since the author has reasserted copyright post 1.32, that doesn't
change my advice in comment 3.

-- 
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/message/Q4KTI5BD3Z2UZUTIKLL66DAI7C5OHUI7/

[Bug 1609221] License 'public domain' is not valid

[bugzilla]

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



--- Comment #4 from Dave Olsthoorn  ---
Maybe the confusion is because of this:
https://metacpan.org/changes/distribution/DBIx-Simple#L26

It seems the versions after 1.32 are not released into the public domain
anymore, but released under "any(OSI)" (as the change log indicates).

-- 
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/message/LKWNIFCS6SFBZR7LCZ3HLVFSC5HAUT3M/

[Bug 1609221] License 'public domain' is not valid

[bugzilla]

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

Tom "spot" Callaway  changed:

   What|Removed |Added

 Status|CLOSED  |ASSIGNED
 Resolution|NOTABUG |---
   Keywords||Reopened



--- Comment #3 from Tom "spot" Callaway  ---
Okay, that is a different situation. Copyright has not been abandoned (or
expired) on this work, the author has merely granted a sort of meta-license
which permits for any OSI approved license to be applied.

Technically, "Public Domain" is not an OSI approved license, so it is not a
valid choice (though, I suspect it was the maintainer's attempt to quantify
that weird meta-license).

The easy fix is to change the License field to be something permissive and OSI
approved. I would suggest changing the spec to:

# Technically, the license allows us to choose any OSI approved license, so we 
# choose MIT for maximal compatibility.
License: MIT

-- 
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/message/EAWH5BKKYNWTE2TA3MYXD32VFC6TK54K/

Fedora Rawhide-20180730.n.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 10/138 (x86_64), 23/24 (i386), 1/2 (arm)

New failures (same test did not fail in Rawhide-20180729.n.0):

ID: 261800  Test: x86_64 universal install_scsi_updates_img
URL: https://openqa.fedoraproject.org/tests/261800
ID: 261802  Test: x86_64 universal install_repository_http_graphical
URL: https://openqa.fedoraproject.org/tests/261802
ID: 261814  Test: x86_64 universal upgrade_kde_64bit
URL: https://openqa.fedoraproject.org/tests/261814

Old failures (same test failed in Rawhide-20180729.n.0):

ID: 261713  Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller
URL: https://openqa.fedoraproject.org/tests/261713
ID: 261721  Test: i386 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/261721
ID: 261722  Test: i386 Server-dvd-iso install_default
URL: https://openqa.fedoraproject.org/tests/261722
ID: 261725  Test: i386 Everything-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/261725
ID: 261742  Test: i386 Workstation-live-iso install_default
URL: https://openqa.fedoraproject.org/tests/261742
ID: 261743  Test: i386 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/261743
ID: 261744  Test: i386 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/261744
ID: 261757  Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/261757
ID: 261758  Test: i386 KDE-live-iso install_default
URL: https://openqa.fedoraproject.org/tests/261758
ID: 261759  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/261759
ID: 261817  Test: x86_64 universal install_european_language
URL: https://openqa.fedoraproject.org/tests/261817
ID: 261818  Test: x86_64 universal install_cyrillic_language
URL: https://openqa.fedoraproject.org/tests/261818
ID: 261819  Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/261819
ID: 261820  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/261820
ID: 261841  Test: x86_64 universal install_iscsi
URL: https://openqa.fedoraproject.org/tests/261841
ID: 261845  Test: i386 universal install_repository_http_graphical
URL: https://openqa.fedoraproject.org/tests/261845
ID: 261846  Test: i386 universal install_scsi_updates_img
URL: https://openqa.fedoraproject.org/tests/261846
ID: 261847  Test: i386 universal install_simple_encrypted
URL: https://openqa.fedoraproject.org/tests/261847
ID: 261848  Test: i386 universal upgrade_desktop_32bit
URL: https://openqa.fedoraproject.org/tests/261848
ID: 261849  Test: i386 universal install_software_raid
URL: https://openqa.fedoraproject.org/tests/261849
ID: 261850  Test: i386 universal install_btrfs
URL: https://openqa.fedoraproject.org/tests/261850
ID: 261851  Test: i386 universal install_ext3
URL: https://openqa.fedoraproject.org/tests/261851
ID: 261852  Test: i386 universal install_blivet_btrfs
URL: https://openqa.fedoraproject.org/tests/261852
ID: 261853  Test: i386 universal install_blivet_no_swap
URL: https://openqa.fedoraproject.org/tests/261853
ID: 261854  Test: i386 universal install_blivet_xfs
URL: https://openqa.fedoraproject.org/tests/261854
ID: 261855  Test: i386 universal install_blivet_lvmthin
URL: https://openqa.fedoraproject.org/tests/261855
ID: 261856  Test: i386 universal install_package_set_minimal
URL: https://openqa.fedoraproject.org/tests/261856
ID: 261857  Test: i386 universal install_lvmthin
URL: https://openqa.fedoraproject.org/tests/261857
ID: 261858  Test: i386 universal install_blivet_ext3
URL: https://openqa.fedoraproject.org/tests/261858
ID: 261859  Test: i386 universal install_blivet_software_raid
URL: https://openqa.fedoraproject.org/tests/261859
ID: 261861  Test: i386 universal install_package_set_kde
URL: https://openqa.fedoraproject.org/tests/261861

Soft failed openQA tests: 69/138 (x86_64), 1/24 (i386)
(Tests completed, but using a workaround for a known bug)

New soft failures (same test did not soft fail in Rawhide-20180729.n.0):

ID: 261698  Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/261698
ID: 261699  Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/261699
ID: 261815  Test: x86_64 universal upgrade_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/261815
ID: 261821  Test: x86_64 universal install_simple_encrypted@uefi
URL: https://openqa.fedoraproject.org/tests/261821
ID: 261840  Test: x86_64 universal install_blivet_lvmthin@uefi
URL: https://openqa.fedoraproject.org/tests/261840

Old soft failures (same test soft failed in Rawhide-20180729.n.0):

ID: 261700  Test: x86_64 Server-dvd-iso install_default_upload
URL: 

Fedora updates-20180730.1 compose check report

[Fedora compose checker]

No missing expected images.

Passed openQA tests: 2/2 (x86_64)

Installed system changes in test x86_64 AtomicHost-dvd_ostree-iso 
install_default: 
System load changed from 0.07 to 0.38
Previous test data: https://openqa.fedoraproject.org/tests/261624#downloads
Current test data: https://openqa.fedoraproject.org/tests/261885#downloads

Installed system changes in test x86_64 AtomicHost-dvd_ostree-iso 
install_default@uefi: 
System load changed from 0.10 to 0.21
Previous test data: https://openqa.fedoraproject.org/tests/261625#downloads
Current test data: https://openqa.fedoraproject.org/tests/261886#downloads
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/message/UJ3ZW5TZ7OP6LFQU2LGHW7R6Z5HOUCXG/

[Bug 1609221] License 'public domain' is not valid

[bugzilla]

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



--- Comment #2 from Dave Olsthoorn  ---
Okay, but how does this work qualify as "Public Domain"? There is a license
text that mentions any OSI approved license is valid, not that it was released
to the public domain: https://metacpan.org/pod/DBIx::Simple#LICENSE

-- 
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/message/MFN5SMRP7RDKPYANVAR5MWKVLU7OFC6R/

[EPEL-devel] Fedora EPEL 7 updates-testing report

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
  50  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3835d39d1a   
unrtf-0.21.9-8.el7
  45  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-15b7dc35af   
pass-1.7.2-1.el7
  26  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-ccbe8e3c4d   
knot-resolver-2.4.0-1.el7
  18  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-d2e0971e9b   
uwsgi-2.0.17.1-1.el7
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3f07844689   
znc-1.7.1-1.el7
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-d8d62b4f6c   
suricata-4.0.5-1.el7
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-8de40d24ca   
redis-3.2.12-1.el7
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-f19460105c   
pam_yubico-2.26-1.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-5b5c4b0050   
rust-1.27.2-3.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-f9d6ff695a   
bibutils-6.6-1.el7 ghc-hs-bibutils-6.6.0.0-1.el7 pandoc-citeproc-0.3.0.1-4.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-e9a8615099   
mbedtls-2.7.5-1.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-52b5b56d0a   
seamonkey-2.49.4-2.el7
   0  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-5346e2123a   
dpkg-1.18.25-1.el7


The following builds have been pushed to Fedora EPEL 7 updates-testing

odcs-0.2.9-1.el7
tklib-0.5-1.el7

Details about builds:



 odcs-0.2.9-1.el7 (FEDORA-EPEL-2018-140ed69abe)
 The On Demand Compose Service

Update Information:

  - Cache Pulp repos and fix the mergerepo_c call used in some corner cases
when repositories for multiple architectures are in single Pulp content set.

ChangeLog:

* Mon Jul 30 2018 Jan Kaluza  - 0.2.9-1
- new version




 tklib-0.5-1.el7 (FEDORA-EPEL-2018-ff3105a60f)
 Collection of widgets and other packages for Tk

Update Information:

Initial build for Epel7.

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org/message/E2SPEZHQZYJL3AHLADXHDRGF6IRBJXOV/

Re: Guideline change: glibc malloc as the C/C++/Rust allocator

[Andrew Lutomirski]

On Jul 27, 2018, at 9:58 AM, Owen Taylor  wrote:

On Fri, Jul 27, 2018 at 9:44 AM, Florian Weimer  wrote:

> On 07/27/2018 03:33 PM, John Reiser wrote:The key principle is that
> sizeof(foo) must be the stride of an array of foo,
>
> and the array must guarantee alignment of each element in the array.
>>
>
> Why do you think that?  If some documentation claims this is the case for
> individual objects, we need to fix it.


struct sizes *do* have this property - they are rounded up so that arrays
have the correct alignment.
But that certainly doesn't imply that malloc(7) is allowed to give you
unaligned memory.



As an x86 person but only occasionally a standardese person, I find the
idea that malloc(8) should return a 16-byte-aligned pointer on x86 to be
nuts. I can only think of one non-UB way to notice the difference between
an 8-byte and 16-byte aligned result, and that way would be to literally
cast to (u)intptr_t and look at the low bits.  This is plausibly relevant
to certain VMs and tag bit users, but is totally irrelevant to basically
anything else.  And 16-byte alignment for small allocations is a giant
waste of memory.

So I think that glibc should change its behavior here to match everyone
else, and get the ABI document changed if needed.

Frankly, I find it a bit odd that C stack frames on x86_64 want 16 byte
alignment, and it took until gcc 4.8 (IIRC) to get proper support to opt
out.
___
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/message/5MHUB6W7TX576QQQSHAHLUFBZJKVJBXE/

Re: F28: Mismatch between the program and library build versions detected, gcc-c++, wxGTK3

[Jonathan Wakely]

On 25/07/18 13:25 -0400, Scott Talbert wrote:

On Wed, 25 Jul 2018, Wolfgang Stoeggl wrote:


Hello,
a recent F28 update build of poedit [1] shows the following message after 
starting:

Warning: Mismatch between the program and library build versions detected.
The library used 3.0 (wchar_t,compiler with C++ ABI 1012,wx 
containers,compatible with 2.8),
and your program used 3.0 (wchar_t,compiler with C++ ABI 1013,wx 
containers,compatible with 2.8).


This warning can be safely ignored.  wxGTK3 has this rather annoying 
behavior where it reports a warning when the C++ ABI of a wxGTK3 user 
doesn't match that of the library.


It still seems a bit wrong to me for the C++ ABI to be changing in a 
Fedora stable release, but this does seem to happen consistently.  


Consistently?

The recent change was a bug fix, to revert an unintentional ABI change
compared to previous versions. When did it last happen in a stable
release?

___
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/message/RA6CHVP4OTFFAJ457INPJBR6ODZQZFX3/

Re: Guideline change: glibc malloc as the C/C++/Rust allocator

[R P Herrold]

On Mon, 30 Jul 2018, Jonathan Wakely wrote:

> On 26/07/18 12:45 -0400, R P Herrold wrote:

> > The use here of 'interpose' is unclear to me -- are you saying
> > 'substitute a different' ?
> 
> The usual way to replace 'malloc' is via ELF symbol interposition:
> https://www.airs.com/blog/archives/307

noted -- thank you

-- Russ herrold
___
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/message/GIOFBZ6H233YYWKPK6HRBDB6EFYT3NSM/

Re: Guideline change: glibc malloc as the C/C++/Rust allocator

[Jonathan Wakely]

On 26/07/18 22:34 +0200, Florian Weimer wrote:

http://www.erahm.org/2016/03/24/minimum-alignment-of-allocation-across-platforms/


Oh dear, this is worrying.

I'm adding more places in libstdc++ where the std::lib assumes that
memory obtained from malloc will always be aligned to
alignof(max_align_t). If somebody replaces malloc and it fails to meet
that requirement, undefined behaviour can happen (specifically, types
that require 16-byte alignment might not get it when placed in
containers like std::vector, leading to unaligned accesses).

Replacement mallocs really need to meet malloc's guarantees, not just
pick and choose what they care about. This is a very good reason why
we should be cautious about allowing applications to replace malloc in
Fedora.
___
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/message/IQQY5ZC7VIXUF544JBTILERCTJMETFHC/

Re: [atomic-devel] Starting a Container SIG

[Clement Verna]

On Mon, 30 Jul 2018 at 17:59, Giuseppe Scrivano  wrote:
>
> I'm also interested.
>
> Regards,
> Giuseppe
>
>
> Jeff Ligon  writes:
>
> > I too would like to be a part of this but I’m not sure how much I’d be able 
> > to help.
> >
> > On Fri, Jul 27, 2018 at 1:29 PM Owen Taylor  wrote:
> >
> >  I'm interested in participating with a special interest in Flatpaks - the 
> > other type of Fedora container ;-) - I want to keep things aligned as much 
> > as possible. And also from the perspective of using containers for 
> > development within
> >  Fedora Workstation.
> >
> >  I can contribute a certain familiarity with OCI images, OSBS, the image 
> > registry, etc.
> >
> >  Owen
> >
> >  On Wed, Jul 25, 2018 at 1:09 PM, Clement Verna  
> > wrote:
> >
> >  Greeting all,
> >
> >  The container effort in Fedora has until now been looked after by the
> >  Atomic WG, since this Working Group is now going to focus mostly on
> >  Fedora CoreOS, I propose to create a new container SIG to regroup
> >  people interested in the maintenance of application containers in
> >  Fedora.
> >
> >  This SIG would look after the container guidelines [0], the container
> >  review process [1] and also the release process and tooling.
> >
> >  Please Reply if you're interested with helping out making the
> >  Container story great in Fedora. If there is a good response, I will
> >  create a Container SIG wiki page, and I guess we can ask for
> >  container-devel mailing list for SIG discussions.
> >
> >  Regards,
> >  Clément
> >
> >  [0] - https://fedoraproject.org/wiki/Container:Guidelines
> >  [1] - https://fedoraproject.org/wiki/Container:Review_Process
>

Hi everyone,

Thanks for all the responses and showing such a strong interest :). I
went ahead with creating a wiki page [0] and a project on pagure [1]
where we can start adding items we would to discuss or work on. I will
also request a new mailing list and will keep you updated once it is
available.

Thanks
Clément

[0] - https://fedoraproject.org/wiki/Container_SIG
[1] - https://pagure.io/ContainerSIG/container-sig
___
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/message/ORBLNOECDU2L4GWNDGSQ45KX5BEKNN63/

[Bug 1609256] perl-CPAN-Perl-Releases-3.72 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.72-1.fc27 has been pushed to the Fedora 27 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-2018-aa743e4784

-- 
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/message/RSF4ZKTK3IHOXTWMOL4PMFJRHUKAIIBB/

[Bug 1606925] perl-CPAN-Perl-Releases-3.70 is available

[bugzilla]

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



--- Comment #7 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.72-1.fc27 has been pushed to the Fedora 27 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-2018-aa743e4784

-- 
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/message/NITJSUBLBCQ4XIUHXF22LTD6SATJDPLT/

[Bug 1609221] License 'public domain' is not valid

[bugzilla]

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

Tom "spot" Callaway  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 CC||tcall...@redhat.com
 Resolution|--- |NOTABUG
Last Closed||2018-07-30 13:02:28



--- Comment #1 from Tom "spot" Callaway  ---
Hi Dave,

Fedora uses this list of "Good Licenses":
https://fedoraproject.org/wiki/Licensing:Main#Good_Licenses

You will note that Public Domain is on that list. You are also correct that the
OSI list does not include Public Domain. Why the difference?

Public Domain is not really a license, and the OSI list only lists licenses.
When a work is in the Public Domain, it is because either the Copyright has
expired or the original copyright holder has abandoned their copyright on the
work.

When a work is in the Public Domain, it may be used by anyone in any way that
they wish. (It is actually way more complicated than that, but for our
purposes, this is correct.)

Becuase PD works have no copyright, they cannot have a copyright license. But,
this is not a problem for Fedora (or anyone else), because no license is
necessary to have all of the freedoms covered in the Open Source Definition for
PD works.

This means that while perl-DBIx-Simple is not technically under an Open Source
License, this is only because it is not under _any_ license, because it is not
copyrighted at all, and that state is Open Source compatible.

Hope that helps.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://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/message/N2BQXS5K5SNHVATXP7PYWOWBV45E5YIP/

Re: Guideline change: glibc malloc as the C/C++/Rust allocator

[Jonathan Wakely]

On 26/07/18 12:45 -0400, R P Herrold wrote:

On Thu, 26 Jul 2018, Florian Weimer wrote:


I would like to request a change of the Packaging Guidelines, advising
packagers not to interpose malloc.


The use here of 'interpose' is unclear to me -- are you saying
'substitute a different' ?


The usual way to replace 'malloc' is via ELF symbol interposition:
https://www.airs.com/blog/archives/307

This means some library provides a definition for the symbol 'malloc'
and that gets used instead of the 'malloc' in libc.so

Symbol interposition means the code continues to call 'malloc' and
'free' but those calls get redirected to different implementations.
The alternative is to explicitly use a different allocator with a
different API, e.g. calling 'foo_malloc' and 'foo_free' instead of
'malloc' and 'free'. The latter case doesn't hijack the symbol and
affect any other shared libraries which want to use malloc, because
those other calls will still use the malloc in libc.
___
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/message/3OEXAFLNKX76QV7UAGO2CQBL7F3J3VBZ/

Fedora rawhide compose report: 20180730.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20180729.n.0
NEW: Fedora-Rawhide-20180730.n.0

= SUMMARY =
Added images:0
Dropped images:  0
Added packages:  1
Dropped packages:4
Upgraded packages:   268
Downgraded packages: 0

Size of added packages:  20.33 MiB
Size of dropped packages:12.00 MiB
Size of upgraded packages:   1.92 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: restic-0.9.1-2.fc29
Summary: Fast, secure, efficient backup program
RPMs:restic
Size:20.33 MiB


= DROPPED PACKAGES =
Package: StarCluster-1:0.95.6-11.fc29
Summary: Tool for managing computing clusters hosted on Amazon's EC2
RPMs:StarCluster StarCluster-doc
Size:2.76 MiB

Package: gnotime-2.4.1-14.fc28
Summary: Tracks and reports time spent
RPMs:gnotime
Size:7.97 MiB

Package: python-iptools-0.6.1-15.fc29
Summary: A few useful functions and objects for manipulating IP addresses in 
python
RPMs:python2-iptools python3-iptools
Size:64.93 KiB

Package: python-pygpgme-0.3-28.fc29
Summary: Python module for working with OpenPGP messages
RPMs:python2-pygpgme python3-pygpgme
Size:1.21 MiB


= UPGRADED PACKAGES =
Package:  GMT-5.4.4-1.fc29
Old package:  GMT-5.4.3-2.fc29
Summary:  Generic Mapping Tools
RPMs: GMT GMT-common GMT-devel GMT-doc
Size: 89.24 MiB
Size change:  -554.18 KiB
Changelog:
  * Sun Jul 29 2018 Orion Poplawski  - 5.4.4-1
  - Update to 5.4.4


Package:  ModemManager-1.8.0-3.fc29
Old package:  ModemManager-1.8.0-2.fc29
Summary:  Mobile broadband modem management service
RPMs: ModemManager ModemManager-devel ModemManager-glib 
ModemManager-glib-devel ModemManager-vala
Size: 10.72 MiB
Size change:  -682.41 KiB
Changelog:
  * Sun Jul 29 2018 Rex Dieter  - 1.8.0-3
  - -devel: own %_includedir/ModemManager/
  - %build: --disable-silent-rules
  - use %make_build %make_install


Package:  NFStest-2.1.5-5.fc29
Old package:  NFStest-2.1.5-4.fc28
Summary:  NFS Testing Tool
RPMs: NFStest
Size: 530.92 KiB
Size change:  -1.18 KiB
Changelog:
  * Thu Jul 12 2018 Fedora Release Engineering  - 
2.1.5-5
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild


Package:  PyRTF-0.45-25.fc29
Old package:  PyRTF-0.45-24.fc28
Summary:  Rich Text Format (RTF) Document Generation in Python
RPMs: PyRTF
Size: 46.40 KiB
Size change:  -2.08 KiB
Changelog:
  * Thu Jul 12 2018 Fedora Release Engineering  - 
0.45-25
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild


Package:  R-Rcpp-0.12.18-1.fc29
Old package:  R-Rcpp-0.12.17-2.fc29
Summary:  Seamless R and C++ Integration
RPMs: R-Rcpp R-Rcpp-devel R-Rcpp-examples
Size: 22.96 MiB
Size change:  282.17 KiB
Changelog:
  * Sat Jul 28 2018 Mattias Ellert  - 0.12.18-1
  - Update to 0.12.18


Package:  aide-0.16-7.fc29
Old package:  aide-0.16-6.fc28
Summary:  Intrusion detection environment
RPMs: aide
Size: 978.03 KiB
Size change:  -71.94 KiB
Changelog:
  * Thu Jul 12 2018 Fedora Release Engineering  - 
0.16-7
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild


Package:  alacarte-3.11.91-11.fc29
Old package:  alacarte-3.11.91-10.fc28
Summary:  Menu editor for the GNOME desktop
RPMs: alacarte
Size: 127.80 KiB
Size change:  -6.73 KiB
Changelog:
  * Thu Jul 12 2018 Fedora Release Engineering  - 
3.11.91-11
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild


Package:  alex4-1.0-27.fc29
Old package:  alex4-1.0-25.fc28
Summary:  Alex the Allegator 4 - Platform game
RPMs: alex4
Size: 4.32 MiB
Size change:  -19.42 KiB
Changelog:
  * Thu Jul 12 2018 Fedora Release Engineering  - 
1.0-26
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild

  * Sun Jul 29 2018 Hans de Goede  - 1.0-27
  - Fix FTBFS (rhbz#1603365)


Package:  alphabet-soup-1.1-23.fc29
Old package:  alphabet-soup-1.1-21.fc28
Summary:  Guide your worm through the soup to spell words
RPMs: alphabet-soup
Size: 5.40 MiB
Size change:  -17.66 KiB
Changelog:
  * Thu Jul 12 2018 Fedora Release Engineering  - 
1.1-22
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild

  * Sun Jul 29 2018 Hans de Goede  - 1.1-23
  - Fix FTBFS (rhbz#1603369)


Package:  apt-cacher-ng-3.1-4.fc29
Old package:  apt-cacher-ng-3.1-3.fc29
Summary:  Caching proxy for package files from Debian
RPMs: apt-cacher-ng
Size: 2.29 MiB
Size change:  -100.72 KiB
Changelog:
  * Sun Jul 29 2018 Kenjiro Nakayama  - 3.1-4
  - Fix 1609197 - apt-cacher-ng service is running in wrong permissions


Package:  arandr-0.1.9-5.fc29
Old package:  arandr-0.1.9-4.fc28
Summary:  Simple GTK+ XRandR GUI
RPMs: arandr
Size

Summary/Minutes from today's FESCo Meeting (2018-07-30)

[Petr Šabata]

=
#fedora-meeting-1: FESCO (2018-07-30)
=


Meeting started by contyk at 15:00:01 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2018-07-30/fesco.2018-07-30-15.00.log.html
.



Meeting summary
---
* init process  (contyk, 15:00:12)

* #1946 Updates process is broken  (contyk, 15:01:50)
  * LINK: https://pagure.io/fesco/issue/1946   (contyk, 15:01:58)
  * AGREED: The issues should be filed with QA instead of FESCo (+6, 0,
-0)  (contyk, 15:09:29)

* #1945 Nonresponsive maintainer policy: stalled pull requests  (contyk,
  15:10:42)
  * LINK: https://pagure.io/fesco/issue/1945   (contyk, 15:10:52)
  * AGREED: Let's update the policy; nirik will discuss a method of
highlighting PRs with pingou  (contyk, 15:24:08)

* #1935 [Security] Remove packages which has a consistent bad security
  record from the distribution  (contyk, 15:24:18)
  * LINK: https://pagure.io/fesco/issue/1935   (contyk, 15:24:26)
  * AGREED: Let's discuss this matter on the devel list before
revisiting the topic next week (+6, 0, -0)  (contyk, 15:52:24)

* #1942 F29 System Wide Change: Remove Excessive Linking  (contyk,
  15:52:41)
  * LINK: https://pagure.io/fesco/issue/1942   (contyk, 15:52:47)
  * LINK: https://pagure.io/fesco/issue/1942#comment-523147
(ignatenkobrain, 15:57:24)
  * AGREED: Accept this change for F30, expecting it to be activated
immediately after branching to provide maximum time to shake out
issues or invoke the contingency plan.  (contyk, 16:06:40)

* Next week's chair  (contyk, 16:06:57)
  * ACTION: jsmith will chair next meeting  (contyk, 16:08:02)

* Open Floor  (contyk, 16:08:11)

Meeting ended at 16:13:32 UTC.




Action Items

* jsmith will chair next meeting




Action Items, by person
---
* jsmith
  * jsmith will chair next meeting



People Present (lines said)
---
* contyk (82)
* bowlofeggs (42)
* sgallagh (40)
* nirik (39)
* tyll (19)
* zodbot (19)
* ignatenkobrain (18)
* jsmith (18)
* jsmith_2 (8)
* bcotton (3)
* misc (2)
* nb (1)
* orc_fedo (1)
* zbyszek (0)
* jwb (0)
* maxamillion (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


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://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/message/VBW7WJJLNBPKQ4XPZNOQAQTIC2R7NY5T/

Re: Rust SIG

[Brian (bex) Exelbierd]

On Mon, Jul 30, 2018 at 5:49 PM, Clement Verna 
wrote:

> On Mon, 30 Jul 2018 at 17:45, Brian (bex) Exelbierd 
> wrote:
> >
> >
> >
> > On Mon, Jul 30, 2018 at 2:31 PM, Martin Sehnoutka 
> wrote:
> >>
> >> Do you plan any hackfest during Flock?
> >
> >
> > We are booked out for schedule hacks during Flock, however there is
> usually some space on the edges for impromptu meetings.
> >
> That could happen during the SIG Roundtable tho ?
> https://flock2018.sched.com/event/FjdA/subprojectsig-roundtables


YES!

regards,

bex


>
> > regards,
> >
> > bex
> >
> >>
> >>
> >> On 07/27/2018 04:04 PM, Igor Gnatenko wrote:
> >> > Hello,
> >> >
> >> > it seems to be a week of SIG announcements, so why shouldn't I share
> that
> >> > we also have Rust SIG .
> >> >
> >> > At this point we have over 400 crates packaged, few applications like
> >> > ripgrep, tokei, stratisd and more.
> >> >
> >> > IRC: #fedora-rust
> >> > ML: r...@lists.fedoraproject.org
> >> >
> >> > Feel free to stop by and don't hesitate to ping me ;)
> >> >
> >> > P.S. I'm going to Flock this year, so let me know if you would like
> to meet
> >> > and work on.
> >> >
> >> >
> >> >
> >> > ___
> >> > 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/message/
> 35T2HEEPFBX75Q4AQLEYBSWADBGIC6TW/
> >> >
> >>
> >> --
> >> Martin Sehnoutka | Associate Software Engineer
> >> PGP: 5FD64AF5
> >> UTC+1 (CET)
> >> RED HAT | TRIED. TESTED. TRUSTED.
> >>
> >>
> >> ___
> >> 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/message/
> ENTMTWEOFGYSTVRGI2KVVC6MX5XMY5WJ/
> >>
> >
> >
> >
> > --
> > Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com
> > Fedora Community Action & Impact Coordinator
> > @bexelbie | http://www.winglemeyer.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/message/
> UX623DHXD33AEJPHSUITVOZJZFIN2W5T/
> ___
> 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/message/6C75YCGHGW6K2L65VPQZGM77VROP7PLQ/
>



-- 
Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.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/message/2EVACPC2UVSAI24YY2JVFGB5AOUFZYW2/

Re: Rust SIG

[Clement Verna]

On Mon, 30 Jul 2018 at 17:45, Brian (bex) Exelbierd  wrote:
>
>
>
> On Mon, Jul 30, 2018 at 2:31 PM, Martin Sehnoutka  wrote:
>>
>> Do you plan any hackfest during Flock?
>
>
> We are booked out for schedule hacks during Flock, however there is usually 
> some space on the edges for impromptu meetings.
>
That could happen during the SIG Roundtable tho ?
https://flock2018.sched.com/event/FjdA/subprojectsig-roundtables
> regards,
>
> bex
>
>>
>>
>> On 07/27/2018 04:04 PM, Igor Gnatenko wrote:
>> > Hello,
>> >
>> > it seems to be a week of SIG announcements, so why shouldn't I share that
>> > we also have Rust SIG .
>> >
>> > At this point we have over 400 crates packaged, few applications like
>> > ripgrep, tokei, stratisd and more.
>> >
>> > IRC: #fedora-rust
>> > ML: r...@lists.fedoraproject.org
>> >
>> > Feel free to stop by and don't hesitate to ping me ;)
>> >
>> > P.S. I'm going to Flock this year, so let me know if you would like to meet
>> > and work on.
>> >
>> >
>> >
>> > ___
>> > 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/message/35T2HEEPFBX75Q4AQLEYBSWADBGIC6TW/
>> >
>>
>> --
>> Martin Sehnoutka | Associate Software Engineer
>> PGP: 5FD64AF5
>> UTC+1 (CET)
>> RED HAT | TRIED. TESTED. TRUSTED.
>>
>>
>> ___
>> 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/message/ENTMTWEOFGYSTVRGI2KVVC6MX5XMY5WJ/
>>
>
>
>
> --
> Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com
> Fedora Community Action & Impact Coordinator
> @bexelbie | http://www.winglemeyer.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/message/UX623DHXD33AEJPHSUITVOZJZFIN2W5T/
___
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/message/6C75YCGHGW6K2L65VPQZGM77VROP7PLQ/

Re: What to BuildRequire for libstdc++.so __cxa_demangle?

[Jonathan Wakely]

On 21/07/18 18:52 +0200, Mark Wielaard wrote:

Hi,

The elfutils tools can demangle C++ symbols through the standard
_cxa_demangle interface. The elfutils tools are written in C and
so simply link with -lstdc++ to get access to __cxa_demangle.


You should be able to use -lsupc++ if you only want the demangler.
It's a much smaller library.

___
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/message/QZ6CRWSAZWOTB6IYY5YZYF4RVJKTUPD4/

Re: Rust SIG

[Brian (bex) Exelbierd]

On Mon, Jul 30, 2018 at 2:31 PM, Martin Sehnoutka 
wrote:

> Do you plan any hackfest during Flock?
>

We are booked out for schedule hacks during Flock, however there is usually
some space on the edges for impromptu meetings.

regards,

bex


>
> On 07/27/2018 04:04 PM, Igor Gnatenko wrote:
> > Hello,
> >
> > it seems to be a week of SIG announcements, so why shouldn't I share that
> > we also have Rust SIG .
> >
> > At this point we have over 400 crates packaged, few applications like
> > ripgrep, tokei, stratisd and more.
> >
> > IRC: #fedora-rust
> > ML: r...@lists.fedoraproject.org
> >
> > Feel free to stop by and don't hesitate to ping me ;)
> >
> > P.S. I'm going to Flock this year, so let me know if you would like to
> meet
> > and work on.
> >
> >
> >
> > ___
> > 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/message/
> 35T2HEEPFBX75Q4AQLEYBSWADBGIC6TW/
> >
>
> --
> Martin Sehnoutka | Associate Software Engineer
> PGP: 5FD64AF5
> UTC+1 (CET)
> RED HAT | TRIED. TESTED. TRUSTED.
>
>
> ___
> 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/message/ENTMTWEOFGYSTVRGI2KVVC6MX5XMY5WJ/
>
>


-- 
Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.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/message/UX623DHXD33AEJPHSUITVOZJZFIN2W5T/

Re: Self Introduction: Rob Brown

[Randy Barlow]

On 07/29/2018 08:59 PM, Robert Brown wrote:
> I'm new to fedora 28, and I am interested in participating in the
> package authoring and maintenance. I'm coming from Debian.

Welcome aboard!

You can read about becoming a packager here:

https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
___
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/message/TZSSU2A7IGL242C6XMUO6KHP7EKOYWUO/

Re: Active but unresponsive maintainer: Peter Lemenkov

[Peter Lemenkov]

Hey,
Sorry for the absence - I'm still around.

2018-07-30 15:34 GMT+02:00 Timothée Floure :
>
> Hello,
>
> Peter Lemenkov [0] is an active packager (he submitted a new erlang
> build to bodhi an hour ago) but I was unable to contact him for the last
> two months.
>
> I first "encountered" him when he used his rights as provenpackager to
> merge some PRs on the elixir package, without thoughts for the ongoing
> discussions. He even submitted builds to bodhi but we *never* got any
> message from him. I'm now trying to contact him over RHBZ #1434779 [1]
> but am still unable to get a response.
>
> Does anyone know how to contact him ? Mail, IRC, RHBZ, Bodhi and src.fp.o
> failed.
>
> [0] https://fedoraproject.org/wiki/User:Peter
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1434779
>
> Thanks,
>
> --
> Timothée
>
> ___
> 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/message/B7WRRTWBMJLCMUHK7XJRB7WLVEPTQ4AE/
>



-- 
With best regards, Peter Lemenkov.
___
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/message/SGCNWHJJHY7D2A7YVBRA55VISYAUEKVO/

Self Introduction

[Iñaki Úcar]

Hi everyone,

My name is Iñaki Ucar, and I am based in Madrid, Spain. I have been a
happy Fedora user and advocate for many many years (since Fedora Core
2). Now I would love to start contributing to the project as a package
maintainer, so I am seeking a sponsor.

I am package maintainer for the R Project since 2015, so I am
primarily interested in this ecosystem, which has grown spectacularly
in recent years. To start with, I have submitted my first package,
'simmer', for which I am the upstream maintainer. It is a
discrete-event simulator, and you can find the review request here:
https://bugzilla.redhat.com/show_bug.cgi?id=1609800

For more information, please visit my GitHub profile
https://github.com/Enchufa2, and feel free to drop me an email. My GPG
key can be found in my Keybase profile: https://keybase.io/enchufa2.

Regards,
Iñaki
___
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/message/ABRUHP3OFMIPJN5ZSXAMH43FLXV3NJDH/

Re: Packages which use the BuildRoot: directive

[Panu Matilainen]

On 07/14/2018 12:47 AM, Kevin Fenzi wrote:

On 07/12/2018 07:45 AM, Miro Hrončok wrote:


I second that. When we mass filled PRs with python2 related changes it
was always a Red Hat maintained software, where people were basically
telling us: "no, we won't accept your PR here, we maintain the specfile
somewhere else". It was very unpleasant experience and usually such
maintainers expects us to:

  1) find their canonical spec file location and figure out what special
branch we need to apply the patch to

  2) wait for a new release of their software to happen and specfile
changes be "backported" into Fedora (sometimes took months)

Some maintainers were kinder than others, taking the changes and
applying them in their god-knows-where mainained spec files. Some where
not.

We don't need to make the rule less strict, we need to find a way to
enforce it. The current state (people ignoring this rule) makes
contributing to Fedora even harder than it already is.


I don't see that there is any way to enforce it. I suppose you could try
and have a hook to detect it, but it could well have false positives and
block legit commits.

Perhaps once we no longer use specs we can solve this. ;)


We can always have rpm spit out warnings first and errors later on.

With RHEL 5 and its contemporaries EOL by now, turning Buildroot: into a 
warning seems like an actual possibility. Finally.


- 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/message/EMFZ7PO3JO3SLZ7AJ3XTM6PIWZ4NRKVJ/

Active but unresponsive maintainer: Peter Lemenkov

[Timothée Floure]

Hello,

Peter Lemenkov [0] is an active packager (he submitted a new erlang 
build to bodhi an hour ago) but I was unable to contact him for the last 
two months.

I first "encountered" him when he used his rights as provenpackager to 
merge some PRs on the elixir package, without thoughts for the ongoing 
discussions. He even submitted builds to bodhi but we *never* got any 
message from him. I'm now trying to contact him over RHBZ #1434779 [1] 
but am still unable to get a response.

Does anyone know how to contact him ? Mail, IRC, RHBZ, Bodhi and src.fp.o 
failed.

[0] https://fedoraproject.org/wiki/User:Peter
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1434779

Thanks,

-- 
Timothée


pgp5cbkbou1D5.pgp
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://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/message/B7WRRTWBMJLCMUHK7XJRB7WLVEPTQ4AE/

Re: Packages which needlessly use %defattr

[Igor Gnatenko]

On Mon, Jul 30, 2018 at 11:01 AM Miroslav Suchý  wrote:

> Dne 4.7.2018 v 12:18 Zbigniew Jędrzejewski-Szmek napsal(a):
> > What about just doing a mass specfile update now? I think asking
> > individual maintainers to fix their packages isn't worth their
> > time.
>
> -1
>
> I like the Jason attitude much more. It gives time to discuss it. To find
> false positives. It gives maintainers more
> time to fix it their own way.
> This is in contrast with Igor G. commits, which comes unannounced. In a
> way which - personally - cause me to do more
> work compared to when I do it myself.
>

I have went and send PR[0] which would print all packages which should be
excluded from any automation. Anyone who feels that packagers are "their"
are welcomed to send a patch for this utility.

[0] https://pagure.io/fedora-misc-package-utilities/pull-request/4

>
> Miroslav
> ___
> 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/message/NQY6UH3PVKYTVCATNM6JCC33BS4PSIBP/
>
-- 

-Igor Gnatenko
___
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/message/OU773O3PYB2EYPINNAYZOB7TMX24L4JQ/

Re: Rust SIG

[Martin Sehnoutka]

Do you plan any hackfest during Flock?

On 07/27/2018 04:04 PM, Igor Gnatenko wrote:
> Hello,
> 
> it seems to be a week of SIG announcements, so why shouldn't I share that
> we also have Rust SIG .
> 
> At this point we have over 400 crates packaged, few applications like
> ripgrep, tokei, stratisd and more.
> 
> IRC: #fedora-rust
> ML: r...@lists.fedoraproject.org
> 
> Feel free to stop by and don't hesitate to ping me ;)
> 
> P.S. I'm going to Flock this year, so let me know if you would like to meet
> and work on.
> 
> 
> 
> ___
> 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/message/35T2HEEPFBX75Q4AQLEYBSWADBGIC6TW/
> 

-- 
Martin Sehnoutka | Associate Software Engineer
PGP: 5FD64AF5
UTC+1 (CET)
RED HAT | TRIED. TESTED. TRUSTED.



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/message/ENTMTWEOFGYSTVRGI2KVVC6MX5XMY5WJ/

Re: Golang SIG for Fedora

[Nicolas Mailhot]

Hi,

I'm obviously interested, even though I'm not available all year round

--
Nicolas Mailhot
___
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/message/RILKIETFKR75SFYH7PUTSTDD7NY6H2K3/

Re: koschei build gone?

[Miro Hrončok]

On 30.7.2018 13:54, Mikolaj Izdebski wrote:

I would found it less confusiong if they are kept in the DB but marked
them "stalled -> canceled"? For example here at least one architecture
failed and even the fact that the build was stalled is interesting.


Agreed. Can you file upstream issue at [1] so that we can track it?


https://github.com/msimacek/koschei/issues/266

--
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://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/message/6RQAJAVW77DDHKK6CD73F3DQPTPPBDKF/

Re: koschei build gone?

[Mikolaj Izdebski]

On 07/30/2018 01:49 PM, Miro Hrončok wrote:
> On 30.7.2018 12:42, Mikolaj Izdebski wrote:
>> On 07/30/2018 11:19 AM, Miro Hrončok wrote:
>>> Hi,
>>>
>>> I've filled this bugzilla: [0] and I clearly remember seeing a failed
>>> build in koschei - I've even linked it in the BZ [1].
>>>
>>> Yet the URL now returns 404.
>>>
>>> Last build in koschei for python3 is 3 days older than the bugreport.
>>>
>>> What happens? Are certain builds deleted for various reasons? Or are we
>>> loosing some data by accident?
>>
>> The corresponding task is
>> https://koji.fedoraproject.org/koji/taskinfo?taskID=28608653
>>
>> This task was cancelled by Koschei itself and removed from database
>> because it was running longer than 48 hours. Koschei does this to
>> prevent stalled builds from blocking build queue and wasting resources.
> 
> I would found it less confusiong if they are kept in the DB but marked
> them "stalled -> canceled"? For example here at least one architecture
> failed and even the fact that the build was stalled is interesting.

Agreed. Can you file upstream issue at [1] so that we can track it?

[1] https://github.com/msimacek/koschei/issues

-- 
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
___
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/message/2T4BA5RHR3VIMSCSHZP4HEV6DVJJ252B/

Re: koschei build gone?

[Miro Hrončok]

On 30.7.2018 12:42, Mikolaj Izdebski wrote:

On 07/30/2018 11:19 AM, Miro Hrončok wrote:

Hi,

I've filled this bugzilla: [0] and I clearly remember seeing a failed
build in koschei - I've even linked it in the BZ [1].

Yet the URL now returns 404.

Last build in koschei for python3 is 3 days older than the bugreport.

What happens? Are certain builds deleted for various reasons? Or are we
loosing some data by accident?


The corresponding task is
https://koji.fedoraproject.org/koji/taskinfo?taskID=28608653

This task was cancelled by Koschei itself and removed from database
because it was running longer than 48 hours. Koschei does this to
prevent stalled builds from blocking build queue and wasting resources.


I would found it less confusiong if they are kept in the DB but marked 
them "stalled -> canceled"? For example here at least one architecture 
failed and even the fact that the build was stalled is interesting.


--
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://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/message/XMU2RFBDAHWPKOVIIQRHGLUYWK2L5IJK/

Re: koschei build gone?

[Mikolaj Izdebski]

On 07/30/2018 11:19 AM, Miro Hrončok wrote:
> Hi,
> 
> I've filled this bugzilla: [0] and I clearly remember seeing a failed
> build in koschei - I've even linked it in the BZ [1].
> 
> Yet the URL now returns 404.
> 
> Last build in koschei for python3 is 3 days older than the bugreport.
> 
> What happens? Are certain builds deleted for various reasons? Or are we
> loosing some data by accident?

The corresponding task is
https://koji.fedoraproject.org/koji/taskinfo?taskID=28608653

This task was cancelled by Koschei itself and removed from database
because it was running longer than 48 hours. Koschei does this to
prevent stalled builds from blocking build queue and wasting resources.

Relevant journal entries:

Jul 28 01:49:08 koschei-backend01.phx2.fedoraproject.org
koschei-polling[4264]: Polling task 28608653 (python3):
task_info={'weight': 0.2, 'parent': None, 'channel_id': 1, 'start_time':
'2018-07-26 01:41:38.260734', 'start_ts': 1532569298.26073, 'waiting':
True, 'awaited': None, 'label': None, 'priority': 50, 'completion_time':
None, 'state': 1, 'create_time': '2018-07-26 01:41:35.740322',
'create_ts': 1532569295.74032, 'owner': 3199, 'host_id': 325, 'method':
'build', 'completion_ts': None, 'arch': 'noarch', 'id': 28608653}

Jul 28 01:49:08 koschei-backend01.phx2.fedoraproject.org
koschei-polling[4264]: Canceling build Build(id=5052601,
package=python3, collection=f29, state=running, task_id=28608653)

Jul 28 01:49:10 koschei-backend01.phx2.fedoraproject.org
koschei-polling[4264]: Deleting build Build(id=5052601, package=python3,
collection=f29, state=running, task_id=28608653) because it was canceled


> 
> 
> [0] https://bugzilla.redhat.com/show_bug.cgi?id=1609291
> [1] https://apps.fedoraproject.org/koschei/build/5052601

-- 
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
___
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/message/ZPGVMSZ6GCIUGF7DOOLAA23JBW7XIKI5/

koschei build gone?

[Miro Hrončok]

Hi,

I've filled this bugzilla: [0] and I clearly remember seeing a failed 
build in koschei - I've even linked it in the BZ [1].


Yet the URL now returns 404.

Last build in koschei for python3 is 3 days older than the bugreport.

What happens? Are certain builds deleted for various reasons? Or are we 
loosing some data by accident?



[0] https://bugzilla.redhat.com/show_bug.cgi?id=1609291
[1] https://apps.fedoraproject.org/koschei/build/5052601
--
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://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/message/VSYG7COVRXPPZJOCUM7ODR32HQXOYNBB/

Re: Packages which needlessly use %defattr

[Miroslav Suchý]

Dne 4.7.2018 v 12:18 Zbigniew Jędrzejewski-Szmek napsal(a):
> What about just doing a mass specfile update now? I think asking
> individual maintainers to fix their packages isn't worth their
> time.

-1

I like the Jason attitude much more. It gives time to discuss it. To find false 
positives. It gives maintainers more
time to fix it their own way.
This is in contrast with Igor G. commits, which comes unannounced. In a way 
which - personally - cause me to do more
work compared to when I do it myself.

Miroslav
___
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/message/NQY6UH3PVKYTVCATNM6JCC33BS4PSIBP/

Re: Auto-filing of FTBFS bugs gone wild

[Hans de Goede]

Hi,

On 19-07-18 17:42, Igor Gnatenko wrote:

On Thu, Jul 19, 2018 at 5:33 PM Hans de Goede mailto:hdego...@redhat.com>> wrote:

Hi All,

I've just got 20 bugs auto-filed against packages which I co-maintain
and that is just for packages starting with the letter 'a'.

A quick check shows that these are all caused by a missing
BuildRequires on gcc / g++ related to:

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

I'm not sure if this means that the FTBFS script has been run before
all the automatic fixing which was planned for this was in place;
or if this means that the automatic fixing missed many many
packages, but either way something needs to happen here, the amount
of work now being pushed onto packagers caused by:

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

Is unacceptable IMHO.

If the FTBFS script has ran too early, all the FTBFS bugs need to be
closed and the FTBFS script has to be run again later.

If the automatic BuildRequires fixing script missed all these, then
I suggest that:

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

Gets reverted for now and we again close all the FTBFS bugs and
rerun the script for them after doing a fresh build with the
buildroot restored as it was.


No one promised that I'm going to fix 100% of packages, I've fixed around 2k 
packages. What my regex couldn't catch -- please send me list of packages, I 
will analyze them and try to fix as much as possible.


I was on vacation last week and coming back now I see that you've
fixed most of these, many thanks for fixing these.

Regards,

Hans

___
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/message/UQ33OLAVSNGHJUL74FZROW4VXICTYVBW/

[EPEL-devel] Re: libbibutils 6.6 update with soname bump in epel7

[Tuomo Soini]

On Sat, 28 Jul 2018 12:29:56 +0900
Jens-Ulrik Petersen  wrote:

> Vasiliy, I have decoupled ghc-hs-bibutils from bibutils in epel7 now
> too, so you shouldn't need to worry about it anymore.

Please, add ghc-rpm-macros to update too. That's build dependency of
ghc-hs-bibutils. And while package is now in koji it's not in any
update bodhi knows about.

-- 
Tuomo Soini 
Foobar Linux services
+358 40 5240030
Foobar Oy 
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org/message/DGQXIYBY5EIR6EP7324M6ZBKJ3PY5P2U/

[Bug 1609587] perl-App-cpm-0.977 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-App-cpm-0.977-1.fc29
 Resolution|--- |RAWHIDE
Last Closed||2018-07-30 03:00:02



-- 
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/message/EFFNWWPKC2FXGMSFYC66ZFW75UGZMQAE/

[Bug 1606926] perl-Alien-pkgconf-0.14 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-Alien-pkgconf-0.14-1.f
   ||c29
 Resolution|--- |RAWHIDE
Last Closed||2018-07-30 02:55:37



--- Comment #2 from Petr Pisar  ---
An enhancement release suitable for Fedora ≥ 29.

-- 
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/message/NZSIT44BK6PWHFD2T4WMHRU2U7TDAY7J/

[Bug 1609443] perl-Net-Netmask-1.9104 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-Net-Netmask-1.9104-1.f
   ||c29
 Resolution|--- |RAWHIDE
Last Closed||2018-07-30 02:43:46



-- 
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/message/INVLR6H27VK5DTBTWFS754XEL66VEESE/

Re: dokuwiki packagers unresponsive

[Matthias Runge]

On Fri, Jul 27, 2018 at 02:51:25AM +0100, Sérgio Basto wrote:
> On Thu, 2018-07-26 at 21:43 -0400, Solomon Peachy wrote:
> > On Thu, Jul 26, 2018 at 09:09:25PM +0200, Peter 'Pessoft' Kolínek
> > wrote:
> > > I'd like to fix some issues (including security problems) which are
> > > for
> > > a long time present in dokuwiki package. Maintainers of the
> > > dokuwiki
> > > however seem unresponsive. 
> > 
> > It's worth stating that "some issues" is a euphamism for "the 
> > package has been fundamentally broken since Fedora 24."
> > 
> >   https://bugzilla.redhat.com/show_bug.cgi?id=1372948
> 
> 
> The main admin (togdog) usually give permission to commit if you ask
> him , at least did to me . 

Right, I can second that. It worked for me as well.

With pagure in place, you could also submit pull requests to improve
the situation.

Matthias
-- 
Matthias Runge 
___
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/message/2ROT7CN7RZ2BEIVBABZJZKR6ZRIVOUEX/

[Bug 1606925] perl-CPAN-Perl-Releases-3.70 is available

[bugzilla]

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



--- Comment #6 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.72-1.fc27 has been submitted as an update to Fedora
27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-aa743e4784

-- 
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/message/2VU57KOFE44NBRCMYIE5T5B4C4AVXIZV/

[Bug 1609256] perl-CPAN-Perl-Releases-3.72 is available

[bugzilla]

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



--- Comment #2 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.72-1.fc27 has been submitted as an update to Fedora
27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-aa743e4784

-- 
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/message/ZQFPOA4CNFFQVF2OX4VNNO6W3YADEXMA/

[Bug 1609256] perl-CPAN-Perl-Releases-3.72 is available

[bugzilla]

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



--- Comment #1 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.72-1.fc28 has been submitted as an update to Fedora
28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-29e957c41c

-- 
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/message/LBSHWHSFGZG4PE6NFDQY3DMZHVKH57H7/

[Bug 1606925] perl-CPAN-Perl-Releases-3.70 is available

[bugzilla]

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



--- Comment #5 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.72-1.fc28 has been submitted as an update to Fedora
28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-29e957c41c

-- 
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/message/KZPY5C6PKT7V3RWQYCSAP7Y5Q6ZVEF3V/

[Bug 1609256] perl-CPAN-Perl-Releases-3.72 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |MODIFIED
   Fixed In Version||perl-CPAN-Perl-Releases-3.7
   ||2-1.fc29



-- 
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/message/H6JSTONKWRJB3EW34TJJSFK6PQVWOXPI/

[Test-Announce] Proposal to CANCEL: 2018-07-30 Fedora QA Meeting

[Adam Williamson]

Hi folks! I'm proposing we cancel the QA meeting tomorrow (today?).
I don't see anything urgent to discuss, so let's take the time off.

If you're aware of anything important we have to discuss this week,
please do reply to this mail and we can go ahead and run the meeting.
Thanks!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org/message/PGRAYK4PQSX6KOBJBFSGEF7B2E4ZKO2W/
___
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/message/PGRAYK4PQSX6KOBJBFSGEF7B2E4ZKO2W/