[389-devel] Re: Groups are not accessible by filter
@William Brown
Its not relevant to this subject line , but its related to lib389 .
Question : Does get_attrs_vals_utf8 and all get_attrs_vals types should
case sensitive ??
Look at bellow result:
with search_s:
(Pdb) topo.standalone.search_s(DEFAULT_SUFFIX, ldap.SCOPE_SUBTREE, F4,
['cn', 'Cn', 'CN'])
[dn: uid=bhall,ou=People,dc=example,dc=com
cn: Benjamin Hall
]
with filter:
(Pdb) Accounts(topo.standalone,
DEFAULT_SUFFIX).filter(F4)[0].get_attrs_vals_utf8(['cn', 'Cn', 'CN'])
{'cn': ['Benjamin Hall'], 'Cn': ['Benjamin Hall'], 'CN': ['Benjamin Hall']}
(Pdb) Accounts(topo.standalone,
DEFAULT_SUFFIX).filter(F4)[0]._unsafe_raw_entry()
dn: uid=bhall,ou=People,dc=example,dc=com
cn: Benjamin Hall
gidNumber: 2000
givenName: Benjamin
homeDirectory: /home/bhall
l: sunnyvale
mail: bh...@anuj.com
manager: uid=trigden,ou=People,dc=example,dc=com
objectClass: top
objectClass: account
objectClass: posixaccount
objectClass: inetOrgPerson
objectClass: organizationalPerson
objectClass: nsMemberOf
objectClass: nsAccount
objectClass: person
ou: Product Development
ou: People
roomNumber: 2511
sn: Hall
telephoneNumber: +1 408 555 6067
uid: bhall
uidNumber: 1000
userPassword:
{PBKDF2_SHA256}AAAIAC03kM8if/x5GVc9teHEpMTOvB67mfH6NZYEmazAev2n6eoN2X+3JKu13ZpIG+WCPGWZH0niBxc7xvvqFsMkNPoRlBvmx23fWM+5VYcTCJs+iWQRxTb0FV/hheEU9a+Tqdj6fa0lL1aJTiOkKKk/mJdAHUiRvh8M6BtZmmc3pD0KNDwHQK/k/tuP1X7+nA+6ioT5WCb2NjjR4jFuNO681Ko6nG/wAWz/T+lYsVHdFV84MfBX81dgRDGmGyAew2YwNDeuEEmFH9EFYS9iczs241/3oA9igvCPuiSc7hoI/EOsRm4c6IhikouebRVCvX9eiZfjPSIBwXJTFHLi93r7xxNC4q3WWZZh2I01A09SOoQZPhXDXMkL6nuAJawG0wkU3JFeJecTSsk3EPgg+xX15X52Ayt7yKMRfTlYRtp45uku
(Pdb) Accounts(topo.standalone,
DEFAULT_SUFFIX).filter(F4)[0].get_attr_val_utf8('CN')
'Benjamin Hall'
(Pdb) Accounts(topo.standalone,
DEFAULT_SUFFIX).filter(F4)[0].get_attr_val_utf8('cn')
'Benjamin Hall'
(Pdb) Accounts(topo.standalone,
DEFAULT_SUFFIX).filter(F4)[0].get_attr_val_utf8('Cn')
'Benjamin Hall'
Regards
Anuj Borah
On Thu, May 9, 2019 at 9:00 AM Anuj Borah wrote:
> @William Brown
>
> Thank you for the clarification.
>
> Regards
> Anuj Borah
>
> On Thu, May 9, 2019 at 8:57 AM William Brown wrote:
>
>>
>>
>> > On 9 May 2019, at 12:47, Anuj Borah wrote:
>> >
>> > @William Brown
>> >
>> > I am attaching the main script where i am facing the problem .
>> >
>> > F4 gives me the following :
>> >
>> > With search_s:
>> >
>> > (Pdb) topo.standalone.search_s(DEFAULT_SUFFIX, ldap.SCOPE_SUBTREE, F4)
>> > [dn: uid=bhall,ou=People,dc=example,dc=com
>> > cn: Benjamin Hall
>> > gidNumber: 2000
>> > givenName: Benjamin
>> > homeDirectory: /home/bhall
>> > l: sunnyvale
>> > mail: bh...@anuj.com
>> > manager: uid=trigden,ou=People,dc=example,dc=com
>> > objectClass: top
>> > objectClass: account
>> > objectClass: posixaccount
>> > objectClass: inetOrgPerson
>> > objectClass: organizationalPerson
>> > objectClass: nsMemberOf
>> > objectClass: nsAccount
>> > objectClass: person
>> > ou: Product Development
>> > ou: People
>> > roomNumber: 2511
>> > sn: Hall
>> > telephoneNumber: +1 408 555 6067
>> > uid: bhall
>> > uidNumber: 1000
>> > userPassword:
>> {PBKDF2_SHA256}AAAIAAlpB8Yaw03XDVfXkH++eiCaugb3D660gbb6xBE3dkSCXOiCVqvM80dTPhPuSBISkY8IWJZgZXXoDt54brqRweEpqZ4YPrMTtqBAd/2kCsX+ZRM9phJLZFd9k7bIAM3joCnxVPFwyR1ETDSHkes0RSql7Isi+oKb8dloC+m5vzj1NG1M/o0TxdICTMxIBvuln+BdANOS9waGyqJgZfZBnQfw2t3lHOKXFxiduaWSZJvwVV8JtYkHt/ofdmqKItayc00eG6EM44qPS19XZa+3drTADPkL7HNAVhMHg1Y8iIWIXKvlZ7WJ1V/ySrHL6SU6XzcXtMNjBT/qi+GCHpu2Bc+Ka2C0iUZwY5ZiJ7YUANa3UYxh6oIVUgKNVmX+4CkJczJLcEgoI43zFCFnFsjtNHYwflPuIPFtwaXvgeBojItZ
>> >
>> > ]
>> >
>> > With filter:
>> >
>> > (Pdb) Accounts(topo.standalone, DEFAULT_SUFFIX).filter(F4)[0].dn
>> > 'uid=bhall,ou=People,dc=example,dc=com'
>> > (Pdb) Accounts(topo.standalone,
>> DEFAULT_SUFFIX).filter(F4)[0]._unsafe_raw_entry()
>> > dn: uid=bhall,ou=People,dc=example,dc=com
>> > cn: Benjamin Hall
>> > gidNumber: 2000
>> > givenName: Benjamin
>> > homeDirectory: /home/bhall
>> > l: sunnyvale
>> > mail: bh...@anuj.com
>> > manager: uid=trigden,ou=People,dc=example,dc=com
>> > objectClass: top
>> > objectClass: account
>> > objectClass: posixaccount
>> > objectClass: inetOrgPerson
>> > objectClass: organizationalPerson
>> > objectClass: nsMemberOf
>> > objectClass: nsAccount
>> > objectClass: person
>> > ou: Product Development
>> > ou: People
>> > roomNumber: 2511
>> > sn: Hall
>> > telephoneNumber: +1 408 555 6067
>> > uid: bhall
>> > uidNumber: 1000
>> > userPassword:
>> {PBKDF2_SHA256}AAAIAAlpB8Yaw03XDVfXkH++eiCaugb3D660gbb6xBE3dkSCXOiCVqvM80dTPhPuSBISkY8IWJZgZXXoDt54brqRweEpqZ4YPrMTtqBAd/2kCsX+ZRM9phJLZFd9k7bIAM3joCnxVPFwyR1ETDSHkes0RSql7Isi+oKb8dloC+m5vzj1NG1M/o0TxdICTMxIBvuln+BdANOS9waGyqJgZfZBnQfw2t3lHOKXFxiduaWSZJvwVV8JtYkHt/ofdmqKItayc00eG6EM44qPS19XZa+3drTADPkL7HNAVhMHg1Y8iIWIXKvlZ7WJ1V/ySrHL6SU6XzcXtMNjBT/qi+GCHpu2Bc+Ka2C0iUZwY5ZiJ7YUANa3UYxh6oIVUgKNVmX+4CkJczJLcEgoI43zFCFnFsjtNHYwflPuIPFtwaXvgeBojItZ
>> >
>> > Now consider the following condition ,
>> >
>> > (Pdb)
[Bug 1686595] rt-4.4.4 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1686595 --- Comment #4 from Fedora Update System --- rt-4.4.4-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-7d9d577ad2 -- 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
Thank you for the clarification.
Regards
Anuj Borah
On Thu, May 9, 2019 at 8:57 AM William Brown wrote:
>
>
> > On 9 May 2019, at 12:47, Anuj Borah wrote:
> >
> > @William Brown
> >
> > I am attaching the main script where i am facing the problem .
> >
> > F4 gives me the following :
> >
> > With search_s:
> >
> > (Pdb) topo.standalone.search_s(DEFAULT_SUFFIX, ldap.SCOPE_SUBTREE, F4)
> > [dn: uid=bhall,ou=People,dc=example,dc=com
> > cn: Benjamin Hall
> > gidNumber: 2000
> > givenName: Benjamin
> > homeDirectory: /home/bhall
> > l: sunnyvale
> > mail: bh...@anuj.com
> > manager: uid=trigden,ou=People,dc=example,dc=com
> > objectClass: top
> > objectClass: account
> > objectClass: posixaccount
> > objectClass: inetOrgPerson
> > objectClass: organizationalPerson
> > objectClass: nsMemberOf
> > objectClass: nsAccount
> > objectClass: person
> > ou: Product Development
> > ou: People
> > roomNumber: 2511
> > sn: Hall
> > telephoneNumber: +1 408 555 6067
> > uid: bhall
> > uidNumber: 1000
> > userPassword:
> {PBKDF2_SHA256}AAAIAAlpB8Yaw03XDVfXkH++eiCaugb3D660gbb6xBE3dkSCXOiCVqvM80dTPhPuSBISkY8IWJZgZXXoDt54brqRweEpqZ4YPrMTtqBAd/2kCsX+ZRM9phJLZFd9k7bIAM3joCnxVPFwyR1ETDSHkes0RSql7Isi+oKb8dloC+m5vzj1NG1M/o0TxdICTMxIBvuln+BdANOS9waGyqJgZfZBnQfw2t3lHOKXFxiduaWSZJvwVV8JtYkHt/ofdmqKItayc00eG6EM44qPS19XZa+3drTADPkL7HNAVhMHg1Y8iIWIXKvlZ7WJ1V/ySrHL6SU6XzcXtMNjBT/qi+GCHpu2Bc+Ka2C0iUZwY5ZiJ7YUANa3UYxh6oIVUgKNVmX+4CkJczJLcEgoI43zFCFnFsjtNHYwflPuIPFtwaXvgeBojItZ
> >
> > ]
> >
> > With filter:
> >
> > (Pdb) Accounts(topo.standalone, DEFAULT_SUFFIX).filter(F4)[0].dn
> > 'uid=bhall,ou=People,dc=example,dc=com'
> > (Pdb) Accounts(topo.standalone,
> DEFAULT_SUFFIX).filter(F4)[0]._unsafe_raw_entry()
> > dn: uid=bhall,ou=People,dc=example,dc=com
> > cn: Benjamin Hall
> > gidNumber: 2000
> > givenName: Benjamin
> > homeDirectory: /home/bhall
> > l: sunnyvale
> > mail: bh...@anuj.com
> > manager: uid=trigden,ou=People,dc=example,dc=com
> > objectClass: top
> > objectClass: account
> > objectClass: posixaccount
> > objectClass: inetOrgPerson
> > objectClass: organizationalPerson
> > objectClass: nsMemberOf
> > objectClass: nsAccount
> > objectClass: person
> > ou: Product Development
> > ou: People
> > roomNumber: 2511
> > sn: Hall
> > telephoneNumber: +1 408 555 6067
> > uid: bhall
> > uidNumber: 1000
> > userPassword:
> {PBKDF2_SHA256}AAAIAAlpB8Yaw03XDVfXkH++eiCaugb3D660gbb6xBE3dkSCXOiCVqvM80dTPhPuSBISkY8IWJZgZXXoDt54brqRweEpqZ4YPrMTtqBAd/2kCsX+ZRM9phJLZFd9k7bIAM3joCnxVPFwyR1ETDSHkes0RSql7Isi+oKb8dloC+m5vzj1NG1M/o0TxdICTMxIBvuln+BdANOS9waGyqJgZfZBnQfw2t3lHOKXFxiduaWSZJvwVV8JtYkHt/ofdmqKItayc00eG6EM44qPS19XZa+3drTADPkL7HNAVhMHg1Y8iIWIXKvlZ7WJ1V/ySrHL6SU6XzcXtMNjBT/qi+GCHpu2Bc+Ka2C0iUZwY5ZiJ7YUANa3UYxh6oIVUgKNVmX+4CkJczJLcEgoI43zFCFnFsjtNHYwflPuIPFtwaXvgeBojItZ
> >
> > Now consider the following condition ,
> >
> > (Pdb) topo.standalone.search_s(DEFAULT_SUFFIX, ldap.SCOPE_SUBTREE,
> F4,['modifiersName','modifyTimestamp'])
> > [dn: uid=bhall,ou=People,dc=example,dc=com
> > modifiersName: cn=directory manager
> > modifyTimestamp: 20190509030743Z
> >
> > ]
> >
> > Problem is :
> > modifiersName and modifyTimestamp can never get with filter .
>
>
> This is not the fault of the filter, but the fault of how you are treating
> these objects. Filter tells you *what entries to find* not what attributes
> to get from them. To get specific attributes you have to interact with the
> results of the filter search.
>
> I have formerly mentioned you can assign the results of searches such as:
>
> bhall_account = Accounts(...).filter(F4)[0]
>
> bhall_account is now an Instance of the Account object, which itself is
> DSLdapObject. Now you have the entry, you can access attributes of it.
>
> values =
> bhall_account.get_attrs_vals_utf8(['modifiersName','modifyTimestamp'])
> print(values)
>
> Should be:
>
> {
>"modifiersName": '...',
>"modifyTimestamp": '...',
> }
>
> I don't know why you still are afraid to assign results from the searches.
> Fundamentally: DSLdapObjects (and it's subclasses) is the SET of all
> possible entries, and the gateway to searching. It returns instances of
> DSLdapObject, that allow direct inspection and manipulation of that
> data from the entry. I am worried that there is a still a deep
> misunderstanding of the API and how to use it, which is causing these
> problems (and odd accusations ...) and I don't understand how to explain it
> or help you to get past this barrier because this topic has been circled
> and discussed for months. How can I help you to understand how to use this
> properly and correctly?
>
>
> PS: There is a reason that function has the word "unsafe" in it, so please
> don't use things marked unsafe in tests or code :(
>
>
> —
> 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
[EPEL-devel] Re: KDE rebuild for RHEL8
Le 09/05/2019 à 00:09, Troy Dawson a écrit : > Just a heads up, incase people are wondering. > My KDE build that I built on RHEL8 beta works [1] on RHEL8 final release. > I have taken a RHEL8-Beta, already running KDE, and updated it to > RHEL8, and everything updated, and worked [1] > I have also taken a fresh installed, and updated, RHEL8 minimal, and > run the above commands to install KDE, and it worked also. > > That doesn't mean this repo will be up forever, but it should last > until we get KDE in EPEL8, whenever that happens. On a side note. Mere user of CentOS 7 + KDE here wondering what my favorite desktop environment will become in the future. Reading this message, I just want to know that your efforts are much appreciated. Cheers from the South of France, Niki Kovacs -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12 ___ 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 1686595] rt-4.4.4 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1686595 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- rt-4.4.4-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-bfc3898b2a -- 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: On GCL and libselinux
On Tue, May 7, 2019 at 3:12 PM Dominik 'Rathann' Mierzejewski wrote: > [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. Thanks! Now the question is whether I can find time to write an article. I need a ghost writer. :-) -- Jerry James http://www.jamezone.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
[Bug 1703675] perl-FFI-CheckLib-0.24 is available
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 |perl-FFI-CheckLib-0.24-1.fc |29 |29 ||perl-FFI-CheckLib-0.24-1.fc ||28 --- Comment #10 from Fedora Update System --- perl-FFI-CheckLib-0.24-1.fc28 has been pushed to the Fedora 28 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
Re: [Fedora-packaging] Schedule for Thursday's FPC Meeting (2019-05-09 16:00 UTC)
On 08. 05. 19 23:01, James Antill wrote: Following is the list of topics that will be discussed in the FPC meeting Thursday at 2019-05-09 16:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. uitime): = Day: Thursday == 2019-05-09 09:00 PDT US/Pacific 2019-05-09 12:00 EDT --> US/Eastern <-- 2019-05-09 16:00 UTC UTC 2019-05-09 17:00 BST Europe/London 2019-05-09 18:00 CEST Europe/Berlin 2019-05-09 18:00 CEST Europe/Paris 2019-05-09 21:30 IST Asia/Calcutta New Day: Friday - 2019-05-10 00:00 HKT Asia/Hong_Kong 2019-05-10 00:00 +08 Asia/Singapore 2019-05-10 01:00 JST Asia/Tokyo 2019-05-10 02:00 AEST Australia/Brisbane Links to all tickets below can be found at: https://pagure.io/packaging-committee/issues?status=Open=meeting = Followups = #topic #845 Wiki deprecation status .fpc 845 https://pagure.io/packaging-committee/issue/845 #topic #859 Scriptlet to replace a directory: try delete first? .fpc 859 https://pagure.io/packaging-committee/issue/859 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at: https://pagure.io/packaging-committee/issues?status=Open=meeting If you would like to add something to this agenda, you can: Please add: https://pagure.io/packaging-committee/issue/889 https://pagure.io/packaging-committee/issue/887 https://pagure.io/packaging-committee/issue/886 Thanks. -- 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
Re: Upgrade to F30 gone wrong
On Wed, May 8, 2019, 4:50 AM Panu Matilainen wrote: > > > Nicolas' point is that the rescue boot entry only works in a limited > number of scenarios. > I'm not sure which of three 'rescue' options is being discussed. grub rescue appears when normal.mod can't be loaded, and means the menu can't be displayed. This thread's bug results in this rescue. Since circa Fedora 19, there is a GRUB menu entry 'Rescue' option which boots a "no host only" initramfs. If you see the option, you don't have the bug under discussion. Install media, dvd and netinst, have a bootloader submenu option for Troubleshooting, that leads to an option Rescue a Fedora system, which actually launches anaconda with app option 'inst.rescue' that helps find, assemble and mount a Fedora installation or even just provide a shell with all the CLI programs normally available for installs including fsck, mkfs, various FS debug tools, etc. > And in some cases the rescue media IS needed to fix this particular > issue as well. For example my box never got to the grub prompt at all, > it was busy reboot-looping, probably due to negletting to reinstall grub > in almost a decade. Others have pointed out other "completely broken" > symptoms. > I don't think that's this bug. It suggests the core.img embedded in either the MBR gap or BIOSBoot partition has a serious bug or that the computer firmware has a serious bug. Somehow is can neither load blscfg.mod (this bug) and can't run it's own rescue mode (not this bug). That would be super tedious to track down. And interestingly, would potentially be masked by always updating the bootloader between major upgrades (makes bootloader a moving Target). But if no one ever tracks it down, which includes the even more tedious requirement of localy building GRUB from source and reproducing the bug (because Fedora's GRUB is so substantially modified from upstream that upstream will always reject Fedora bugs), it won't get fixed. I admit, we've already failed if we're at grub rescue, letter alone in a reboot cycle. But the latter sounds hardware (firmware) specific. Difficult no matter what. > Really, if you don't even get a menu from grub, how many people are > going to be able to work it from there? I think 1 in 10. Just a guess. That's probably generous. Even if there was another > computer comfortably nearby for googling, I wouldn't bother even trying. > Much easier to grab that rescue image, which thank goodness is there still. I don't know what rescue image is. The bug this thread is about, if you hit it, you do not get a GRUB menu. To me, rescue image means install media with Rescue boot option i.e. anaconda inst.rescue. -- 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
Fedora Rawhide-20190508.n.0 compose check report
Missing expected images: Atomichost raw-xz x86_64 Atomichost qcow2 x86_64 Compose FAILS proposed Rawhide gating check! 7 of 47 required tests failed openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 16/146 (x86_64), 2/24 (i386), 1/2 (arm) ID: 397887 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller **GATING** URL: https://openqa.fedoraproject.org/tests/397887 ID: 397888 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart **GATING** URL: https://openqa.fedoraproject.org/tests/397888 ID: 397891 Test: x86_64 Server-dvd-iso realmd_join_cockpit URL: https://openqa.fedoraproject.org/tests/397891 ID: 397892 Test: x86_64 Server-dvd-iso realmd_join_sssd **GATING** URL: https://openqa.fedoraproject.org/tests/397892 ID: 397893 Test: x86_64 Server-dvd-iso server_freeipa_replication_master URL: https://openqa.fedoraproject.org/tests/397893 ID: 397894 Test: x86_64 Server-dvd-iso server_freeipa_replication_replica URL: https://openqa.fedoraproject.org/tests/397894 ID: 397895 Test: x86_64 Server-dvd-iso server_freeipa_replication_client URL: https://openqa.fedoraproject.org/tests/397895 ID: 397901 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/397901 ID: 397918 Test: x86_64 Workstation-live-iso desktop_browser **GATING** URL: https://openqa.fedoraproject.org/tests/397918 ID: 397924 Test: x86_64 Workstation-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/397924 ID: 397927 Test: i386 Workstation-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/397927 ID: 397931 Test: x86_64 KDE-live-iso install_no_user **GATING** URL: https://openqa.fedoraproject.org/tests/397931 ID: 397937 Test: x86_64 KDE-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/397937 ID: 397944 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/397944 ID: 397956 Test: x86_64 universal install_anaconda_text **GATING** URL: https://openqa.fedoraproject.org/tests/397956 ID: 398013 Test: x86_64 universal upgrade_2_desktop_64bit URL: https://openqa.fedoraproject.org/tests/398013 ID: 398019 Test: x86_64 universal install_cyrillic_language URL: https://openqa.fedoraproject.org/tests/398019 ID: 398023 Test: x86_64 universal install_european_language URL: https://openqa.fedoraproject.org/tests/398023 ID: 398029 Test: i386 universal install_repository_http_graphical **GATING** URL: https://openqa.fedoraproject.org/tests/398029 Soft failed openQA tests: 3/24 (i386), 4/146 (x86_64) (Tests completed, but using a workaround for a known bug) ID: 397904 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/397904 ID: 397905 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/397905 ID: 397916 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/397916 ID: 397923 Test: x86_64 Workstation-boot-iso memory_check@uefi URL: https://openqa.fedoraproject.org/tests/397923 ID: 397928 Test: i386 Workstation-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/397928 ID: 398012 Test: x86_64 universal upgrade_2_minimal_64bit URL: https://openqa.fedoraproject.org/tests/398012 ID: 398014 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/398014 Passed openQA tests: 126/146 (x86_64), 19/24 (i386) Skipped non-gating openQA tests: 1 of 172 -- 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
Fedora rawhide compose report: 20190508.n.0 changes
OLD: Fedora-Rawhide-20190506.n.1 NEW: Fedora-Rawhide-20190508.n.0 = SUMMARY = Added images:1 Dropped images: 7 Added packages: 3 Dropped packages:421 Upgraded packages: 137 Downgraded packages: 0 Size of added packages: 7.29 MiB Size of dropped packages:5.90 GiB Size of upgraded packages: 5.51 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 88.98 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Minimal raw-xz aarch64 Path: Spins/aarch64/images/Fedora-Minimal-Rawhide-20190508.n.0.aarch64.raw.xz = DROPPED IMAGES = Image: Cloud_Base qcow2 s390x Path: Cloud/s390x/images/Fedora-Cloud-Base-Rawhide-20190506.n.1.s390x.qcow2 Image: Cloud_Base vmdk s390x Path: Cloud/s390x/images/Fedora-Cloud-Base-Rawhide-20190506.n.1.s390x.vmdk Image: Design_suite live i386 Path: Labs/i386/iso/Fedora-Design_suite-Live-i386-Rawhide-20190506.n.1.iso Image: Container_Base docker s390x Path: Container/s390x/images/Fedora-Container-Base-Rawhide-20190506.n.1.s390x.tar.xz Image: Python_Classroom raw-xz armhfp Path: Labs/armhfp/images/Fedora-Python-Classroom-armhfp-Rawhide-20190506.n.1-sda.raw.xz Image: Cloud_Base raw-xz s390x Path: Cloud/s390x/images/Fedora-Cloud-Base-Rawhide-20190506.n.1.s390x.raw.xz Image: Games live i386 Path: Labs/i386/iso/Fedora-Games-Live-i386-Rawhide-20190506.n.1.iso = ADDED PACKAGES = Package: libyang-0.16.105-1.fc31 Summary: YANG data modeling language library RPMs:libyang libyang-cpp libyang-cpp-devel libyang-devel libyang-devel-doc python3-libyang Size:7.23 MiB Package: rust-gettext-rs-0.4.1-1.fc31 Summary: GNU Gettext FFI binding for Rust RPMs:rust-gettext-rs+default-devel rust-gettext-rs+gettext-system-devel rust-gettext-rs-devel Size:29.99 KiB Package: rust-rustio-0.0.2-1.fc31 Summary: Rust API wrapper for radio-browser.info RPMs:rust-rustio+default-devel rust-rustio-devel Size:31.00 KiB = DROPPED PACKAGES = Package: ant-1.10.5-1.module_f28+3873+06cd63fa Summary: Java build tool RPMs:ant ant-antlr ant-apache-bcel ant-apache-bsf ant-apache-log4j ant-apache-oro ant-apache-regexp ant-apache-resolver ant-apache-xalan2 ant-commons-logging ant-commons-net ant-javamail ant-jdepend ant-jmf ant-jsch ant-junit ant-lib ant-swing ant-testutil ant-xz Size:3.22 MiB Package: antlr-2.7.7-56.module_f28+3872+5b76729e Summary: ANother Tool for Language Recognition RPMs:antlr-C++-doc antlr-tool python2-antlr Size:7.05 MiB Package: aopalliance-1.0-17.module_f28+3939+dc18cd75 Summary: Java/J2EE AOP standards RPMs:aopalliance Size:16.06 KiB Package: apache-commons-cli-1.4-4.module_f28+3939+dc18cd75 Summary: Command Line Interface Library for Java RPMs:apache-commons-cli Size:72.81 KiB Package: apache-commons-codec-1.11-3.module_f28+3939+dc18cd75 Summary: Implementations of common encoders and decoders RPMs:apache-commons-codec Size:287.44 KiB Package: apache-commons-io-1:2.6-3.module_f28+3939+dc18cd75 Summary: Utilities to assist with developing IO functionality RPMs:apache-commons-io Size:222.54 KiB Package: apache-commons-lang3-3.7-3.module_f28+3939+dc18cd75 Summary: Provides a host of helper utilities for the java.lang API RPMs:apache-commons-lang3 Size:481.69 KiB Package: apache-commons-logging-1.2-13.module_f28+3872+5b76729e Summary: Apache Commons Logging RPMs:apache-commons-logging Size:170.82 KiB Package: apache-commons-net-3.6-3.module_f28+3872+5b76729e Summary: Internet protocol suite Java library RPMs:apache-commons-net Size:295.74 KiB Package: atinject-1-28.20100611svn86.module_f28+3939+dc18cd75 Summary: Dependency injection specification for Java (JSR-330) RPMs:atinject Size:19.03 KiB Package: bcel-6.2-2.module_f28+3872+5b76729e Summary: Byte Code Engineering Library RPMs:bcel Size:616.56 KiB Package: bsf-2.4.0-30.module_f28+3872+5b76729e Summary: Bean Scripting Framework RPMs:bsf Size:108.47 KiB Package: c-ares-1.15.0-3.module_f31+3902+92dfb6c9 Summary: A library that performs asynchronous DNS operations RPMs:c-ares c-ares-devel Size:2.13 MiB Package: cdi-api-1.2-8.module_f28+3939+dc18cd75 Summary: CDI API RPMs:cdi-api Size:68.52 KiB Package: community-mysql-5.6.39-2.module_f31+3355+9ac64843 Summary: MySQL client programs and shared libraries RPMs:community-mysql community-mysql-bench community-mysql-common community-mysql-devel community-mysql-embedded community-mysql-embedded-devel community-mysql-errmsg community-mysql-libs community-mysql-server community-mysql-test Size:234.75 MiB Package: cri-o-2:1.11.8-1.git71cc465.module_f31+3270+f6ef9413 Summary: Kubernetes Container Runtime Interface for OCI-based containers RPMs:conmon cri-o Size:61.28 MiB Package: cri-tools-1.11.1-2.gitedabfb5.module_f31+3270+f6ef9413 Summary: CLI and validation tools for Container Runtime Interface RPMs:cri-tools Size:31.77 MiB
Schedule for Thursday's FPC Meeting (2019-05-09 16:00 UTC)
Following is the list of topics that will be discussed in the FPC meeting Thursday at 2019-05-09 16:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. uitime): = Day: Thursday == 2019-05-09 09:00 PDT US/Pacific 2019-05-09 12:00 EDT --> US/Eastern <-- 2019-05-09 16:00 UTC UTC 2019-05-09 17:00 BST Europe/London 2019-05-09 18:00 CEST Europe/Berlin 2019-05-09 18:00 CEST Europe/Paris 2019-05-09 21:30 IST Asia/Calcutta New Day: Friday - 2019-05-10 00:00 HKT Asia/Hong_Kong 2019-05-10 00:00 +08 Asia/Singapore 2019-05-10 01:00 JST Asia/Tokyo 2019-05-10 02:00 AEST Australia/Brisbane Links to all tickets below can be found at: https://pagure.io/packaging-committee/issues?status=Open=meeting = Followups = #topic #845 Wiki deprecation status .fpc 845 https://pagure.io/packaging-committee/issue/845 #topic #859 Scriptlet to replace a directory: try delete first? .fpc 859 https://pagure.io/packaging-committee/issue/859 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at: https://pagure.io/packaging-committee/issues?status=Open=meeting If you would like to add something to this agenda, you can: * Reply to this e-mail * File a new ticket at: https://pagure.io/packaging-committee * E-mail me directly * Bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Test-Announce] Fedora 31 Rawhide 20190508.n.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 31 Rawhide 20190508.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: lorax - 20190505.n.0: lorax-31.4-1.fc31.src, 20190508.n.0: lorax-31.5-1.fc31.src pungi - 20190505.n.0: pungi-4.1.36-1.fc31.src, 20190508.n.0: pungi-4.1.36-3.fc31.src Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/31 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190508.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190508.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190508.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190508.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190508.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190508.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190508.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer ___ 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 ___ 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 1707920] perl-Array-Diff-0.08 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1707920 Paul Howarth changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-Array-Diff-0.08-1.fc31 Resolution|--- |RAWHIDE Last Closed||2019-05-08 19:04:30 --- Comment #1 from Paul Howarth --- https://koji.fedoraproject.org/koji/taskinfo?taskID=34729368 -- 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: Docker and user namespaces on F30
> Which looks even stranger. > > I see we don't have the same version of docker. I have version 18.06.3, > build d7080c1. Did you install docker from > https://docs.docker.com/install/ ? Yes, for docker-ce I installed it from the page's Linux/Fedora page when I used Fedora 29. If you are fine to remove all the images, try below one. $ sudo systemctl stop docker $ cd /var/lib/ $ sudo rm -rf docker $ sudo systemctl start docker <= recreate initial /var/lib/docker $ docker run -it --rm docker.io/php:7-fpm-alpine sh For podman, if you have not set the rootless setting to run podman without sudo, you can try it with sudo. $ sudo podman run -it --rm docker.io/php:7-fpm-alpine sh Does below command work for you? $ docker run -t --rm docker.io/alpine uname -a Linux 828dcafd0bbe 5.0.10-300.fc30.x86_64 #1 SMP Tue Apr 30 16:22:12 UTC 2019 x86_64 Linux > However, dk run --userns=host -it --rm docker.io/php:7-fpm-alpine sh > works fine. So it seems to be limited to user namespaces. What is dk command? -- 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 1707920] New: perl-Array-Diff-0.08 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1707920 Bug ID: 1707920 Summary: perl-Array-Diff-0.08 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Array-Diff Keywords: FutureFeature, Triaged Assignee: emman...@seyman.fr Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: berra...@redhat.com, emman...@seyman.fr, p...@city-fan.org, perl-devel@lists.fedoraproject.org, trem...@tremble.org.uk Target Milestone: --- Classification: Fedora Latest upstream release: 0.08 Current version/release in rawhide: 0.07-29.fc30 URL: http://search.cpan.org/dist/Array-Diff/ 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/2652/ -- 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 1686595] rt-4.4.4 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1686595 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #1 from Fedora Update System --- rt-4.4.4-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-7d9d577ad2 -- 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 1686595] rt-4.4.4 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1686595 --- Comment #2 from Fedora Update System --- rt-4.4.4-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-bfc3898b2a -- 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: Attempting to contact unresponsive maintainers: dkaspar flaper87
On 5/7/19 2:47 PM, Nathan Scott wrote: > 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. Excellent. 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: Package with open and closed dual license
Oh, sorry, I hadn't thought to try searching for previous threads about VeraCrypt in particular. And, looking at it again, the dual license here is tricky, because it looks like the old TrueCrypt files are still TrueCrypt-licensed, while the new files are Apache-licensed. I wondered briefly about whether VeraCrypt had evolved enough that it would build if you just omitted the TrueCrypt files (unlikely) -- but worse: Many of the old TrueCrypt files have been modified, so license comments at the top claim *portions* of the file will have the old or the new license depending on who wrote which lines when. Eww :( ...Would it be allowed in RPM Fusion, then? ___ 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: Docker and user namespaces on F30
Sadly this doesn't work either. With podman, I have this error: ERRO[0004] Error pulling image ref //php:7-fpm-alpine: Error committing the finished image: error adding layer with blob "sha256:f581654c6ada4fba71ebfbfe4cd96430abe7b5dabebd92a6a62c11391a79cc9 8": Error processing tar file(exit status 1): there might not be enough IDs available in the namespace (requested 82:82 for /home/www-data): lchown /home/www-data: invalid argument Failed Error: unable to pull docker.io/php:7-fpm-alpine: unable to pull image: Error committing the finished image: error adding layer with blob "sha256:f581654c6ada4fba71ebfbfe4cd96430abe7b5dabebd92a6a62c11391a79cc9 8": Error processing tar file(exit status 1): there might not be enough IDs available in the namespace (requested 82:82 for /home/www-data): lchown /home/www-data: invalid argument Which looks even stranger. I see we don't have the same version of docker. I have version 18.06.3, build d7080c1. Did you install docker from https://docs.docker.com/install/ ? -- Julien Enselme http://www.jujens.eu/ Je lun, 2019-05-06 je 16:17 +0200, Jun Aruga skribis: > Podman 1.2 and Docker CE 18.09.5 on My Fedora 30 work for your use > case. > > $ rpm -q kernel > kernel-5.0.5-200.fc29.x86_64 > kernel-5.0.10-200.fc29.x86_64 > kernel-5.0.10-300.fc30.x86_64 > > $ podman --version > podman version 1.2.0 > > $ podman run -it --rm docker.io/php:7-fpm-alpine sh > /var/www/html # uname -a > Linux f8b9dafd7816 5.0.10-300.fc30.x86_64 #1 SMP Tue Apr 30 16:22:12 > UTC 2019 x86_64 Linux > > $ docker --version > Docker version 18.09.5, build e8ff056 > > $ docker run -it --rm docker.io/php:7-fpm-alpine sh > /var/www/html # uname -a > Linux 936e897b0a9b 5.0.10-300.fc30.x86_64 #1 SMP Tue Apr 30 16:22:12 > UTC 2019 x86_64 Linux > > On Sat, May 4, 2019 at 5:05 PM Julien Enselme > wrote: > > Hi, > > > > I just updated to F30 and my docker setup with user namespaces > > doesn't > > work anymore. When I try to run: > > docker run -it --rm docker.io/php:7-fpm-alpine sh > > I get this error: > > docker: Error response from daemon: OCI runtime create failed: > > container_linux.go:348: starting container process caused > > "process_linux.go:402: container init caused \"rootfs_linux.go:58: > > mounting \\\"mqueue\\\" to rootfs > > \\\"/var/lib/docker/1000.1001/btrfs/subvolumes/38ce5c87e31bbbcec010 > > db85 > > 383d1af57e8652ff4e4c411cebe0c2102a36a020\\\" at \\\"/dev/mqueue\\\" > > caused \\\"operation not permitted\\\"\"": unknown. > > > > I tried to disable SELinux with setenforce 0 but got the same > > result. > > > > However, dk run --userns=host -it --rm docker.io/php:7-fpm-alpine > > sh > > works fine. So it seems to be limited to user namespaces. > > > > My kernel: 5.0.9-301.fc30.x86_64 > > > > Any ideas on where this may come from? This worked fine on F29 (and > > probably on older versions too, I have this setup for a while now). > > > > 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 > > > -- > Jun Aruga / He - His - Him > jar...@redhat.com / IRC: jaruga > ___ > 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 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
Fedora 30 Elections: Nomination period open
Today we are starting the Nomination & Campaign period during which we accept nominations to the "steering bodies" of the following teams: * FESCo (Engineering) (4 seats) [1] * Fedora Council (1 seat) [2] * Mindshare (1 seat) [3] This period is open until 2019-05-22 at 23:59:59 UTC. Candidates may self-nominate. If you nominate someone else, please check with them to ensure that they are willing to be nominated before submitting their name. The steering bodies are currently selecting interview questions for the candidates. Nominees submit their questionnaire answers via a private Pagure issue. The Election Wrangler or their backup will publish the interviews to the Community Blog before the start of the voting period. Fedora Podcast episodes will be recorded and published as well. Please note that the interview is mandatory for all nominees. Nominees not having their interview ready by end of the Interview period (2019-05-29) will be disqualified and removed from the election. As part of the campaign people may also ask questions to specific candidates on the appropriate mailing list. The full schedule of the elections is available on the Elections schedule[4]. For more information about the elections process, see the wiki[5]. [1] https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations [2] https://fedoraproject.org/wiki/Council/Nominations [3] https://fedoraproject.org/wiki/Mindshare/Nominations [4] https://fedorapeople.org/groups/schedule/f-30/f-30-elections.html [5] https://fedoraproject.org/wiki/Elections -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Fedora 30 Elections: Nomination period open
Today we are starting the Nomination & Campaign period during which we accept nominations to the "steering bodies" of the following teams: * FESCo (Engineering) (4 seats) [1] * Fedora Council (1 seat) [2] * Mindshare (1 seat) [3] This period is open until 2019-05-22 at 23:59:59 UTC. Candidates may self-nominate. If you nominate someone else, please check with them to ensure that they are willing to be nominated before submitting their name. The steering bodies are currently selecting interview questions for the candidates. Nominees submit their questionnaire answers via a private Pagure issue. The Election Wrangler or their backup will publish the interviews to the Community Blog before the start of the voting period. Fedora Podcast episodes will be recorded and published as well. Please note that the interview is mandatory for all nominees. Nominees not having their interview ready by end of the Interview period (2019-05-29) will be disqualified and removed from the election. As part of the campaign people may also ask questions to specific candidates on the appropriate mailing list. The full schedule of the elections is available on the Elections schedule[4]. For more information about the elections process, see the wiki[5]. [1] https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations [2] https://fedoraproject.org/wiki/Council/Nominations [3] https://fedoraproject.org/wiki/Mindshare/Nominations [4] https://fedorapeople.org/groups/schedule/f-30/f-30-elections.html [5] https://fedoraproject.org/wiki/Elections -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ 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
On 5/7/19 8:15 PM, Chris Murphy wrote: 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. Nicolas' point is that the rescue boot entry only works in a limited number of scenarios. And in some cases the rescue media IS needed to fix this particular issue as well. For example my box never got to the grub prompt at all, it was busy reboot-looping, probably due to negletting to reinstall grub in almost a decade. Others have pointed out other "completely broken" symptoms. Really, if you don't even get a menu from grub, how many people are going to be able to work it from there? Even if there was another computer comfortably nearby for googling, I wouldn't bother even trying. Much easier to grab that rescue image, which thank goodness is there still. - Panu - ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Attempting to contact unresponsive maintainers: dkaspar flaper87
On Wed, May 08, 2019 at 07:47:20AM +1000, Nathan Scott wrote: > 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. Yes, I sponsored Flavio a while back, but I'm sure he won't have the time to dedicate the necessary love to his packages. 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
[EPEL-devel] Wordpress in EPEL enter "security mode" only update
Hi, Wordpress 5.2 was released This version raise dependency on PHP 5.6 (but 7.2 is recommended for performance, and to avoid some pure-PHP compatibility libraries) So this new version will only be available in Fedora repository (and later in EPEL-8) EPEL-6 and EPEL-7 will keep 5.1.x as along as possible. Remi ___ 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?
On Tue, 7 May 2019 at 23:46, Kevin Fenzi wrote: > > 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. Yes I do the Dockerhub updates, and since we did not have a full compose working in a while I did my best to at least get something out for fedora 30. The problem we have with the compose is tracked in this ticket --> https://pagure.io/releng/issue/8173 > > > 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 > > ___ > 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
