libqalculate soname bump is happening with v3.8.0.
The following packages are affected -
- qalculate-gtk
- plasma-workspace
- step
- cantor
I will rebuild all these packages on rawhide.
qalculate-kde will also affected but this is already FTBFS. So, I won't
touch this.
Mukundan.
libqalculate soname bump is happening with v3.6.0.
The following packages are affected -
plasma-workspace
step
cantor
qalculate-kde
I will rebuild all the packages on rawhide.
Mukundan.
signature.asc
Description: OpenPGP digital signature
___
On Mon, 2019-08-26 at 17:47 -0400, Mukundan Ragavan wrote:
> libqalculate soname bump is happening with v3.3 (libqalculate.so.21.2.0).
>
> The following packages are affected -
>
> plasma-workspace
> step
> cantor
> qalculate-kde
>
> I will rebuild the packages on both rawhide and F31 tomorrow.
libqalculate soname bump is happening with v3.3 (libqalculate.so.21.2.0).
The following packages are affected -
plasma-workspace
step
cantor
qalculate-kde
I will rebuild the packages on both rawhide and F31 tomorrow.
Maintainers, if you do not want me to touch F31, please let me know.
libqalculate soname bump is happening with update to v3.1. The following
packages are affected -
plasma-workspace
step
cantor
qalculate-kde
I will rebuild these in the coming days.Note that qalculate-kde is FTBFS
right now.
signature.asc
Description: OpenPGP digital signature
libqalculate soname bump is happening with v2.9. The following
packages are affected -
plasma-workspace
step
cantor
qalculate-kde
I will rebuild these packages and file bug reports if needed.
Mukundan.
signature.asc
Description: OpenPGP digital signature
Since 2.4.0 is out, soname change will be to libqalculate.so.16. I will submit
pull requests for the affected packages. I might miss F28.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
I will be updating libqalculate to the latest upstream release (v2.3.0 instead
of 2.2.1 as per my previous email). This involves a soname change.
The following packages are affected -
plasma-workspace
step
cantor
qalculate-kde
I will build qalculate and the affected packages in rawhide and
Adam Williamson wrote:
> This cycle was actually kind of an interesting case, because on the one
> hand, there's a pretty good argument that we were in a very bad state
> at freeze time this cycle. On the *other* hand, one of the main reasons
> we were in a bad state is because people kept
> On Wed, 2018-03-07 at 20:46 -0500, Mukundan Ragavan wrote:
>
> Thanks for the notification.
>
> Note F28 is currently in freeze for Beta; this is a long freeze, and
> honestly, might get longer, given the current state of things. So I'm
> not sure whether it'd be optimal to have this committed
On Thu, 2018-03-08 at 10:15 -0500, Przemek Klosowski wrote:
>
> Having said that, I could see there might be a case for delaying the
> freeze before it starts, if the overall schedule is delayed for
> well-understood reasons.
This cycle was actually kind of an interesting case, because on the
On Thu, 2018-03-08 at 15:51 +0100, Kevin Kofler wrote:
> Adam Williamson wrote:
> > Note F28 is currently in freeze for Beta; this is a long freeze, and
> > honestly, might get longer, given the current state of things.
>
> IMHO, if we know that we are not in a good enough state to release, we
>
On 03/08/2018 09:51 AM, Kevin Kofler wrote:
> IMHO, if we know that we are not in a good enough state to release, we
> should delay the start of the freeze (in the current case where it has
> already started: cancel the freeze and try again later) until we are in a
> releasable state. It just
On 03/08/2018 09:51 AM, Kevin Kofler wrote:
Adam Williamson wrote:
Note F28 is currently in freeze for Beta; this is a long freeze, and
honestly, might get longer, given the current state of things.
IMHO, if we know that we are not in a good enough state to release, we
should delay the start
Adam Williamson wrote:
> Note F28 is currently in freeze for Beta; this is a long freeze, and
> honestly, might get longer, given the current state of things.
IMHO, if we know that we are not in a good enough state to release, we
should delay the start of the freeze (in the current case where it
On Wed, 2018-03-07 at 20:46 -0500, Mukundan Ragavan wrote:
> I will be updating libqalculate to the latest upstream release (v2.2.1).
> This involves a soname change. The following packages are affected.
>
> plasma-workspace
> step
> cantor
> qalculate-kde
>
> I have built all these packages for
I will be updating libqalculate to the latest upstream release (v2.2.1).
This involves a soname change. The following packages are affected.
plasma-workspace
step
cantor
qalculate-kde
I have built all these packages for rawhide and F28 in a COPR [0]. Since
we have the same versions on both
17 matches
Mail list logo
