On Fri, 2019-08-02 at 19:13 +0200, Björn 'besser82' Esser wrote:
> Am Donnerstag, den 01.08.2019, 14:28 -0400 schrieb Steven A. Falco:
> > The upstream KiCAD project has requested that I remove
> > GLIBCXX_ASSERTIONS from the Fedora package, as described here:
> > https://bugs.launchpad.net/kicad/
* Pierre-Yves Chibon:
> On Sat, Aug 03, 2019 at 11:20:35AM -0700, Kevin Fenzi wrote:
>> On 8/2/19 11:13 AM, Florian Weimer wrote:
>> > * Pierre-Yves Chibon:
>> >
>> >> When you run `fedpkg build` on Rawhide, your package will be built in
>> >> a new koji tag (which will be the default target for
On Sun, Aug 4, 2019 at 2:36 PM Iñaki Ucar wrote:
>
> On Sun, 4 Aug 2019 at 15:01, Rex Dieter wrote:
> >
> > Iñaki Ucar wrote:
> >
> > > On Sun, 4 Aug 2019 at 01:21, Miro Hrončok wrote:
> > >>
> > >> > So the question is: should I add "Obsoletes: pkg-devel < $new_version"
> > >> > to pkg's SPEC?
On Sat, Aug 03, 2019 at 11:20:35AM -0700, Kevin Fenzi wrote:
> On 8/2/19 11:13 AM, Florian Weimer wrote:
> > * Pierre-Yves Chibon:
> >
> >> When you run `fedpkg build` on Rawhide, your package will be built in
> >> a new koji tag (which will be the default target for Rawhide). The
> >> package wil
On Sat, Aug 03, 2019 at 06:52:55PM +, Gwyn Ciesla via devel wrote:
>I'll take the python packagesand igraph.
igraph and python-igraph are yours, thanks! :)
Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an ema
How does it deal with rich dependencies? Does it take conflicts into the
account? What about multiple provides which satisfy dependency?
On Sun, Aug 4, 2019, 19:41 Adam Samalik wrote:
> I wrote a script to visualise dependencies of RPM installations [1]. It
> supports file paths and container im
On Sun, 4 Aug 2019 at 15:01, Rex Dieter wrote:
>
> Iñaki Ucar wrote:
>
> > On Sun, 4 Aug 2019 at 01:21, Miro Hrončok wrote:
> >>
> >> > So the question is: should I add "Obsoletes: pkg-devel < $new_version"
> >> > to pkg's SPEC? Is this a proper use of "Obsoletes"?
> >>
> >> Yes. Exactly a right
On Sun, 4 Aug 2019 at 16:21, Sam Varshavchik wrote:
>
> I'm well aware of the alternatives. That's not the point.
>
> The point is that there's nothing wrong with this specific form of existing
> code that now throws exceptions when the hardened build gets turned on.
> There is no buffer overruns,
I wrote a script to visualise dependencies of RPM installations [1]. It
supports file paths and container images as an input.
The script generates a graph of packages and their relations including
sizes of all individual packages and some basic clustering. Clicking on a
package highlights its rela
Whoop this is great!
But I wonder why the scratch build sizes have gone up this dramatically in
f31?
On Sun, Aug 4, 2019 at 10:59 AM Adam Samalik wrote:
>
>
> On Sat, Aug 3, 2019 at 11:24 PM Clement Verna
> wrote:
>
>> On Sat, 3 Aug 2019 at 20:34, Zbigniew Jędrzejewski-Szmek
>> wrote:
>> >
>
>> On Sat, 3 Aug 2019 at 20:34, Zbigniew Jędrzejewski-Szmek
>> wrote:
>> >
>> > On Thu, Aug 01, 2019 at 10:25:55AM +0200, Adam Samalik wrote:
>> > > I've already done some experiments with that. I used multi-stage builds
>> > > with podman, but it's the same in principle. And yes, the sizes are
>>
OLD: Fedora-Rawhide-20190802.n.1
NEW: Fedora-Rawhide-20190804.n.0
= SUMMARY =
Added images:0
Dropped images: 0
Added packages: 9
Dropped packages:3
Upgraded packages: 100
Downgraded packages: 1
Size of added packages: 13.15 MiB
Size of dropped packages
Georg Sauthoff writes:
> I ended up tweaking my code to avoid the assertions, rather than disabling
> them. For this particular situation, my original change was to try
>
> std::copy(&foo[0], &foo[0]+foo.size(), std::back_insert_iterator{bar});
>
> But that still tripped the assertion when the f
No missing expected images.
Compose FAILS proposed Rawhide gating check!
13 of 45 required tests failed, 8 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Unsatisfied gating requirements that could not be mapped to openQA tests:
FAILED: compose.cl
Kevin Fenzi wrote:
> If the build has gone out in a rawhide compose, you need to just push
> out a fixed build. That could be something to fix it, or adding an Epoch
> and downgrading back to a previous version.
>
> If it's not yet gone out in a compose, you can file a releng ticket to
> have some
Iñaki Ucar wrote:
> On Sun, 4 Aug 2019 at 01:21, Miro Hrončok wrote:
>>
>> > So the question is: should I add "Obsoletes: pkg-devel < $new_version"
>> > to pkg's SPEC? Is this a proper use of "Obsoletes"?
>>
>> Yes. Exactly a right thing to do.
>
> Thanks, Miro. Then, I suggest to add this parti
On Sun, 4 Aug 2019 at 01:21, Miro Hrončok wrote:
>
> > So the question is: should I add "Obsoletes: pkg-devel < $new_version"
> > to pkg's SPEC? Is this a proper use of "Obsoletes"?
>
> Yes. Exactly a right thing to do.
Thanks, Miro. Then, I suggest to add this particular case to the
documentatio
On Sat, Aug 3, 2019 at 11:24 PM Clement Verna
wrote:
> On Sat, 3 Aug 2019 at 20:34, Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > On Thu, Aug 01, 2019 at 10:25:55AM +0200, Adam Samalik wrote:
> > > I've already done some experiments with that. I used multi-stage builds
> > > with podman, but it's
18 matches
Mail list logo