[EPEL-devel] Re: EPEL 8 Beta/Alpha?

[Thomas Stephen Lee]

Hi All,

https://www.redhat.com/en/enterprise-linux-8

RHEL 8 is released.

thanks

--

Lee

On Mon, Feb 18, 2019 at 10:43 AM Thomas Stephen Lee 
wrote:

> Hi All,
>
> Probably you already know this.
>
> RHEL 8 is based on Fedora 28
>
> https://www.redhat.com/en/blog/road-red-hat-enterprise-linux-8-beta
>
> thanks
>
> --
>
> Lee
>
> On Wed, Nov 28, 2018 at 7:47 PM Paul Howarth  wrote:
>
>> On Wed, 28 Nov 2018 07:01:04 -0600
>> Richard Shaw  wrote:
>>
>> > On Wed, Nov 28, 2018 at 5:29 AM Paul Howarth 
>> > wrote:
>> >
>> > > On Wed, 28 Nov 2018 10:53:58 +0530
>> > >
>> > > I seem to remember that for EL-7 we generally just branched the f19
>> > > packages for epel7, rebuilt and that was pretty much it.
>> > >
>> >
>> > I thought it was more of an "opt-in" situation, that packages that
>> > had a EL -1 branch didn't automatically get an EL new branch?
>> >
>> > I would definitely like the opportunity to do some major version
>> > upgrades of some of the packages I maintain.
>>
>> It was mostly opt-in as I recall it, but some packages got EPEL
>> branches for the first time as they were needed as dependencies. Anyone
>> packaging for EPEL-8 should of course be free to choose whichever
>> version of their package is best suited to it; I think f19 was the
>> latest at the time of the EL7 beta release when a lot of stuff got
>> built.
>>
>> Paul.
>> ___
>> 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
>>
>
___
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

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

[updates]

The following Fedora EPEL 6 Security updates need testing:
 Age  URL
  14  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-009f5f140b   
php-horde-horde-5.2.21-1.el6
  14  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-b9ea566899   
php-horde-turba-4.2.24-1.el6
  14  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-e406623fec   
bird-1.6.6-1.el6
   7  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-dc3342b950   
drupal7-7.66-1.el6


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

fuse3-3.4.2-7.el6
inxi-3.0.34-1.el6
nginx-1.10.3-1.el6

Details about builds:



 fuse3-3.4.2-7.el6 (FEDORA-EPEL-2019-c3bb94f94c)
 File System in Userspace (FUSE) v3 utilities

Update Information:

Build fuse3 for el6

References:

  [ 1 ] Bug #1696454 - Please include fuse3 and fuse3-libs in EPEL
https://bugzilla.redhat.com/show_bug.cgi?id=1696454




 inxi-3.0.34-1.el6 (FEDORA-EPEL-2019-23a6335af0)
 A full featured system information script

Update Information:

Update to 3.0.34.

ChangeLog:

* Mon May  6 2019 Vasiliy N. Glazov  - 3.0.34-1
- Update to 3.0.34




 nginx-1.10.3-1.el6 (FEDORA-EPEL-2019-2343dfaaf5)
 A high performance web server and reverse proxy server

Update Information:

Update to upstream release 1.10.3

ChangeLog:

* Tue May  7 2019 Jamie Nguyen  - 1.10.3-1
- Update to upstream release 1.10.3


___
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

[Bug 1703790] perl-YAML-1.28 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-YAML-1.28-1.fc31   |perl-YAML-1.28-1.fc31
   |perl-YAML-1.28-1.fc30   |perl-YAML-1.28-1.fc30
   ||perl-YAML-1.28-1.fc29



--- Comment #6 from Fedora Update System  ---
perl-YAML-1.28-1.fc29 has been pushed to the Fedora 29 stable repository. If
problems still persist, please make note of it in this bug report.

-- 
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 1703675] perl-FFI-CheckLib-0.24 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-FFI-CheckLib-0.24-1.fc |perl-FFI-CheckLib-0.24-1.fc
   |31  |31
   |perl-FFI-CheckLib-0.24-1.fc |perl-FFI-CheckLib-0.24-1.fc
   |30  |30
   ||perl-FFI-CheckLib-0.24-1.fc
   ||29



--- Comment #9 from Fedora Update System  ---
perl-FFI-CheckLib-0.24-1.fc29 has been pushed to the Fedora 29 stable
repository. If problems still persist, please make note of it in this bug
report.

-- 
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 1664030] perl-Class-DBI-Plugin-Type-0.02-35.fc30 FTBFS: tests fail with perl-DBD-SQLite-1.62-1.fc30

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Class-DBI-Plugin-Type- |perl-Class-DBI-Plugin-Type-
   |0.02-37.fc31|0.02-37.fc31
   |perl-Class-DBI-Plugin-Type- |perl-Class-DBI-Plugin-Type-
   |0.02-37.fc30|0.02-37.fc30
   ||perl-Class-DBI-Plugin-Type-
   ||0.02-36.fc29



--- Comment #9 from Fedora Update System  ---
perl-Class-DBI-Plugin-Type-0.02-36.fc29 has been pushed to the Fedora 29 stable
repository. If problems still persist, please make note of it in this bug
report.

-- 
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 1705666] please add perl-DateTime-Format-SQLite to epel7

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #5 from Fedora Update System  ---
perl-DateTime-Format-SQLite-0.11-22.el7 has been pushed to the Fedora EPEL 7
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-EPEL-2019-56a4330c5e

-- 
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 1703675] perl-FFI-CheckLib-0.24 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-FFI-CheckLib-0.24-1.fc |perl-FFI-CheckLib-0.24-1.fc
   |31  |31
   ||perl-FFI-CheckLib-0.24-1.fc
   ||30
 Resolution|--- |ERRATA
Last Closed||2019-05-08 01:12:07



--- Comment #8 from Fedora Update System  ---
perl-FFI-CheckLib-0.24-1.fc30 has been pushed to the Fedora 30 stable
repository. If problems still persist, please make note of it in this bug
report.

-- 
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 1664030] perl-Class-DBI-Plugin-Type-0.02-35.fc30 FTBFS: tests fail with perl-DBD-SQLite-1.62-1.fc30

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-Class-DBI-Plugin-Type- |perl-Class-DBI-Plugin-Type-
   |0.02-37.fc31|0.02-37.fc31
   ||perl-Class-DBI-Plugin-Type-
   ||0.02-37.fc30
 Resolution|--- |ERRATA
Last Closed||2019-05-08 01:12:05



--- Comment #8 from Fedora Update System  ---
perl-Class-DBI-Plugin-Type-0.02-37.fc30 has been pushed to the Fedora 30 stable
repository. If problems still persist, please make note of it in this bug
report.

-- 
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 1703498] perl-Test2-Suite-0.000120 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-Test2-Suite-0.000120-1 |perl-Test2-Suite-0.000120-1
   |.fc31   |.fc31
   ||perl-Test2-Suite-0.000120-1
   ||.fc30
 Resolution|--- |ERRATA
Last Closed||2019-05-08 01:12:04



--- Comment #4 from Fedora Update System  ---
perl-Test2-Suite-0.000120-1.fc30 has been pushed to the Fedora 30 stable
repository. If problems still persist, please make note of it in this bug
report.

-- 
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 1703790] perl-YAML-1.28 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-YAML-1.28-1.fc31   |perl-YAML-1.28-1.fc31
   ||perl-YAML-1.28-1.fc30
 Resolution|--- |ERRATA
Last Closed||2019-05-08 01:11:59



--- Comment #5 from Fedora Update System  ---
perl-YAML-1.28-1.fc30 has been pushed to the Fedora 30 stable repository. If
problems still persist, please make note of it in this bug report.

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

[389-devel] Re: Groups are not accessible by filter

[William Brown]

> On 7 May 2019, at 22:35, Ludwig Krispenz  wrote:
> 
> 
> On 05/07/2019 02:08 PM, William Brown wrote:
>> 
>>> On 7 May 2019, at 22:03, Viktor Ashirov  wrote:
>>> 
>>> On Mon, Apr 29, 2019 at 6:48 AM William Brown  wrote:
 
 
> On 29 Apr 2019, at 12:33, Anuj Borah  wrote:
> 
> @William Brown
> 
> Thanks for the tip!
> 
> (Pdb) len(topo.standalone.search_s(DEFAULT_SUFFIX, 
> ldap.SCOPE_SUBTREE,"testUserAccountControl:1.2.840.113556.1.4.803:=8388608",
>  ['attrlist=cn:sn:uid:testUserAccountControl']))
> 6
> (Pdb) len(Accounts(topo.standalone, 
> DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608)"))
> 6
> 
> We cant not mix up ['attrlist=cn:sn:uid:testUserAccountControl'] with 
> filter , like we do with search_s .
> 
> (Pdb) len(Accounts(topo.standalone, 
> DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608)",
>  ['attrlist=cn:sn:uid:testUserAccountControl']))
> *** TypeError: filter() takes 2 positional arguments but 3 were given
> (Pdb) len(Accounts(topo.standalone, 
> DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608),
>  ['attrlist=cn:sn:uid:testUserAccountControl']"))
> *** ldap.FILTER_ERROR: {'desc': 'Bad search filter', 'errno': 2, 'info': 
> 'No such file or directory'}
> 
> Again i have to use "re" module for the same .
> 
> 
 What are you trying to achieve?
>>> Test case is very simple: search for entries using different filters
>>> and request specific attributes.
>> But those entries have types and classes - you know what you are expecting 
>> to get.
>> 
>>> The problem that Anuj is facing is that filter() doesn't support
>>> attrlist. Moreover, _unsafe_raw_entry() doesn't return *all*
>>> attributes, it omits operational attributes (like nsRoleDN).
>>> IMHO, search_s is good enough here.
>> If you want to avoid any of the "magic" use DSLdapObjects(instance).filter() 
>> then because that doesn't prescribe any classes. But it does take a lot of 
>> the safety out of the library, and I still think that there is something 
>> missing in the approach here.
> but we are testing ldap clients and need to be able to do anything the 
> protocol allows, not only what you declare safe

And there are still ways to do that, you can use search_s if you mark that you 
are aware it's not safe. And in many cases, the tests being written don't need 
that kind of access, which is why I keep asking what he's trying to achieve. 

Half the issue isn't the safety, it's the huge amount of techdebt inside of 
DirSrv and Entry that are problems to the framework, and violate good python 
design.




>> 
>> 
 
 Sincerely,
 
 William Brown
 
 Senior Software Engineer, 389 Directory Server
 SUSE Labs
 ___
 389-devel mailing list -- 389-devel@lists.fedoraproject.org
 To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
 Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
 List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
 List Archives: 
 https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
>>> 
>>> 
>>> --
>>> Viktor
>>> ___
>>> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
>>> To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
>>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>>> List Archives: 
>>> https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
>> —
>> Sincerely,
>> 
>> William Brown
>> 
>> Senior Software Engineer, 389 Directory Server
>> SUSE Labs
>> ___
>> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
>> To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
> 
> -- 
> Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
> Commercial register: Amtsgericht Muenchen, HRB 153243,
> Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, 
> Eric Shander
> ___
> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
> To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> 

[389-devel] Re: Groups are not accessible by filter

[William Brown]

> On 7 May 2019, at 23:56, Viktor Ashirov  wrote:
> 
> On Tue, May 7, 2019 at 2:09 PM William Brown  wrote:
>> 
>> 
>> 
>>> On 7 May 2019, at 22:03, Viktor Ashirov  wrote:
>>> 
>>> On Mon, Apr 29, 2019 at 6:48 AM William Brown  wrote:
 
 
 
> On 29 Apr 2019, at 12:33, Anuj Borah  wrote:
> 
> @William Brown
> 
> Thanks for the tip!
> 
> (Pdb) len(topo.standalone.search_s(DEFAULT_SUFFIX, 
> ldap.SCOPE_SUBTREE,"testUserAccountControl:1.2.840.113556.1.4.803:=8388608",
>  ['attrlist=cn:sn:uid:testUserAccountControl']))
> 6
> (Pdb) len(Accounts(topo.standalone, 
> DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608)"))
> 6
> 
> We cant not mix up ['attrlist=cn:sn:uid:testUserAccountControl'] with 
> filter , like we do with search_s .
> 
> (Pdb) len(Accounts(topo.standalone, 
> DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608)",
>  ['attrlist=cn:sn:uid:testUserAccountControl']))
> *** TypeError: filter() takes 2 positional arguments but 3 were given
> (Pdb) len(Accounts(topo.standalone, 
> DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608),
>  ['attrlist=cn:sn:uid:testUserAccountControl']"))
> *** ldap.FILTER_ERROR: {'desc': 'Bad search filter', 'errno': 2, 'info': 
> 'No such file or directory'}
> 
> Again i have to use "re" module for the same .
> 
> 
 
 What are you trying to achieve?
>>> Test case is very simple: search for entries using different filters
>>> and request specific attributes.
>> 
>> But those entries have types and classes - you know what you are expecting 
>> to get.
>> 
>>> The problem that Anuj is facing is that filter() doesn't support
>>> attrlist. Moreover, _unsafe_raw_entry() doesn't return *all*
>>> attributes, it omits operational attributes (like nsRoleDN).
>>> IMHO, search_s is good enough here.
>> 
>> If you want to avoid any of the "magic" use DSLdapObjects(instance).filter() 
>> then because that doesn't prescribe any classes. But it does take a lot of 
>> the safety out of the library, and I still think that there is something 
>> missing in the approach here.
> I have a problem with DSLdapObjects(instance).filter() is that it
> takes way more effort to write *test* code with a very little benefit.
> Consider this example: I need to fetch all regular attributes,
> operational attributes and entry state information from the server.
> With DSLdapObjects I had to do the following:
> (Pdb) _ = Accounts(topo.standalone, DEFAULT_SUFFIX)
> (Pdb) _._filterattrs=["*", "+", "nscpEntryWSI"]
> (Pdb) _.filter(F10)[0].get_all_attrs()
> 
> get_all_attrs() doesn't return nscpEntryWSI at all, and, as a bonus,
> lowercases some of the attribute names.
> 
> vs.
> 
> (Pdb) topo.standalone.search_s(DEFAULT_SUFFIX, ldap.SCOPE_SUBTREE,
> attrlist=["*", "+", "nscpEntryWSI"])
> 
> Safety here is not a main concern, since it's a test code. In tests we
> need more than often to have a raw LDAP access without too much
> abstractions. Main concern is precision and certainty.
> Abstractions are good when they increase clarity and make things
> certain. In case of the very common search pattern above, DSLdapObject
> doesn't work really well. For me at least.

And that's fine, search_s can still work - the issue here is that Anuj has not 
articulated what he's trying to achieve, and has previously misunderstood the 
api :(. So honestly, I need to see this in a test case, with proper code 
structures to comment more.

The main reason to avoid search_s is that today in DirSrv it uses a really 
horrid hack to get Entry, which I have wanted to purge with fire for a long 
time - so the main reason to minimise it's use is to limit damage when I do 
eventually change that api.


>> 
>> 
 
 
 Sincerely,
 
 William Brown
 
 Senior Software Engineer, 389 Directory Server
 SUSE Labs
 ___
 389-devel mailing list -- 389-devel@lists.fedoraproject.org
 To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
 Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
 List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
 List Archives: 
 https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
>>> 
>>> 
>>> 
>>> --
>>> Viktor
>>> ___
>>> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
>>> To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
>>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>>> List Archives: 
>>> https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
>> 
>> —
>> Sincerely,
>> 
>> William Brown
>> 
>> Senior Software 

Re: Attempting to contact unresponsive maintainers: dkaspar flaper87

[Nathan Scott]

Hi Kevin,

On Wed, May 8, 2019 at 7:18 AM Kevin Fenzi  wrote:
> [...]
> flaper87:
>
> "redis": "flaper87",

I've been doing the Redis Fedora and EPEL updates for a few years now,
I'm happy to take this one on.

cheers.

--
Nathan
___
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: Where are armv7hl, i686 and ppc64le Container tar.xz files?

[Kevin Fenzi]

On 5/6/19 11:57 AM, Jun Aruga wrote:
> Yes, Kevin. Thank you for the info.
> What I do not understand is below DockerHub has Feodra 30 ppc64le,
> Fedora 29 armhfp that Fedora Project did not release.
> 
> https://hub.docker.com/r/ppc64le/fedora/
>   Fedora 29, 30
> https://hub.docker.com/r/arm32v7/fedora/
>   Fedora 29 (not 30)

updating images in docker hub requires a human to file a pull request
with the exact image that needs to be pulled. It's not automated at all.
For a long time also, docker hub didn't do anything except x86_64.

So, likely we haven't had a armv7 fedora 30 compose recently, and so no
one has updated it. The container sig would be the ones to ask here.

> Kevin, I have a question.
> 
> https://pagure.io/pungi-fedora/blob/f30/f/fedora-final.conf#_322
>> > 'arches': ['armhfp', 'aarch64', 'ppc64le', 's390x', 'x86_64'],
> 
> From above setting for Container, ideally those 5 archs should be
> released on URL [a] or [b]?

Yes. :)

The primary arches will be at a, the alternative arches will be at b.

> Where is ppc64le's image?

Thats an alternative arch, so it would be at b (fedora-secondary).
(If it composed with the final release)

> 
> "'distro': 'Fedora-22', " in
> https://pagure.io/pungi-fedora/blob/f30/f/fedora-final.conf#_320 is
> right setting?

Yes. This is a koji setting thats passed to 'oz' for the images. Before
Fedora 22 we used yum, after Fedora 22 dnf was used.

> a. https://dl.fedoraproject.org/pub/fedora/linux/releases/30/Container/
>   aarch64, x86_64
> b. https://dl.fedoraproject.org/pub/fedora-secondary/releases/30/Container/
>   s390x
> c. https://dl.fedoraproject.org/pub/fedora/linux/development/30/Container/
>   aarch64, armhfp, x86_64


c is for when a release is in development (ie, before final release).

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

Attempting to contact unresponsive maintainers: dkaspar flaper87

[Kevin Fenzi]

I'd like to appologize for the delay in this email.

The notices I get were being filtered and I didn't realize I wasn't
seeing them for a while. ;(


We've been told that the email addresses for these package maintainers
are no longer valid. I'm starting the unresponsive maintainer policy to
find out if they are still interested in maintaining their packages (and
if so, have them update their email addresses in FAS).

If they're not interested in maintaining or we can't locate them in 1
week, I'll have FESCo orphan the packages so that others can take them
over.

If you have a way to contact these maintainers, please let them know
that we'd appreciate knowing what to do with their packages. Thanks!

dkaspar:

"dstat": "dkaspar",
"initscripts": "dkaspar",
"mtools": "dkaspar",
"tcsh": "dkaspar",

flaper87:

"redis": "flaper87",


Thanks,

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: On GCL and libselinux

[Dominik 'Rathann' Mierzejewski]

On Monday, 06 May 2019 at 02:49, Jerry James wrote:
> Awhile back, I mentioned that GCL was building in mock on my local
> machine, but was segfaulting on the koji builders.  By dint of much
> experimentation, I now know what is going on.  For the enlightenment
> of anybody who cares:
[snip excellent technical detective work]

That was brilliant. Thanks for writing that up.

I bet it would get a significant audience as an article on LWN. Might be
worth a try.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
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 1707588] New: perl-Test2-Suite-0.000121 is available

[bugzilla]

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

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



Latest upstream release: 0.000121
Current version/release in rawhide: 0.000120-1.fc31
URL: http://search.cpan.org/dist/Test2-Suite/

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

-- 
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: Package with open and closed dual license

[Jason L Tibbitts III]

> "AT" == Andrew Toskin  writes:

AT> I'm looking specifically into VeraCrypt, the open-source fork from
AT> TrueCrypt.

Has the situation which has kept VeraCrypt out of Fedora previously been
changed?

See this, for example:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/XF5GFHQ6FF7GTDDOYFFU4EZICOWMQW7Z/#TIRNFOQXXRM4IBC4OA3FJCDJIAFC2FGN

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

Package with open and closed dual license

[Andrew Toskin]

Sorry if this has already been discussed, but I couldn't find a thread dealing 
with this exact situation... I'm considering a new package that is 
dual-licensed under a free and a nonfree license.

The Fedora Licensing Guidelines say:

  > If code is multiple licensed, and at least one of the licenses is approved 
for Fedora, that code can be included in Fedora under the approved license(s) 
(but only under the terms of the approved license(s)).

In particular, does that mean the spec `License:` tag should only list the 
Fedora-approved license? Or should I still list both? Or does this mean the 
package is not allowed in Fedora?

I'm looking specifically into VeraCrypt, the open-source fork from TrueCrypt. 
It's released under the Apache License v2.0 (free), but for some reason also 
maintains the old TrueCrypt 3.0 freeware license as an option...

https://www.veracrypt.fr/code/VeraCrypt/tree/License.txt

Thanks,
~ Andrew (FAS: terrycloth)
___
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

[EPEL-devel] [Fedocal] Reminder meeting : EPEL Steering Co

[smooge]

Dear all,

You are kindly invited to the meeting:
   EPEL Steering Co on 2019-05-08 from 18:00:00 to 19:00:00 GMT
   At freenode@fedora-meeting

The meeting will be about:
This is the weekly EPEL Steering Committee Meeting. Agenda is in the 
https://infinote.fedoraproject.org/cgit/infinote/tree/epel-meeting-next 


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

___
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

Re: Enable dmarc mitigations

[Stephen J. Turnbull]

Matthew Miller writes:
 > On Sun, May 05, 2019 at 12:43:02PM -0700, stan via devel wrote:
 > > To each their own, of course, but there was a long discussion of
 > > discourse here a while ago.  I tried it out, but it was like a bad
 > > version of a mailing list.  It sent me a mail informing me that there
 > > were messages to read.  Then I had to go there and read the messages on
 > > the web, using their interface.  
 > 
 > That's definitely the primary intended mode of interaction,

To be fair, that's *one* intended mode of interaction, when Discourse
is used as an adjunct to a blog platform.  As a substitute for "devel"
or "users", I would expect that it would sit there in a window (or
windows) of your browser pretty much always visible, or on the next
desktop, and there'd be a "bomb crater" emoji instead of the switch for
turning notifications on.

I could see using it in a "users" style forum, where I'd use it like
Twitter: wander in, see if there was anything interesting, if there
were a post or two with insufficient answers I'd provide what help I
could, and then come back next week and do the same.  I wouldn't want
to use it in a "devel" forum, but that's likely *mostly* because I
have a complex set of customizations for dealing with my devel forums
in my mail client, and I'm pretty sure they won't be replicated in any
web forum.  I would probably eventually come up with alternatives and
workarounds, but for many months I would be in A Very Bad Bad Mood,
and Extremely Unpleasant to Be Around. :-)

This should not be considered advocacy one way or the other vis-a-vis
Fedora channels -- I'm here more or less by accident, but if GNU
Mailman can provide better support to the Fedora community I'd like to
push that forward.

 > but there is also a "mailing list mode" which does more of what you
 > want. (One email per post, and you can reply directly.)

Which ain't so great.  Not for the person who likes mailing lists, and
not for the people who like discourse as a platform.  It's partly
social, of course, but there's also the technological difference
between synchronous and asynchronous messaging.  Platforms designed
for synchronous messaging tend to have longer "conversations", whereas
ansynchronous messaging tends to result in branchy thread trees.

Much as I love mailing lists, I admit that there are valid arguments
and personal preferences for web fora.  This is going to be one of
those situations where it kinda has to be tyranny of some kind, maybe
the tyranny of inertia, maybe tyranny of the majority.  But some
people (fvo "some" including "many") will be dissatisfied.

Steve
___
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: Upgrade to F30 gone wrong

[Chris Murphy]

On Tue, May 7, 2019 at 12:40 AM Nicolas Mailhot
 wrote:
>
>
>
> Le May 6, 2019 4:29:22 PM UTC, Chris Murphy  a écrit 
> :
> >On Mon, May 6, 2019 at 1:52 AM Nicolas Mailhot
> > wrote:
> >>
> >> Le dimanche 05 mai 2019 à 16:14 -0600, Chris Murphy a écrit :
> >> >
> >> > Right and that's the same with beta testing, which is how bugs like
> >> > this can sometimes not even get found until after release. A lot of
> >> > tests are done on pristine systems that are throw away. It's
> >entirely
> >> > understandable few people want to test Fedora pre-release on their
> >> > rock solid 5+ year old Fedora system, but we actually stumbled on
> >> > this
> >> > in some sense by luck of alternate arch acting like a canary.
> >>
> >> That's not true, many boot problems are found quite early in the
> >> process by rawhide users, but rawhide users feedback is not taken
> >into
> >> account by installer folks because they don't look at boot problems
> >> before quite late in the cycle, when rawhide users have already moved
> >> on manually, and the default solution is always to reinstall from
> >> scratch.
> >>
> >> So problems are found, just not fixed
> >
> >This is out of scope because the context of the conversation is
> >upgrades. You're talking about the installer which means clean
> >installs.
>
> I'm talking rescuing systems that do not boot anymore and that means the 
> install media. You can't rescue a system with broken boot from within this 
> system

I have no idea what you're talking about. The context of this thread
is a bug that happens during upgrades, and you do not need
rescue/install media to fix it. The Common Bugs lists the step you
need to successfully boot and fix the problem within this system.

-- 
Chris Murphy
___
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 1707154] perl-libwww-perl-6.39 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
perl-libwww-perl-6.39-1.fc30 has been pushed to the Fedora 30 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-89a1ffc9bf

-- 
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: Kernel upgrades

[Chris Murphy]

On Tue, May 7, 2019 at 8:29 AM Steven A. Falco  wrote:
>
> On 5/6/19 5:51 PM, Chris Murphy wrote:
>
> > But it's worth keeping an eye on anomalies. There is the potential for
> > goofy things happening. Unrelated to this particular feature, rather
> > it was grub.cfg being updated, in cases where that update happened
> > very quickly followed by an immediate reboot, GRUB only saw the
> > previous grub.cfg. On journaled file systems, the new file gets
> > written out, and indicated only in the journal, and a particular set
> > of circumstances preventing the root fs from being cleanly unmounted
> > resulted in a hidden new grub.cfg that only became revealed after
> > journal replay by the kernel code. The GRUB code can't read file
> > system journals, so it was seeing the stale file as a result of
> > reading stale file system metadata without the benefit of reading the
> > journal. :P
>
> I may indeed have tripped over that a time or two.  I've had cases where 
> strange things happened following a kernel update / immediate reboot.  Given 
> the relative non-volatility of /boot, it's starting to make sense to use a 
> plain ext2 fs for /boot rather than a more modern fs.
>
> If I ever have to reload this machine, I may switch to UEFI.  While I don't 
> like the FAT filesystems, their simplicity has an advantage in this 
> application.

The reality is, you can't disable UEFI on a UEFI computer. Legacy just
enables a compatibility support module on top of UEFI to present a
faux-BIOS to the bootloader and the kernel. I only recommend it if
there are UEFI bugs that can't be worked around, yet are masked by the
CSM. Any reputable vendor is responsive with firmware updates to
address the worst UEFI bugs. For laptops, not running UEFI natively
can also have negative power management side effects.

-- 
Chris Murphy
___
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 1703294] perl-DBD-Pg-3.8.0 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-DBD-Pg-3.8.0-1.fc31|perl-DBD-Pg-3.8.0-1.fc31
   ||perl-DBD-Pg-3.8.0-1.fc30
 Resolution|--- |ERRATA
Last Closed||2019-05-07 16:46:14



--- Comment #3 from Fedora Update System  ---
perl-DBD-Pg-3.8.0-1.fc30 has been pushed to the Fedora 30 stable repository. If
problems still persist, please make note of it in this bug report.

-- 
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 1703696] perl-Devel-PatchPerl-1.58 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-Devel-PatchPerl-1.58-1 |perl-Devel-PatchPerl-1.58-1
   |.fc31   |.fc31
   ||perl-Devel-PatchPerl-1.58-1
   ||.fc30
 Resolution|--- |ERRATA
Last Closed||2019-05-07 16:46:15



--- Comment #3 from Fedora Update System  ---
perl-Devel-PatchPerl-1.58-1.fc30 has been pushed to the Fedora 30 stable
repository. If problems still persist, please make note of it in this bug
report.

-- 
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 1705666] please add perl-DateTime-Format-SQLite to epel7

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #4 from Fedora Update System  ---
perl-DateTime-Format-SQLite-0.11-22.el7 has been submitted as an update to
Fedora EPEL 7.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-56a4330c5e

-- 
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 1705666] please add perl-DateTime-Format-SQLite to epel7

[bugzilla]

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



--- Comment #3 from Sergio Monteiro Basto  ---
oops , I just read the email now , please ignore my last comment .

Thanks

-- 
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 1705666] please add perl-DateTime-Format-SQLite to epel7

[bugzilla]

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



--- Comment #2 from Sergio Monteiro Basto  ---
(In reply to Jitka Plesnikova from comment #1)
> I requested EPEL7 branch.
> 
> https://pagure.io/releng/fedora-scm-requests/issue/11487

Epel7 branch already exist [1]

[1]
https://src.fedoraproject.org/rpms/perl-DateTime-Format-SQLite/commits/epel7


Hello, 

Please, I'd like request to commit to perl-DateTime-Format-
SQLite, my fas user is : sergiomb 

For me I think I will have
less work if I can add this package to epel7 .

Two years ago already was attempt add this package to epel7 [1] but the
package was deleted from koji , I don't know why. 

Thanks

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

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

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
 265  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d   
condor-8.6.11-1.el7
  73  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f8311ec8a2   
tor-0.3.5.8-1.el7
  41  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d2c1368294   
cinnamon-3.6.7-5.el7
  33  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-50a6a1ddfd   
afflib-3.7.18-2.el7
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f05ef50515   
php-horde-horde-5.2.21-1.el7
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-add436bec5   
php-horde-turba-4.2.24-1.el7
   9  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d28d3135da   
python36-3.6.8-1.el7
   7  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c499781e80   
python-gnupg-0.4.4-1.el7
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-de28ce6966   
drupal7-7.66-1.el7
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bc0182548b   
bubblewrap-0.3.3-2.el7


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

conda-4.6.13-1.el7
holland-1.1.15-4.el7
kgb-bot-1.51-2.el7
python-bottle-0.12.13-3.el7
python3-pycurl-7.43.0-7.el7
qsstv-9.4.1-1.el7

Details about builds:



 conda-4.6.13-1.el7 (FEDORA-EPEL-2019-64a5451672)
 Cross-platform, Python-agnostic binary package manager

Update Information:

Conda is a cross-platform, Python-agnostic binary package manager. It is the
package manager used by Anaconda installations, but it may be used for other
systems as well. Conda makes environments first-class citizens, making it easy
to create independent environments even for C libraries. Conda is written
entirely in Python.

References:

  [ 1 ] Bug #1631641 - Request an EPEL7 buiild of conda
https://bugzilla.redhat.com/show_bug.cgi?id=1631641




 holland-1.1.15-4.el7 (FEDORA-EPEL-2019-879e7fe038)
 Pluggable Backup Framework

Update Information:

fix my failure to properly declare requirements    add subprocess32 dep to
enable split better    upstream 1.1.15, add dependencies for holland-mysql
to relevant subpackages

ChangeLog:

* Mon May  6 2019 Pete Travis  - 1.1.15-4
- fix my failure to properly declare requirements
* Mon May  6 2019 Pete Travis  - 1.1.15-3
- add subprocess32 dep to enable split better
* Thu May  2 2019 Pete Travis  - 1.1.15-2
- add dependencies for holland-mysql to relevant subpackages
* Thu May  2 2019 Pete Travis  - 1.1.15-1
- Latest upstream

References:

  [ 1 ] Bug #1703567 - Subpackage missing dependencies
https://bugzilla.redhat.com/show_bug.cgi?id=1703567
  [ 2 ] Bug #1701580 - holland-1.1.15 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1701580




 kgb-bot-1.51-2.el7 (FEDORA-EPEL-2019-27a39bdc50)
 IRC Collaboration Bot

Update Information:

Make sure /var/run/kgb-bot gets created and assigned correct permissions

ChangeLog:

* Mon May  6 2019 Andrea Veri  - 1.51-2
- Make sure /var/run/kgb-bot gets created and assigned correct permissions




 python-bottle-0.12.13-3.el7 (FEDORA-EPEL-2019-29a9c757ec)
 Fast and simple WSGI-framework for small web-applications

Update Information:

Build for python34

ChangeLog:

* Sun May  5 2019 Orion Poplawski  - 0.12.13-3
- Build for python3_other

References:

  [ 1 ] Bug #1705680 - python34-pycurl package has disappeared from EPEL
https://bugzilla.redhat.com/show_bug.cgi?id=1705680

[EPEL-devel] Re: Is there an EPEL archive?

[James Gamei]

Thanks a lot for that. Seems to have worked


On 07/05/2019, 16:31, "Stephen John Smoogen"  wrote:

>
>
>
>On Tue, 7 May 2019 at 11:17, James Gamei  wrote:
>
>
>Hi
>
>I’m looking for an older version of a package (specifically qt5-qtwebkit
>5.6.1 for CentOS 7). Does anyone know if there is an archive like the
>CentOS vault for EPEL packages?
>
>
>
>
>
>EPEL has been in the past built like a rawhide where there is no regular
>archiving of old releases. We are hoping to change this but currently
>older packages will have to be downloaded from koji
>
>
>https://koji.fedoraproject.org/koji/buildinfo?buildID=954669
>
>https://koji.fedoraproject.org/koji/buildinfo?buildID=773143
>
>
>
>are 5.6.2 and a version of 5.6.1
>
>
> 
>
>Thanks
>
>James
>
>___
>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.fedoraproje
>ct.org 
>ect.org>
>
>
>
>
>
>
>-- 
>Stephen J Smoogen.
>
>
>
>
>
>

___
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

[EPEL-devel] Re: Is there an EPEL archive?

[Stephen John Smoogen]

On Tue, 7 May 2019 at 11:17, James Gamei  wrote:

> Hi
>
> I’m looking for an older version of a package (specifically qt5-qtwebkit
> 5.6.1 for CentOS 7). Does anyone know if there is an archive like the
> CentOS vault for EPEL packages?
>
>
EPEL has been in the past built like a rawhide where there is no regular
archiving of old releases. We are hoping to change this but currently older
packages will have to be downloaded from koji

https://koji.fedoraproject.org/koji/buildinfo?buildID=954669
https://koji.fedoraproject.org/koji/buildinfo?buildID=773143

are 5.6.2 and a version of 5.6.1



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


-- 
Stephen J Smoogen.
___
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

Re: [Fedocal] Reminder meeting : Modularity Team (weekly)

[Igor Gnatenko]

Except that everyone is on RH Summit, so there won't be a meeting today.

On Tue, May 7, 2019 at 4:54 PM Jun Aruga  wrote:

> > The agenda for the meeting is available as flagged tickets [in the
> Modularity repository](
> https://pagure.io/modularity/issues?status=Open=Meeting).
>
> No agenda? I have several topics to let you discuss.
>
> --
> Jun Aruga / He - His - Him
> ___
> 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

[EPEL-devel] Is there an EPEL archive?

[James Gamei]

Hi

I’m looking for an older version of a package (specifically qt5-qtwebkit
5.6.1 for CentOS 7). Does anyone know if there is an archive like the
CentOS vault for EPEL packages?

Thanks

James

___
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

Re: Where are armv7hl, i686 and ppc64le Container tar.xz files?

[Jun Aruga]

> pungi is the tool, and this:
> https://pagure.io/pungi-fedora/blob/f30/f/fedora-final.conf
> was the config used.

Kevin, I have a question.

https://pagure.io/pungi-fedora/blob/f30/f/fedora-final.conf#_322
> 'arches': ['armhfp', 'aarch64', 'ppc64le', 's390x', 'x86_64'],

From above setting for Container, ideally those 5 archs should be
released on URL [a] or [b]?
Where is ppc64le's image?

"'distro': 'Fedora-22', " in
https://pagure.io/pungi-fedora/blob/f30/f/fedora-final.conf#_320 is
right setting?

a. https://dl.fedoraproject.org/pub/fedora/linux/releases/30/Container/
  aarch64, x86_64
b. https://dl.fedoraproject.org/pub/fedora-secondary/releases/30/Container/
  s390x
c. https://dl.fedoraproject.org/pub/fedora/linux/development/30/Container/
  aarch64, armhfp, x86_64

-- 
Jun Aruga / He - His - Him
___
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: [Fedocal] Reminder meeting : Modularity Team (weekly)

[Jun Aruga]

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

No agenda? I have several topics to let you discuss.

-- 
Jun Aruga / He - His - Him
___
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

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

[updates]

The following Fedora EPEL 6 Security updates need testing:
 Age  URL
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-009f5f140b   
php-horde-horde-5.2.21-1.el6
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-b9ea566899   
php-horde-turba-4.2.24-1.el6
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-e406623fec   
bird-1.6.6-1.el6
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-dc3342b950   
drupal7-7.66-1.el6


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

holland-1.1.15-3.el6
singularity-3.1.1-1.el6

Details about builds:



 holland-1.1.15-3.el6 (FEDORA-EPEL-2019-bb53a3db63)
 Pluggable Backup Framework

Update Information:

add subprocess32 dep to enable split better    upstream 1.1.15, add
dependencies for holland-mysql to relevant subpackages

ChangeLog:

* Mon May  6 2019 Pete Travis  - 1.1.15-3
- add subprocess32 dep to enable split better
* Thu May  2 2019 Pete Travis  - 1.1.15-2
- add dependencies for holland-mysql to relevant subpackages
* Thu May  2 2019 Pete Travis  - 1.1.15-1
- Latest upstream

References:

  [ 1 ] Bug #1701580 - holland-1.1.15 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1701580
  [ 2 ] Bug #1703567 - Subpackage missing dependencies
https://bugzilla.redhat.com/show_bug.cgi?id=1703567




 singularity-3.1.1-1.el6 (FEDORA-EPEL-2019-1069e1d162)
 Application and environment virtualization

Update Information:

Update to upstream 3.1.1-1

ChangeLog:

* Tue Apr  2 2019 Dave Dykstra  - 3.1.1-1
- Update to upstream 3.1.1-1
* Mon Feb 25 2019 Dave Dykstra  - 3.1.0-1
- Update to upstream 3.1.0-1
* Tue Jan 22 2019 Dave Dykstra  - 3.0.3-1
- Update to upstream 3.0.3-1 release.
* Fri Jan 18 2019 Dave Dykstra  - 3.0.3-rc2
- Update to upstream 3.0.3-rc2
* Wed Jan 16 2019 Dave Dykstra  - 3.0.3-rc1
- Update to upstream 3.0.3-rc1
* Wed Jan  9 2019 Dave Dykstra  - 3.0.2-1.2
- Add patch for PR 2531
* Mon Jan  7 2019 Dave Dykstra  - 3.0.2-1.1
- Update to upstream 3.0.2
- Added patches for PRs 2472, 2478, 2481

References:

  [ 1 ] Bug #1693909 - singularity-3.1.1 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1693909


___
epel-devel mailing list -- epel-de...@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-de...@lists.fedoraproject.org

Re: Kernel upgrades

[Steven A. Falco]

On 5/6/19 5:51 PM, Chris Murphy wrote:

> But it's worth keeping an eye on anomalies. There is the potential for
> goofy things happening. Unrelated to this particular feature, rather
> it was grub.cfg being updated, in cases where that update happened
> very quickly followed by an immediate reboot, GRUB only saw the
> previous grub.cfg. On journaled file systems, the new file gets
> written out, and indicated only in the journal, and a particular set
> of circumstances preventing the root fs from being cleanly unmounted
> resulted in a hidden new grub.cfg that only became revealed after
> journal replay by the kernel code. The GRUB code can't read file
> system journals, so it was seeing the stale file as a result of
> reading stale file system metadata without the benefit of reading the
> journal. :P

I may indeed have tripped over that a time or two.  I've had cases where 
strange things happened following a kernel update / immediate reboot.  Given 
the relative non-volatility of /boot, it's starting to make sense to use a 
plain ext2 fs for /boot rather than a more modern fs.

If I ever have to reload this machine, I may switch to UEFI.  While I don't 
like the FAT filesystems, their simplicity has an advantage in this application.

Steve
___
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 1698172] perl-Sereal-4.007 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Sereal-4.007-1.fc31|perl-Sereal-4.007-1.fc31
   |perl-Sereal-4.007-1.fc28|perl-Sereal-4.007-1.fc28
   ||perl-Sereal-4.007-1.fc29



--- Comment #10 from Fedora Update System  ---
perl-Sereal-4.007-1.fc29 has been pushed to the Fedora 29 stable repository. If
problems still persist, please make note of it in this bug report.

-- 
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 1703269] serious typo in Summary

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Sereal-Encoder-4.007-2 |perl-Sereal-Encoder-4.007-2
   |.fc28   |.fc28
   |perl-Sereal-Encoder-4.007-2 |perl-Sereal-Encoder-4.007-2
   |.fc30   |.fc30
   ||perl-Sereal-Encoder-4.007-2
   ||.fc29



--- Comment #10 from Fedora Update System  ---
perl-Sereal-Encoder-4.007-2.fc29 has been pushed to the Fedora 29 stable
repository. If problems still persist, please make note of it in this bug
report.

-- 
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 1520948] Upgrade perl-Test-WWW-Mechanize-PSGI to 0.38

[bugzilla]

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



--- Comment #10 from Fedora Update System  ---
perl-Test-WWW-Mechanize-PSGI-0.39-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-7ca5842031

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

[389-devel] Re: Groups are not accessible by filter

[Viktor Ashirov]

On Tue, May 7, 2019 at 2:09 PM William Brown  wrote:
>
>
>
> > On 7 May 2019, at 22:03, Viktor Ashirov  wrote:
> >
> > On Mon, Apr 29, 2019 at 6:48 AM William Brown  wrote:
> >>
> >>
> >>
> >>> On 29 Apr 2019, at 12:33, Anuj Borah  wrote:
> >>>
> >>> @William Brown
> >>>
> >>> Thanks for the tip!
> >>>
> >>> (Pdb) len(topo.standalone.search_s(DEFAULT_SUFFIX, 
> >>> ldap.SCOPE_SUBTREE,"testUserAccountControl:1.2.840.113556.1.4.803:=8388608",
> >>>  ['attrlist=cn:sn:uid:testUserAccountControl']))
> >>> 6
> >>> (Pdb) len(Accounts(topo.standalone, 
> >>> DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608)"))
> >>> 6
> >>>
> >>> We cant not mix up ['attrlist=cn:sn:uid:testUserAccountControl'] with 
> >>> filter , like we do with search_s .
> >>>
> >>> (Pdb) len(Accounts(topo.standalone, 
> >>> DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608)",
> >>>  ['attrlist=cn:sn:uid:testUserAccountControl']))
> >>> *** TypeError: filter() takes 2 positional arguments but 3 were given
> >>> (Pdb) len(Accounts(topo.standalone, 
> >>> DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608),
> >>>  ['attrlist=cn:sn:uid:testUserAccountControl']"))
> >>> *** ldap.FILTER_ERROR: {'desc': 'Bad search filter', 'errno': 2, 'info': 
> >>> 'No such file or directory'}
> >>>
> >>> Again i have to use "re" module for the same .
> >>>
> >>>
> >>
> >> What are you trying to achieve?
> > Test case is very simple: search for entries using different filters
> > and request specific attributes.
>
> But those entries have types and classes - you know what you are expecting to 
> get.
>
> > The problem that Anuj is facing is that filter() doesn't support
> > attrlist. Moreover, _unsafe_raw_entry() doesn't return *all*
> > attributes, it omits operational attributes (like nsRoleDN).
> > IMHO, search_s is good enough here.
>
> If you want to avoid any of the "magic" use DSLdapObjects(instance).filter() 
> then because that doesn't prescribe any classes. But it does take a lot of 
> the safety out of the library, and I still think that there is something 
> missing in the approach here.
I have a problem with DSLdapObjects(instance).filter() is that it
takes way more effort to write *test* code with a very little benefit.
Consider this example: I need to fetch all regular attributes,
operational attributes and entry state information from the server.
With DSLdapObjects I had to do the following:
(Pdb) _ = Accounts(topo.standalone, DEFAULT_SUFFIX)
(Pdb) _._filterattrs=["*", "+", "nscpEntryWSI"]
(Pdb) _.filter(F10)[0].get_all_attrs()

get_all_attrs() doesn't return nscpEntryWSI at all, and, as a bonus,
lowercases some of the attribute names.

vs.

(Pdb) topo.standalone.search_s(DEFAULT_SUFFIX, ldap.SCOPE_SUBTREE,
attrlist=["*", "+", "nscpEntryWSI"])

Safety here is not a main concern, since it's a test code. In tests we
need more than often to have a raw LDAP access without too much
abstractions. Main concern is precision and certainty.
Abstractions are good when they increase clarity and make things
certain. In case of the very common search pattern above, DSLdapObject
doesn't work really well. For me at least.
>
>
> >>
> >>
> >> Sincerely,
> >>
> >> William Brown
> >>
> >> Senior Software Engineer, 389 Directory Server
> >> SUSE Labs
> >> ___
> >> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
> >> To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
> >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >> List Archives: 
> >> https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
> >
> >
> >
> > --
> > Viktor
> > ___
> > 389-devel mailing list -- 389-devel@lists.fedoraproject.org
> > To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
>
> —
> Sincerely,
>
> William Brown
>
> Senior Software Engineer, 389 Directory Server
> SUSE Labs
> ___
> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
> To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org



-- 
Viktor
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of 

[389-devel] Re: Groups are not accessible by filter

[Ludwig Krispenz]

On 05/07/2019 02:08 PM, William Brown wrote:



On 7 May 2019, at 22:03, Viktor Ashirov  wrote:

On Mon, Apr 29, 2019 at 6:48 AM William Brown  wrote:




On 29 Apr 2019, at 12:33, Anuj Borah  wrote:

@William Brown

Thanks for the tip!

(Pdb) len(topo.standalone.search_s(DEFAULT_SUFFIX, 
ldap.SCOPE_SUBTREE,"testUserAccountControl:1.2.840.113556.1.4.803:=8388608", 
['attrlist=cn:sn:uid:testUserAccountControl']))
6
(Pdb) len(Accounts(topo.standalone, 
DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608)"))
6

We cant not mix up ['attrlist=cn:sn:uid:testUserAccountControl'] with filter , 
like we do with search_s .

(Pdb) len(Accounts(topo.standalone, 
DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608)",
 ['attrlist=cn:sn:uid:testUserAccountControl']))
*** TypeError: filter() takes 2 positional arguments but 3 were given
(Pdb) len(Accounts(topo.standalone, 
DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608), 
['attrlist=cn:sn:uid:testUserAccountControl']"))
*** ldap.FILTER_ERROR: {'desc': 'Bad search filter', 'errno': 2, 'info': 'No 
such file or directory'}

Again i have to use "re" module for the same .



What are you trying to achieve?

Test case is very simple: search for entries using different filters
and request specific attributes.

But those entries have types and classes - you know what you are expecting to 
get.


The problem that Anuj is facing is that filter() doesn't support
attrlist. Moreover, _unsafe_raw_entry() doesn't return *all*
attributes, it omits operational attributes (like nsRoleDN).
IMHO, search_s is good enough here.

If you want to avoid any of the "magic" use DSLdapObjects(instance).filter() 
then because that doesn't prescribe any classes. But it does take a lot of the safety out 
of the library, and I still think that there is something missing in the approach here.
but we are testing ldap clients and need to be able to do anything the 
protocol allows, not only what you declare safe





Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org



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

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org


--
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric 
Shander
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org

[389-devel] Re: Groups are not accessible by filter

[William Brown]

> On 7 May 2019, at 22:03, Viktor Ashirov  wrote:
> 
> On Mon, Apr 29, 2019 at 6:48 AM William Brown  wrote:
>> 
>> 
>> 
>>> On 29 Apr 2019, at 12:33, Anuj Borah  wrote:
>>> 
>>> @William Brown
>>> 
>>> Thanks for the tip!
>>> 
>>> (Pdb) len(topo.standalone.search_s(DEFAULT_SUFFIX, 
>>> ldap.SCOPE_SUBTREE,"testUserAccountControl:1.2.840.113556.1.4.803:=8388608",
>>>  ['attrlist=cn:sn:uid:testUserAccountControl']))
>>> 6
>>> (Pdb) len(Accounts(topo.standalone, 
>>> DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608)"))
>>> 6
>>> 
>>> We cant not mix up ['attrlist=cn:sn:uid:testUserAccountControl'] with 
>>> filter , like we do with search_s .
>>> 
>>> (Pdb) len(Accounts(topo.standalone, 
>>> DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608)",
>>>  ['attrlist=cn:sn:uid:testUserAccountControl']))
>>> *** TypeError: filter() takes 2 positional arguments but 3 were given
>>> (Pdb) len(Accounts(topo.standalone, 
>>> DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608),
>>>  ['attrlist=cn:sn:uid:testUserAccountControl']"))
>>> *** ldap.FILTER_ERROR: {'desc': 'Bad search filter', 'errno': 2, 'info': 
>>> 'No such file or directory'}
>>> 
>>> Again i have to use "re" module for the same .
>>> 
>>> 
>> 
>> What are you trying to achieve?
> Test case is very simple: search for entries using different filters
> and request specific attributes.

But those entries have types and classes - you know what you are expecting to 
get.

> The problem that Anuj is facing is that filter() doesn't support
> attrlist. Moreover, _unsafe_raw_entry() doesn't return *all*
> attributes, it omits operational attributes (like nsRoleDN).
> IMHO, search_s is good enough here.

If you want to avoid any of the "magic" use DSLdapObjects(instance).filter() 
then because that doesn't prescribe any classes. But it does take a lot of the 
safety out of the library, and I still think that there is something missing in 
the approach here. 


>> 
>> 
>> Sincerely,
>> 
>> William Brown
>> 
>> Senior Software Engineer, 389 Directory Server
>> SUSE Labs
>> ___
>> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
>> To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
> 
> 
> 
> --
> Viktor
> ___
> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
> To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org

[389-devel] Re: Groups are not accessible by filter

[Viktor Ashirov]

On Mon, Apr 29, 2019 at 6:48 AM William Brown  wrote:
>
>
>
> > On 29 Apr 2019, at 12:33, Anuj Borah  wrote:
> >
> > @William Brown
> >
> > Thanks for the tip!
> >
> > (Pdb) len(topo.standalone.search_s(DEFAULT_SUFFIX, 
> > ldap.SCOPE_SUBTREE,"testUserAccountControl:1.2.840.113556.1.4.803:=8388608",
> >  ['attrlist=cn:sn:uid:testUserAccountControl']))
> > 6
> > (Pdb) len(Accounts(topo.standalone, 
> > DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608)"))
> > 6
> >
> > We cant not mix up ['attrlist=cn:sn:uid:testUserAccountControl'] with 
> > filter , like we do with search_s .
> >
> > (Pdb) len(Accounts(topo.standalone, 
> > DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608)",
> >  ['attrlist=cn:sn:uid:testUserAccountControl']))
> > *** TypeError: filter() takes 2 positional arguments but 3 were given
> > (Pdb) len(Accounts(topo.standalone, 
> > DEFAULT_SUFFIX).filter("(testUserAccountControl:1.2.840.113556.1.4.803:=8388608),
> >  ['attrlist=cn:sn:uid:testUserAccountControl']"))
> > *** ldap.FILTER_ERROR: {'desc': 'Bad search filter', 'errno': 2, 'info': 
> > 'No such file or directory'}
> >
> > Again i have to use "re" module for the same .
> >
> >
>
> What are you trying to achieve?
Test case is very simple: search for entries using different filters
and request specific attributes.
The problem that Anuj is facing is that filter() doesn't support
attrlist. Moreover, _unsafe_raw_entry() doesn't return *all*
attributes, it omits operational attributes (like nsRoleDN).
IMHO, search_s is good enough here.
>
>
> Sincerely,
>
> William Brown
>
> Senior Software Engineer, 389 Directory Server
> SUSE Labs
> ___
> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
> To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org



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

Re: module testing files?

[Jun Aruga]

I think the people who are using or used "meta-test-family" (the
application to test module), has these kind of testing files.

But I faced an installation error on my Fedora 30.
https://github.com/fedora-modularity/meta-test-family/issues/245

Are you using "meta-test-family" now?
Does it work on your environment?

-- 
Jun Aruga / He - His - Him
___
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 1707154] perl-libwww-perl-6.39 is available

[bugzilla]

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



--- Comment #2 from Fedora Update System  ---
perl-libwww-perl-6.39-1.fc30 has been submitted as an update to Fedora 30.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-89a1ffc9bf

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

mpich rebuilt with default c/cxx/ld flags

[Zbigniew Jędrzejewski-Szmek]

Heads-up: I dropped most of the build flags customizations in mpich.
This "resets" mpich back to the Fedora defaults and, inter alia, adds
all the hardening options. Unit tests pass, including those in dependent
packages, but of course this is not a definitive proof of anything. If
you see any strange crashes or slowdowns, please let me know.

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

[Bug 1707154] perl-libwww-perl-6.39 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-libwww-perl-6.39-1.fc3
   ||1



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

-- 
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 1705666] please add perl-DateTime-Format-SQLite to epel7

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
Summary|plese add   |please add
   |perl-DateTime-Format-SQLite |perl-DateTime-Format-SQLite
   |to epel7|to epel7



--- Comment #1 from Jitka Plesnikova  ---
I requested EPEL7 branch.

https://pagure.io/releng/fedora-scm-requests/issue/11487

-- 
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: orphan compat-openssl10-pkcs11-helper

[Jakub Jelen]

On Mon, 2019-05-06 at 10:59 -0500, Rex Dieter wrote:
> Once upon a time, qca needed this, but hasn't for quite awhile, so
> I'm no 
> longer interested in maintaining compat-opensl10-pkcs11-helper
> 
> According to repoquery, one item (still) depends on it:
> gnupg-pkcs11-scd

I do not think this is needed anymore. I filled the following bug to
update to current version, which builds against current opnessl:

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

Regards,
-- 
Jakub Jelen
Senior Software Engineer
Security Technologies
Red Hat, Inc.
___
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 1707167] perl-Log-ger-0.028 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-Log-ger-0.028-1.fc31
 Resolution|--- |RAWHIDE
Last Closed||2019-05-07 07:50:19



-- 
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: Upgrade to F30 gone wrong

[Nicolas Mailhot via devel]

Le May 6, 2019 4:29:22 PM UTC, Chris Murphy  a écrit :
>On Mon, May 6, 2019 at 1:52 AM Nicolas Mailhot
> wrote:
>>
>> Le dimanche 05 mai 2019 à 16:14 -0600, Chris Murphy a écrit :
>> >
>> > Right and that's the same with beta testing, which is how bugs like
>> > this can sometimes not even get found until after release. A lot of
>> > tests are done on pristine systems that are throw away. It's
>entirely
>> > understandable few people want to test Fedora pre-release on their
>> > rock solid 5+ year old Fedora system, but we actually stumbled on
>> > this
>> > in some sense by luck of alternate arch acting like a canary.
>>
>> That's not true, many boot problems are found quite early in the
>> process by rawhide users, but rawhide users feedback is not taken
>into
>> account by installer folks because they don't look at boot problems
>> before quite late in the cycle, when rawhide users have already moved
>> on manually, and the default solution is always to reinstall from
>> scratch.
>>
>> So problems are found, just not fixed
>
>This is out of scope because the context of the conversation is
>upgrades. You're talking about the installer which means clean
>installs.

I'm talking rescuing systems that do not boot anymore and that means the 
install media. You can't rescue a system with broken boot from within this 
system
-- 
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