https://bugzilla.suse.com/show_bug.cgi?id=1215172 Maintenance Automation changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1215172 https://bugzilla.suse.com/show_bug.cgi?id=1215172#c3 Smith changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #3 from Smith --- It seems very unfortunate that the package has these issues. Hopefully they'll be mitigated in the future so we can see a return of croc, but until then I've requested the removal of croc from Factory. Thank you! -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1215172 https://bugzilla.suse.com/show_bug.cgi?id=1215172#c5 --- Comment #5 from Smith --- It seems so. This was already removed in SR#111035, so I believe the issue could be closed. Thanks for the reminder! https://build.opensuse.org/request/show/1110357 -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1215172 https://bugzilla.suse.com/show_bug.cgi?id=1215172#c11 Filippo Bonazzi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |filippo.bonazzi@suse.com --- Comment #11 from Filippo Bonazzi --- Matthias, just so you're aware, this is being re-introduced to Factory in https://build.opensuse.org/request/show/1177272. Not sure whether you are satisfied with the fixes released by upstream, or if you would still want the application to be confined with e.g. nsjail in our packaging. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1215172 https://bugzilla.suse.com/show_bug.cgi?id=1215172#c16 --- Comment #16 from Matthias Gerstner --- I did not have time yet to check the individual fixes that the upstream author has come up with. It happened all rather quickly, after a long time, and with a sense of rejection on the upstream author's part, so it's possible that some things might still be insufficiently addressed. I have the review of the upstream fixes on my todo list, but it don't know when I'll get around to actually do it. I will update this bug here once I have news. -- You are receiving this mail because: You are on the CC list for the bug.