Adding anaconda-devel list too.
On Thu, 2021-04-29 at 12:26 +0200, jkone...@redhat.com wrote:
> Hi everyone,
>
> I've just filed a bug with all the details about the topic so we can
> start discussion there:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1955025
>
>
> I gave a short summary
Hi everyone,
I've just filed a bug with all the details about the topic so we can
start discussion there:
https://bugzilla.redhat.com/show_bug.cgi?id=1955025
I gave a short summary here.
The libxklavier library will be deprecated from a future Fedora (it
doesn't mean Fedora 35!). Anaconda and
Hello everyone,
We've created patch to require 'inst.' prefix for all Anaconda kernel
boot arguments. To make transition smoother warnings will stay there.
That means that you will get warning but the argument will be ignored
and not processed by Anaconda.
Pull request for the change:
Hello everyone,
We've created patch to require 'inst.' prefix for all Anaconda kernel
boot arguments. To make transition smoother warnings will stay there.
That means that you will get warning but the argument will be ignored
and not processed by Anaconda.
Pull request for the change:
On Wed, 2020-10-28 at 17:07 -0700, Davide Cavalca via devel wrote:
> Hello!
>
> I've been involved in the Fedora and CentOS communities for a few
> years
> now as part of the Operating Systems team at Facebook, and most
> recently helped drive the btrfs by default change proposal for Fedora
> 33.
On Thu, 2020-08-13 at 09:22 -0400, Stephen John Smoogen wrote:
> On Thu, 13 Aug 2020 at 08:58, Fabio Valentini
> wrote:
> > On Thu, Aug 13, 2020 at 2:16 PM wrote:
> > > Hello everyone,
> > >
> > > Anaconda team has decided to deprecate use of Anaconda kernel
> > > boot
> > > parameters without
Hello everyone,
Anaconda team has decided to deprecate use of Anaconda kernel boot
parameters without 'inst.' prefix. As you may already know you can
specify Anaconda kernel boot parameters both with and without 'inst.'
prefix (e.g. 'inst.repo=' or 'repo='). This deprecation means that when
you
Hi,
see my answers below.
On Tue, 2020-08-11 at 05:28 +, Jean-Baptiste Holcroft wrote:
> python-mehhttps://github.com/rhinstaller/python-meh/issues/25
This project didn't have a release in decade. I will try to look on
this soon.
> python-simpleline
>
On Thu, 2020-07-02 at 16:31 +, Nicolas Mailhot via devel wrote:
>
> Le July 2, 2020 2:47:49 PM UTC, Vitaly Zaitsev via devel <
> devel@lists.fedoraproject.org> a écrit :
> > On 02.07.2020 11:27, Nicolas Mailhot wrote:
> > > Why? Koji schedules a build. The build registers its own build
> > >
On Wed, 2020-04-01 at 09:54 -0700, Adam Williamson wrote:
> On Wed, 2020-04-01 at 15:08 +0100, Leigh Griffin wrote:
> > On Wed, Apr 1, 2020 at 2:47 PM Frank Ch. Eigler
> > wrote:
> >
> > > > [...] Nor would it have helped with the SLA requirements and
> > > > operational cost. [...]
> > >
> > >
-- snip --
>
> As for Pagure itself, I think this is where we fundamentally
> disagree.
> I think it behooves us to own and provide an experience tailored for
> our community from beginning to end. That's why we have Koji, Bodhi,
> Dist-Git, and many other tools in that part of the lifecycle. The
On Tue, 2020-03-31 at 12:47 +0200, Felix Schwarz wrote:
> Am 31.03.20 um 12:42 schrieb Kevin Kofler:
> > I think that using anything other than Free Software as the hosting
> > platform
> > for Fedora should be an absolute no go. In other words, self-hosted
> > GitLab
> > CE or Pagure, no other
Thanks a lot for clarification!
On Thu, 2020-03-05 at 15:26 +0100, Miro Hrončok wrote:
> On 05. 03. 20 15:21, jkone...@redhat.com wrote:
> > Thanks for reply, see my answers inline.
> >
> > On Thu, 2020-03-05 at 10:26 +0100, Miro Hrončok wrote:
> > > On 05. 03. 20 9:12, jkone...@redhat.com
Thanks for reply, see my answers inline.
On Thu, 2020-03-05 at 10:26 +0100, Miro Hrončok wrote:
> On 05. 03. 20 9:12, jkone...@redhat.com wrote:
> > Hello everyone,
> >
> > I'm co-maintaining package of kakoune and this package have failing
> > build on F32 and Rawhide because of tests.
> >
> >
Great advice. Thanks Daniel!
On Thu, 2020-03-05 at 10:08 +, Daniel P. Berrangé wrote:
> On Thu, Mar 05, 2020 at 10:26:56AM +0100, Miro Hrončok wrote:
> > On 05. 03. 20 9:12, jkone...@redhat.com wrote:
> > > Hello everyone,
> > >
> > > I'm co-maintaining package of kakoune and this package
Hello everyone,
I'm co-maintaining package of kakoune and this package have failing
build on F32 and Rawhide because of tests.
https://bugzilla.redhat.com/show_bug.cgi?id=1799560
As you can see in the last comment there is an upstream bug on gcc-10
which is blocking the package tests.
What I
On Thu, 2020-03-05 at 07:44 +0100, Fabio Valentini wrote:
> On Thu, Mar 5, 2020, 00:55 Martin Kolman wrote:
> >
> >
> > - Original Message -
> >
> > > From: "Neal Gompa"
> >
> > > To: "Development discussions related to Fedora" <
> > devel@lists.fedoraproject.org>
> >
> > > Sent:
On Wed, 2020-03-04 at 18:55 -0500, Martin Kolman wrote:
>
> - Original Message -
> > From: "Neal Gompa"
> > To: "Development discussions related to Fedora" <
> > devel@lists.fedoraproject.org>
> > Sent: Wednesday, March 4, 2020 11:01:43 PM
> > Subject: Re: Announcing start of DNF 5
Hi,
Thanks a lot for this change. 00:00 is always confusing to deal with.
Jirka
On Thu, 2020-02-20 at 14:04 -0500, Mohan Boddu wrote:
> Hi all,
>
> It has been brought to our attention that release freezes starting at
> 00:00 UTC has been confusing for a lot of people. So, we decided to
>
Release Engineering issue is created and change is proposed.
Thanks everyone a lot for your help with the change and with finding
the best solution!
Jirka
On Wed, 2019-11-13 at 12:40 -0800, Kevin Fenzi wrote:
> On Wed, Nov 13, 2019 at 02:59:56PM +0100, jkone...@redhat.com wrote:
> > On Wed,
On Wed, 2019-11-13 at 15:04 +0100, Miro Hrončok wrote:
> On 13. 11. 19 14:59, jkone...@redhat.com wrote:
> > Link to this thread is at the bottom of the proposal in the
> > Documentation section.
>
> oh, sorry for not noticing that.
>
No problem at all. Thanks a lot for your polishing!
On Wed, 2019-11-13 at 14:49 +0100, Miro Hrončok wrote:
> On 13. 11. 19 14:12, jkone...@redhat.com wrote:
> > Here's the draft. It would be great if you can check it out and do
> > the
> > appropriate edits to improve the Change.
> >
> >
Here's the draft. It would be great if you can check it out and do the
appropriate edits to improve the Change.
https://fedoraproject.org/wiki/Changes/Freeze_after_branching_until_compose_is_ready
Thanks Miro!
Jirka
On Mon, 2019-11-11 at 19:16 +0100, Miro Hrončok wrote:
> On 11. 11. 19 19:09,
If you think the change proposal is a better way then I'll create a
draft and before sending it I'll contact you off the list to polish it.
Thanks a lot everyone for helping. You are the best!
Jirka
On Mon, 2019-11-11 at 19:16 +0100, Miro Hrončok wrote:
> On 11. 11. 19 19:09, Miro Hrončok
On Fri, 2019-11-08 at 12:16 -0500, Ben Cotton wrote:
> On Fri, Nov 8, 2019 at 11:54 AM wrote:
> > I agree with you in general but I don't like the `brief` wording
> > here.
> > What that means exactly?
> > I would rather go with specifying a strong freeze. Meaning that the
> > freeze will
On Fri, 2019-11-08 at 07:20 -0800, Kevin Fenzi wrote:
> On Thu, Nov 07, 2019 at 08:43:44PM +0100, Miro Hrončok wrote:
> > On 07. 11. 19 18:35, Ben Cotton wrote:
> > > Here's the link to the Community Blog post that looks at the
> > > schedule options:
> > >
Hi Kevin,
Could we please create an action item list for FESCO ticket?
I guess at the end we don't want to freeze Rawhide but we should have
steps required for the branched Fedora freeze. Do you know how to do
that or could you point someone here please?
Jirka
On Sun, 2019-09-22 at 10:48
On Mon, 2019-10-28 at 14:29 -0400, Ben Cotton wrote:
> On Mon, Oct 28, 2019 at 1:43 PM Kevin Fenzi wrote:
> > On Tue, Oct 22, 2019 at 02:09:04PM +0200, jkone...@redhat.com
> > wrote:
> > > I guess it will be easier to just think about the branching date
> > > when
> > > Flock schedule is
On Mon, 2019-10-28 at 14:29 -0400, Ben Cotton wrote:
> On Mon, Oct 28, 2019 at 1:43 PM Kevin Fenzi wrote:
> > On Tue, Oct 22, 2019 at 02:09:04PM +0200, jkone...@redhat.com
> > wrote:
> > > I guess it will be easier to just think about the branching date
> > > when
> > > Flock schedule is
On Mon, 2019-10-21 at 11:19 -0700, Kevin Fenzi wrote:
> On Mon, Oct 14, 2019 at 11:59:30AM +0200, jkone...@redhat.com wrote:
> > FYI: FESCO ticket was created
> >
> > https://pagure.io/fesco/issue/2246
>
> Yeah, and we had a bit more discussion there, which we probibly
> should
> have just had
FYI: FESCO ticket was created
https://pagure.io/fesco/issue/2246
On Tue, 2019-09-17 at 15:58 +0200, jkone...@redhat.com wrote:
> Hello everyone,
>
> I'm Anaconda developer and I'm also taking care about our
> infrastructure and this Fedora release brought me a plenty of
> "unnecessary" work
On Thu, 2019-10-10 at 16:40 +0200, Lukas Ruzicka wrote:
>
> >
> > So despite providing zero feedback here, this was voted at the
> > modularity meeting:
> >
> >
> >
> > * Tagging Module Defaults into non-modular repo (sgallagh,
> > 15:41:37)
> >
> >* AGREED: We disagree with merging
On Thu, 2019-09-26 at 08:26 -0700, Brian C. Lane wrote:
> On Thu, Sep 26, 2019 at 02:25:49PM +0200, jkone...@redhat.com wrote:
> > On Fri, 2019-09-20 at 10:21 -0700, Brian C. Lane wrote:
> > > On Tue, Sep 17, 2019 at 03:09:01PM +0200, jkone...@redhat.com
> > > wrote:
>
> [snip]
>
> > > With an
On Fri, 2019-09-20 at 10:21 -0700, Brian C. Lane wrote:
> On Tue, Sep 17, 2019 at 03:09:01PM +0200, jkone...@redhat.com wrote:
> > Hello everyone,
> >
> > We (the Anaconda installer team) want to solve multiple problems by
> > one
> > solution and we want
> >
> > *YOUR FEEDBACK!*
> >
> >
> >
Hello,
Could you please also resolve breaking upgrade paths for people who
never run `dnf module` command?
I'll try to explain what happened to me. As I wrote above I never run
`dnf module` until I was forced to run `dnf module reset` to fix my
issue. I'm running Fedora 30.
If I understand
On Thu, 2019-09-19 at 14:29 -0700, Kevin Fenzi wrote:
> On 9/18/19 1:41 AM, jkone...@redhat.com wrote:
> > Hi Kevin,
> > Thanks for the explanation. See my comments below.
>
> ...snip...
>
> > > * Stop rawhide composes until we have a branched compose. This
> > > may
> > > not
> > > be needed
Hi James,
On Tue, 2019-09-17 at 09:57 -0400, James Cassell wrote:
> In general, I'd prefer to extend the ks repo command.
>
> My main concern is that the original-ks.cfg or anaconda-ks.cfg might
> no longer provide a complete description of how a particular system
> was installed, so it'd like
Hi Kevin,
Thanks for the explanation. See my comments below.
On Tue, 2019-09-17 at 09:28 -0700, Kevin Fenzi wrote:
> On 9/17/19 8:04 AM, Miro Hrončok wrote:
> > On 17. 09. 19 17:00, jkone...@redhat.com wrote:
> > > If that is not doable what about taking last Rawhide compose and
> > > mark
> > >
On Tue, 2019-09-17 at 10:38 -0400, Ben Cotton wrote:
> On Tue, Sep 17, 2019 at 10:00 AM wrote:
> > I want to ask for an improvement here. Ideal solution for me would
> > be
> > to add rule that there have to be compose to do the branching and
> > if
> > the compose fails then the branching won't
On Tue, 2019-09-17 at 16:56 +0200, Miro Hrončok wrote:
> On 17. 09. 19 16:39, jkone...@redhat.com wrote:
> > Hi Miro,
> >
> > No, I did not wanted to tell that the python 3.8 transition was
> > badly
> > executed. The problem was more about timing.
> >
> > I was fighting with Fedora 31 and we
On Tue, 2019-09-17 at 16:31 +0200, Miro Hrončok wrote:
> On 17. 09. 19 15:58, jkone...@redhat.com wrote:
> > I want to ask for an improvement here. Ideal solution for me would
> > be
> > to add rule that there have to be compose to do the branching and
> > if
> > the compose fails then the
On Tue, 2019-09-17 at 16:33 +0200, Fabio Valentini wrote:
> On Tue, Sep 17, 2019, 16:28 Miro Hrončok wrote:
> > On 17. 09. 19 15:58, jkone...@redhat.com wrote:
> >
> > > To make things even worse there was a switch to python 3.8 on
> > Rawhide
> >
> > > which wasn't really prepared (pylint did
Hi Miro,
No, I did not wanted to tell that the python 3.8 transition was badly
executed. The problem was more about timing.
I was fighting with Fedora 31 and we had Rawhide as replacement for F31
tests because the environment is usually not that different. However,
when the switch to python 3.8
Hello everyone,
I'm Anaconda developer and I'm also taking care about our
infrastructure and this Fedora release brought me a plenty of
"unnecessary" work thanks to the fact that compose for Fedora 31 was
not available until a week before beta freeze. That is too late.
I wasn't the only one who
Hello everyone,
We (the Anaconda installer team) want to solve multiple problems by one
solution and we want
*YOUR FEEDBACK!*
In short we are proposing to use custom repo files when configuring
Anaconda for image creation instead of adding even more complexity to
the kickstart repo command.
On Tue, 2019-09-10 at 16:11 +0200, Frantisek Zatloukal wrote:
> Also, I have feeling that Lutris is far superior alternative, at
> least for games :)
I don't want to be mean on PlayOnLinux but yes I agree with the above.
Jirka
> On Tue, Sep 10, 2019 at 4:01 PM Michael Cronenworth
> wrote:
> >
On Wed, 2019-09-11 at 09:54 +0530, Danishka Navin wrote:
> Is it ok to modify /etc/os-release for re-branding purpose?
Hi Danishka Navin,
Good question on a bad place. Adding Fedora devel list here, there
could be someone who is able to answer you this question.
Jirka
> On Wed, Sep 4, 2019 at
Hello everyone,
I was a maintainer of PlayOnLinux on Fedora for some time and now is
the time to say goodbye to the PlayOnLinux package. It won't be shipped
anymore on Rawhide (Fedora 32)[0].
Reason is: It's python 2 only, it won't be migrated by upstream and
there will not be any python 2 on
Hi Brian,
Thanks for all your work and special thanks for making a stable place
for the pykickstart again.
Congratulations for getting this project under your umbrella. We will
try to help you with PR reviews and other project related stuff ;).
I'm looking forward for our cooperation!
Best
Looks like it's fixed on the COPR now.
Thanks a lot for your work!
Jirka
On Fri, 2019-08-23 at 22:28 +, Marcin Zajaczkowski wrote:
> Thanks guys for your replies. It built successfully with
> "use_bootstrap_container experimental" disabled.
>
> Marcin
>
The coverage dependency was removed (F31 and Rawhide):
https://github.com/rhinstaller/anaconda/pull/2086
The main reason for the removal was that this wasn't really used in the
past and the recent Anaconda changes needs other solution to get the
correct coverage.
Jirka
On Wed, 2019-08-14 at
On Wed, 2019-07-24 at 15:29 +0200, Jiri Eischmann wrote:
> Kamil Paral píše v St 24. 07. 2019 v 13:37 +0200:
> > On Tue, Jul 23, 2019 at 7:44 PM Ben Cotton
> > wrote:
> > > https://fedoraproject.org/wiki/Changes/Anaconda_Reclaim_Disk_Space
> > >
> > > The Manual Partitioning screen supports all
On Wed, 2019-07-24 at 14:31 -0700, Adam Williamson wrote:
> On Wed, 2019-07-24 at 14:24 -0700, Adam Williamson wrote:
> > On Wed, 2019-07-24 at 15:29 +0200, Jiri Eischmann wrote:
> > > Kamil Paral píše v St 24. 07. 2019 v 13:37 +0200:
> > > > On Tue, Jul 23, 2019 at 7:44 PM Ben Cotton
> > > >
Hi everyone,
In what timezone is this deadline? :)
Regards,
Jirka
On Mon, 2019-07-22 at 10:01 -0400, Ben Cotton wrote:
> Self-Contained Change proposals for Fedora 31 must be submitted (i.e.
> placed into the ChangeReadyForWrangler category) by the end of
> tomorrow (23 July).
>
> I was on PTO
It works!
Thanks a lot for your suggestion.
Jirka
On Fri, 2019-04-19 at 20:18 +0200, Rafal Luzynski wrote:
> 18.04.2019 21:16 jkone...@redhat.com wrote:
> > [...]
> > All the information can be found here:
> >
> > https://github.com/rpm-software-management/mock/issues/250
>
> The discussion
and my knowledge
of C++ is somehow dusted. So it's hard for me to find the root cause of
these failures.
All the information can be found here:
https://github.com/rpm-software-management/mock/issues/250
[0]: https://copr.fedorainfracloud.org/coprs/jkonecny/kakoune/builds/
[1]:
https://copr
On Wed, 2019-04-10 at 19:12 +0200, Martin Kolman wrote:
> On Wed, 2019-04-10 at 11:07 +0200, Hans de Goede wrote:
> > Hi All,
> >
> > I just noticed that Fedora-Workstation-Live-x86_64-30-
> > 20190408.n.0.iso still
> > contains the dbus-daemon package even though we are using dbus-
> > broker
>
> > > First I want to ask if there were some changes in packaging which
> > > I
> > > missed so my build is failing thanks to that?
> > >
> > > Second could this be an issue of GCC 9? I also tried clang which
> > > is
> > > also supported
://copr.fedorainfracloud.org/coprs/jkonecny/kakoune/builds/
Thanks for your help,
Jirka
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code
OK, thanks Dan and Lennart for explanation.
I also think it would be better to make this happen in the systemd RPM.
It feel more suitable place for these kind of settings.
Jirka
On Thu, 2019-02-14 at 13:59 -0500, Daniel Walsh wrote:
> Ok I guess this will not effect anaconda, just affect
Hi Dan,
How the Anaconda will be affected? I'm not aware of any cgroups control
from Anaconda side or do we need change something to the installed
system to enable v2 cgroups?
Thanks for answers,
Jirka
On Thu, 2019-02-14 at 08:10 -0500, Daniel Walsh wrote:
> I have opened a Change Request to
Hi all,
Based on the feedback we modified the change:
* There is a more formal contingency plan in place.
* Contingency deadline is moved one week earlier.
* Detailed description contains explanation of what we want to achieve
for F28. We don't aim to have everything in F28.
* It is System Wide
Hi all,
Based on the feedback we modified the change:
* There is a more formal contingency plan in place.
* Contingency deadline is moved one week earlier.
* Detailed description contains explanation of what we want to achieve
for F28. We don't aim to have everything in F28.
* It is System Wide
On Sat, 2018-01-06 at 09:09 +, Zbigniew Jędrzejewski-Szmek wrote:
> Wow, that sounds like a hefty change. Has the work already begun?
> Is there a repo/branch where one can look at the WIP, test stuff,
> etc?
>
We are already working on that and everything goes directly to master -
"Rawhide"
On Tue, 2017-10-17 at 09:30 +0200, Miroslav Suchý wrote:
> Dne 17.10.2017 v 03:51 Matthew Miller napsal(a):
> > I think the bug here is that DNF is being over-zealous.
> > NetworkManager
> > does not require Cockpit, but Cockpit requires NetworkManager. For
> > some
> > reason, DNF thinks that
Hi,
We are making daily builds of Anaconda in Copr for Rawhide[1] and
actual Fedora[2]. These daily builds are used for our other test
suites.
[1]: https://copr.fedorainfracloud.org/coprs/g/rhinstaller/Anaconda/
[2]: https://copr.fedorainfracloud.org/coprs/g/rhinstaller/Anaconda-dev
el/
On
66 matches
Mail list logo
