On Thu, Jul 21, 2022 at 10:39:55PM +0200, Fabio Valentini wrote:
> On Wed, Jul 20, 2022 at 4:56 PM Dan Horák wrote:
> >
> > On Wed, 20 Jul 2022 16:48:02 +0200
> > Miro Hrončok wrote:
> >
> > > On 15. 07. 22 23:48, Ben Cotton wrote:
> > > > == Summary ==
> > > > Move the minimal architecture level
notmuch failed to build from source because of a strange test suite failure on
ppc64le:
https://koji.fedoraproject.org/koji/taskinfo?taskID=89837091
The only failing test is a pytest run on the bindings
```
T391-python-cffi: Testing python bindings (pytest)
FATAL: /builddir/build/BUILD/notmuch-
On Mi, 20.07.22 20:48, Demi Marie Obenour (demioben...@gmail.com) wrote:
> > So, in my view of the world, the kernel command line is fixated in the
> > unified kernel image (if you use systemd-stub, this already happens if
> > a .cmdline PE section exists, and SecureBoot is on). If you want to
> >
On Do, 21.07.22 05:56, Colin Walters (walt...@verbum.org) wrote:
> >> We recently did
> >> https://github.com/coreos/fedora-coreos-config/pull/1840 for Fedora
> >> CoreOS (more background:
> >> https://github.com/coreos/fedora-coreos-tracker/issues/1244 ) and
> >> I'd like to consider applying thi
On 7/22/22 05:40, Lennart Poettering wrote:
> On Mi, 20.07.22 20:48, Demi Marie Obenour (demioben...@gmail.com) wrote:
>
>>> So, in my view of the world, the kernel command line is fixated in the
>>> unified kernel image (if you use systemd-stub, this already happens if
>>> a .cmdline PE section e
Announcing the creation of a new nightly release validation test event
for Fedora-IoT 37 RC 20220722.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_pl
Hi everyone,
This is a weekly report from the CPE (Community Platform Engineering) Team.
If you have any questions or feedback, please respond to this report or
contact us on #redhat-cpe channel on libera.chat (https://libera.chat/).
Week: 18th - 22nd of July 2022
If you wish to read this in for
On Thu, 21 Jul 2022 at 08:43, Stephen Smoogen wrote:
>
>
> On Wed, 20 Jul 2022 at 16:12, Dan Čermák
> wrote:
>
>> Hi Kevin and all,
>>
>> "Kevin P. Fleming" writes:
>>
>> > On 7/20/22 14:57, Marcus Müller wrote:
>> >> Oh! That comes as a surprise. Let me try a rebuild!
>> >>
>> >> :( I was real
Hi,
As from the pcre-8.45, the upstream stopped supporting this library. The
recommended procedure is to switch onto the new pcre2 library that has full
upstream support. [1]
As a result of this announcement, the older PCRE library in Fedora will be
retired.
Without upstream support, we don't hav
Once upon a time, Lennart Poettering said:
> Hence, I am not convinved the benefit really outweighs the effort
> here. Modifying your kernel command line is invasive, and hackish, and
> hence I think it's OK to leave it out of the model.
It may be invasive or hackish, but sometimes it is absolute
V Fri, Jul 22, 2022 at 02:24:00PM +0200, Lukas Javorsky napsal(a):
> As from the pcre-8.45, the upstream stopped supporting this library. The
> recommended procedure is to switch onto the new pcre2 library that has full
> upstream support. [1]
>
> As a result of this announcement, the older PCRE l
On Fri, Jul 22, 2022 at 2:25 PM Lukas Javorsky wrote:
>
> Hi,
>
> As from the pcre-8.45, the upstream stopped supporting this library. The
> recommended procedure is to switch onto the new pcre2 library that has full
> upstream support. [1]
>
> As a result of this announcement, the older PCRE li
On 7/22/22 08:26, Chris Adams wrote:
> Once upon a time, Lennart Poettering said:
>> Hence, I am not convinved the benefit really outweighs the effort
>> here. Modifying your kernel command line is invasive, and hackish, and
>> hence I think it's OK to leave it out of the model.
> It may be invasi
On 22/07/2022 14:24, Lukas Javorsky wrote:
As from the pcre-8.45, the upstream stopped supporting this library.
If it builds from sources we can maintain it in downstream due to a big
number of dependent packages.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
On Fri, Jul 22, 2022 at 8:25 AM Lukas Javorsky wrote:
>
> As a result of this announcement, the older PCRE library in Fedora will be
> retired.
> Without upstream support, we don't have enough capacity to keep up with the
> security and bugs-related issues, and thus we will support only the new
Thanks for all of the replies,
The list of affected packages I've provided was generated using the 'dnf
repoquery --alldeps --whatrequires pcre'
Is this command giving the right output or should I use another? If so
which one?
We will definitely discuss all of these concerns within the team and g
On Fri, Jul 22, 2022 at 03:21:02PM +0200, Lukas Javorsky wrote:
> Thanks for all of the replies,
>
> The list of affected packages I've provided was generated using the 'dnf
> repoquery --alldeps --whatrequires pcre'
> Is this command giving the right output or should I use another? If so
> which
Next failure is portmidi due to "Drop_i686_JDKs"
https://fedoraproject.org/wiki/Changes/Drop_i686_JDKs
I don't know how I missed that change proposal. I cannot even make sense of the
English in those template mails (never got any myself). This is going to be a
lot of fun ... java-17-openjdk-dev
Hi,
I'd like to take over the orphaned package dnstracer.
https://src.fedoraproject.org/rpms/dnstracer
I submitted a ticket with releng for this as there was no "take" button present.
https://pagure.io/releng/issue/10915
My username is jonathanspw
_
V Fri, Jul 22, 2022 at 03:21:02PM +0200, Lukas Javorsky napsal(a):
> The list of affected packages I've provided was generated using the 'dnf
> repoquery --alldeps --whatrequires pcre'
>
> Is this command giving the right output or should I use another? If so
> which one?
>
If I run your command o
On Mon, 2022-07-18 at 13:29 -0400, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Emacs_28
>
> This document represents a proposed Change. As part of the Changes
> process, proposals are publicly announced in order to receive
> community feedback. This proposal will only be implemented
On 22/07/22 09:08AM, Michael J Gruber wrote:
> notmuch failed to build from source because of a strange test suite failure
> on ppc64le:
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=89837091
>
> The only failing test is a pytest run on the bindings
>
> ```
> T391-python-cffi: Testing
On Fri, Jul 22, 2022 at 02:24:00PM +0200, Lukas Javorsky wrote:
> coccinelle
This is an optional dependency but we'd lose a particular feature by
disabling it. I have asked upstream if they plan to port to PCRE2.
Also the OCaml bindings they are using for regexps don't support PCRE2
(see below).
On Fri, Jul 22, 2022 at 08:24:32AM -0500, Richard Shaw wrote:
> On Fri, Jul 22, 2022 at 8:22 AM Lukas Javorsky wrote:
>
> Thanks for all of the replies,
>
> The list of affected packages I've provided was generated using the 'dnf
> repoquery --alldeps --whatrequires pcre'
> Is th
* Lukas Javorsky [22/07/2022 14:24] :
>
> perl-HTML-Template-Pro
I'll build against pcre2 in the coming days (probably this weekend).
Emmanuel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedo
On Fri, Jul 22, 2022 at 02:24:21PM -0500, Maxwell G via devel wrote:
> On 22/07/22 09:08AM, Michael J Gruber wrote:
> > notmuch failed to build from source because of a strange test suite failure
> > on ppc64le:
> >
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=89837091
> >
> > The onl
On Fri, Jul 22, 2022 at 04:26:28PM -, Jonathan Wright via devel wrote:
> Hi,
>
> I'd like to take over the orphaned package dnstracer.
> https://src.fedoraproject.org/rpms/dnstracer
>
> I submitted a ticket with releng for this as there was no "take" button
> present.
>
> https://pagure.i
Hi,
Lukas Javorsky writes:
> i3
> i3-gaps
there is a patch to make i3 (and thus i3-gaps) compatible with pcre2 [1],
which has been merged upstream. I can cherry pick it and rebuild i3 in
Rawhide without requiring pcre, if this is urgent. Otherwise I'd rather
wait for the next upstream release.
David Malcolm writes:
> On Mon, 2022-07-18 at 13:29 -0400, Ben Cotton wrote:
>> https://fedoraproject.org/wiki/Changes/Emacs_28
>>
>> This document represents a proposed Change. As part of the Changes
>> process, proposals are publicly announced in order to receive
>> community feedback. This pr
On Fri, 2022-07-22 at 22:50 +0200, Dan Čermák wrote:
> David Malcolm writes:
>
> > On Mon, 2022-07-18 at 13:29 -0400, Ben Cotton wrote:
> > > https://fedoraproject.org/wiki/Changes/Emacs_28
> > >
> > > This document represents a proposed Change. As part of the Changes
> > > process, proposals ar
On 22/07/22 10:24PM, Fabio Valentini wrote:
> the script that determines leaf packages in the Rust SIG
Can you provide a link to this?
> $ (dnf repoquery --whatrequires pcre ; dnf repoquery --whatrequires
> pcre-cpp ; dnf repoquery --whatrequires pcre-devel ; dnf repoquery
> --whatrequires pcre-s
(It seems my previous message didn't send properly...)
On 22/07/22 10:24PM, Fabio Valentini wrote:
> the script that determines leaf packages in the Rust SIG
Can you provide a link to this?
> $ (dnf repoquery --whatrequires pcre ; dnf repoquery --whatrequires
> pcre-cpp ; dnf repoquery --whatre
Fabio Valentini wrote:
> Given that there's a very long list of affected packages, just
> dropping the package in a few weeks would have disastrous effects on
> Fedora.
> I also see core components of several Editions and Spins on that list,
> so I assume just dropping pcre would also make QA, Rele
On Fri, Jul 22, 2022 at 11:47 PM Maxwell G wrote:
>
> On 22/07/22 10:24PM, Fabio Valentini wrote:
> > the script that determines leaf packages in the Rust SIG
>
> Can you provide a link to this?
I can, now that I've published it (again):
https://pagure.io/ironthree/fedora-rust-sig-leaf-check
It'
On Sat, Jul 23, 2022 at 12:23 AM Kevin Kofler via devel
wrote:
>
> Fabio Valentini wrote:
> > Given that there's a very long list of affected packages, just
> > dropping the package in a few weeks would have disastrous effects on
> > Fedora.
> > I also see core components of several Editions and S
Fabio Valentini wrote:
> It would be entirely possible to mark the package as deprecated, but
> also give it to new maintainers.
Why not leave the decision to the new maintainers then?
I do not see a good reason to prevent adding software depending on pcre (1)
as long as somebody maintains pcre
On Wed, Jul 20, 2022 at 2:10 PM Dan Čermák
wrote:
> Sorry for breaking your packages Jerry. Maybe we should add some gating
> tests to prevent this kind of breakage in the future. Would you have
> some details what happened?
Bigloo was easy to fix, so no problem there. The pvs-sbcl package
uses
On Mon, 18 Jul 2022, Marcus Müller wrote:
Since the pgtk toolkit supports both X and wayland under the hood, I'd very
much propose that we do not only package an emacs-pgtk binary, but also, that
it becomes what you get by default (i.e. when you install and run `emacs`).
The emacs developers
38 matches
Mail list logo
