Re: Auto-filing of FTBFS bugs gone wild

Hi, On 19-07-18 17:42, Igor Gnatenko wrote: On Thu, Jul 19, 2018 at 5:33 PM Hans de Goede mailto:hdego...@redhat.com>> wrote: Hi All, I've just got 20 bugs auto-filed against packages which I co-maintain and that is just for packages starting with the letter 'a'. A quick check

Re: Packages which needlessly use %defattr

Dne 4.7.2018 v 12:18 Zbigniew Jędrzejewski-Szmek napsal(a): > What about just doing a mass specfile update now? I think asking > individual maintainers to fix their packages isn't worth their > time. -1 I like the Jason attitude much more. It gives time to discuss it. To find false positives. It

koschei build gone?

Hi, I've filled this bugzilla: [0] and I clearly remember seeing a failed build in koschei - I've even linked it in the BZ [1]. Yet the URL now returns 404. Last build in koschei for python3 is 3 days older than the bugreport. What happens? Are certain builds deleted for various reasons? Or

Re: koschei build gone?

On 07/30/2018 11:19 AM, Miro Hrončok wrote: > Hi, > > I've filled this bugzilla: [0] and I clearly remember seeing a failed > build in koschei - I've even linked it in the BZ [1]. > > Yet the URL now returns 404. > > Last build in koschei for python3 is 3 days older than the bugreport. > > What

Re: koschei build gone?

On 30.7.2018 12:42, Mikolaj Izdebski wrote: On 07/30/2018 11:19 AM, Miro Hrončok wrote: Hi, I've filled this bugzilla: [0] and I clearly remember seeing a failed build in koschei - I've even linked it in the BZ [1]. Yet the URL now returns 404. Last build in koschei for python3 is 3 days olde

Re: koschei build gone?

On 07/30/2018 01:49 PM, Miro Hrončok wrote: > On 30.7.2018 12:42, Mikolaj Izdebski wrote: >> On 07/30/2018 11:19 AM, Miro Hrončok wrote: >>> Hi, >>> >>> I've filled this bugzilla: [0] and I clearly remember seeing a failed >>> build in koschei - I've even linked it in the BZ [1]. >>> >>> Yet the UR

Re: koschei build gone?

On 30.7.2018 13:54, Mikolaj Izdebski wrote: I would found it less confusiong if they are kept in the DB but marked them "stalled -> canceled"? For example here at least one architecture failed and even the fact that the build was stalled is interesting. Agreed. Can you file upstream issue at [1

Re: Golang SIG for Fedora

Hi, I'm obviously interested, even though I'm not available all year round -- Nicolas Mailhot ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://ge

Re: Rust SIG

Do you plan any hackfest during Flock? On 07/27/2018 04:04 PM, Igor Gnatenko wrote: > Hello, > > it seems to be a week of SIG announcements, so why shouldn't I share that > we also have Rust SIG . > > At this point we have over 400 crates packaged, few a

Re: Packages which needlessly use %defattr

On Mon, Jul 30, 2018 at 11:01 AM Miroslav Suchý wrote: > Dne 4.7.2018 v 12:18 Zbigniew Jędrzejewski-Szmek napsal(a): > > What about just doing a mass specfile update now? I think asking > > individual maintainers to fix their packages isn't worth their > > time. > > -1 > > I like the Jason attitu

Active but unresponsive maintainer: Peter Lemenkov

Hello, Peter Lemenkov [0] is an active packager (he submitted a new erlang build to bodhi an hour ago) but I was unable to contact him for the last two months. I first "encountered" him when he used his rights as provenpackager to merge some PRs on the elixir package, without thoughts for the

Re: Packages which use the BuildRoot: directive

On 07/14/2018 12:47 AM, Kevin Fenzi wrote: On 07/12/2018 07:45 AM, Miro Hrončok wrote: I second that. When we mass filled PRs with python2 related changes it was always a Red Hat maintained software, where people were basically telling us: "no, we won't accept your PR here, we maintain the spec

Self Introduction

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

Re: Active but unresponsive maintainer: Peter Lemenkov

Hey, Sorry for the absence - I'm still around. 2018-07-30 15:34 GMT+02:00 Timothée Floure : > > Hello, > > Peter Lemenkov [0] is an active packager (he submitted a new erlang > build to bodhi an hour ago) but I was unable to contact him for the last > two months. > > I first "encountered" him when

Re: Self Introduction: Rob Brown

On 07/29/2018 08:59 PM, Robert Brown wrote: > I'm new to fedora 28, and I am interested in participating in the > package authoring and maintenance. I'm coming from Debian. Welcome aboard! You can read about becoming a packager here: https://fedoraproject.org/wiki/Join_the_package_collection_mai

Re: Rust SIG

On Mon, Jul 30, 2018 at 2:31 PM, Martin Sehnoutka wrote: > Do you plan any hackfest during Flock? > We are booked out for schedule hacks during Flock, however there is usually some space on the edges for impromptu meetings. regards, bex > > On 07/27/2018 04:04 PM, Igor Gnatenko wrote: > > He

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

On 21/07/18 18:52 +0200, Mark Wielaard wrote: Hi, The elfutils tools can demangle C++ symbols through the standard _cxa_demangle interface. The elfutils tools are written in C and so simply link with -lstdc++ to get access to __cxa_demangle. You should be able to use -lsupc++ if you only want

Re: Rust SIG

On Mon, 30 Jul 2018 at 17:45, Brian (bex) Exelbierd wrote: > > > > On Mon, Jul 30, 2018 at 2:31 PM, Martin Sehnoutka wrote: >> >> Do you plan any hackfest during Flock? > > > We are booked out for schedule hacks during Flock, however there is usually > some space on the edges for impromptu meeti

Re: Rust SIG

On Mon, Jul 30, 2018 at 5:49 PM, Clement Verna wrote: > On Mon, 30 Jul 2018 at 17:45, Brian (bex) Exelbierd > wrote: > > > > > > > > On Mon, Jul 30, 2018 at 2:31 PM, Martin Sehnoutka > wrote: > >> > >> Do you plan any hackfest during Flock? > > > > > > We are booked out for schedule hacks durin

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

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

Fedora rawhide compose report: 20180730.n.0 changes

OLD: Fedora-Rawhide-20180729.n.0 NEW: Fedora-Rawhide-20180730.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 1 Dropped packages:4 Upgraded packages: 268 Downgraded packages: 0 Size of added packages: 20.33 MiB Size of dropped packages

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

On 26/07/18 12:45 -0400, R P Herrold wrote: On Thu, 26 Jul 2018, Florian Weimer wrote: I would like to request a change of the Packaging Guidelines, advising packagers not to interpose malloc. The use here of 'interpose' is unclear to me -- are you saying 'substitute a different' ? The usua

Re: [atomic-devel] Starting a Container SIG

On Mon, 30 Jul 2018 at 17:59, Giuseppe Scrivano wrote: > > I'm also interested. > > Regards, > Giuseppe > > > Jeff Ligon writes: > > > I too would like to be a part of this but I’m not sure how much I’d be able > > to help. > > > > On Fri, Jul 27, 2018 at 1:29 PM Owen Taylor wrote: > > > > I'm

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

On 26/07/18 22:34 +0200, Florian Weimer wrote: http://www.erahm.org/2016/03/24/minimum-alignment-of-allocation-across-platforms/ Oh dear, this is worrying. I'm adding more places in libstdc++ where the std::lib assumes that memory obtained from malloc will always be aligned to alignof(max_alig

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

On Mon, 30 Jul 2018, Jonathan Wakely wrote: > On 26/07/18 12:45 -0400, R P Herrold wrote: > > The use here of 'interpose' is unclear to me -- are you saying > > 'substitute a different' ? > > The usual way to replace 'malloc' is via ELF symbol interposition: > https://www.airs.com/blog/archives/

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

On 25/07/18 13:25 -0400, Scott Talbert wrote: On Wed, 25 Jul 2018, Wolfgang Stoeggl wrote: Hello, a recent F28 update build of poedit [1] shows the following message after starting: Warning: Mismatch between the program and library build versions detected. The library used 3.0 (wchar_t,compil

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

On Jul 27, 2018, at 9:58 AM, Owen Taylor wrote: On Fri, Jul 27, 2018 at 9:44 AM, Florian Weimer wrote: > On 07/27/2018 03:33 PM, John Reiser wrote:The key principle is that > sizeof(foo) must be the stride of an array of foo, > > and the array must guarantee alignment of each element in the arr

Fedora updates-20180730.1 compose check report

No missing expected images. Passed openQA tests: 2/2 (x86_64) Installed system changes in test x86_64 AtomicHost-dvd_ostree-iso install_default: System load changed from 0.07 to 0.38 Previous test data: https://openqa.fedoraproject.org/tests/261624#downloads Current test data: https://openq

Fedora Rawhide-20180730.n.0 compose check report

No missing expected images. Failed openQA tests: 10/138 (x86_64), 23/24 (i386), 1/2 (arm) New failures (same test did not fail in Rawhide-20180729.n.0): ID: 261800 Test: x86_64 universal install_scsi_updates_img URL: https://openqa.fedoraproject.org/tests/261800 ID: 261802 Test: x86_64

Intent to retire python-svg

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

Fedora testing-20180730.0 compose check report

No missing expected images. Passed openQA tests: 2/2 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedorap

Re: dokuwiki packagers unresponsive

On 2018-07-27 17:08, Matthias Runge wrote: On Fri, Jul 27, 2018 at 02:51:25AM +0100, Sérgio Basto wrote: On Thu, 2018-07-26 at 21:43 -0400, Solomon Peachy wrote: > On Thu, Jul 26, 2018 at 09:09:25PM +0200, Peter 'Pessoft' Kolínek > wrote: > > I'd like to fix some issues (including security probl

Re: dokuwiki packagers unresponsive

On Mon, 2018-07-30 at 23:07 +0200, Peter 'Pessoft' Kolínek wrote: > On 2018-07-27 17:08, Matthias Runge wrote: > > On Fri, Jul 27, 2018 at 02:51:25AM +0100, Sérgio Basto wrote: > > > On Thu, 2018-07-26 at 21:43 -0400, Solomon Peachy wrote: > > > > On Thu, Jul 26, 2018 at 09:09:25PM +0200, Peter 'Pe

[Fedocal] Reminder meeting : Modularity Office Hours

Dear all, You are kindly invited to the meeting: Modularity Office Hours on 2018-07-31 from 10:00:00 to 11:00:00 US/Eastern At fedora-modular...@chat.freenode.net The meeting will be about: This is where you ask the Fedora Modularity Team questions (and we try to answer them)! Join us on

Re: Intent to retire python-svg

Julien, I'd be happy to take some ownership. Any info? Thanks On Mon, Jul 30, 2018, 4:15 PM Julien Enselme wrote: > Hi all, > > I intend to retire python-svg. Tests are failing on Python 3.7 for a > reason I cannot figure, there was no commit during the last year and > according to `repoquery

Making Fedora secure - Package exit policy for security

Hi All, I was asked to bring this issue[1] to the developer community before FESCO makes a decision. In several instances[2] there exists packages in Fedora, in which package-maintainers did not patch security issues, for multiple reasons including 1. non-responsive maintainer 2. issue hard to pa