On 2/26/20 6:59 PM, Daniel Pocock wrote:
> On 26/02/2020 22:56, Dakota Williams wrote:
>> On 2/24/20 5:57 PM, Daniel Pocock wrote:
>>> On 24/02/2020 20:47, Dakota Williams wrote:
>>>> Does anyone know how to contact maintainer pocock?
>>> Like most developers, I have a backlog of things to deal with and I try
>>> to coordinate fixes for packaging issues into the right part of the
>>> release cycle
>> Would you like help? I'd be willing to be a co-maintainer to make the
> Yes, I would welcome help with these packages
> But there is also an increasing problem of making decisions about trust
> In the case of developers who I haven't met or worked with, I don't
> really know how to proceed
> I've seen several extraordinary examples of developers doing things that
> undermine my confidence in them over the last couple of years. The
> fighting within GNU and FSF right now is the latest iteration of that.
> Now, whenever I receive a request from somebody I don't know, there is
> an extra effort for me to decide how to proceed.
> Maybe I can simply resign from maintaining the asio package and then opt
> out of the process of choosing a new maintainer.
> Please don't take this personally: it is a reflection of the overall
> state of free software communities today.
I don't know about the situation with the GNU project and the FSF, but
if there's something you'd like me to do to prove trust, I could do it.
I built ocaml-4.10.0-1.fc33 yesterday.
Now I want to build ocaml-4.10.0-1.fc32 into a side tag today, but
builds fail with:
$ fedpkg request-side-tag --base-tag f32-build
Side tag 'f32-build-side-19863' (id 19863) created.
Use 'fedpkg build --target=f32-build-side-19863' to use it.
Use 'koji wait-repo f32-build-side-19863' to wait for the build repo to be generated.
$ fedpkg build --target=f32-build-side-19863
Could not execute build: Package ocaml-4.10.0-1 has already been built
Note: You can skip this check with --skip-nvr-check. See help for more info.
This is wrong isn't it?
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
Can someone point me to a way to generate a list of non-retired packages
that I am a maintainer on? Thanks.
Hunting around for a "pagure cli" doesn't bring up much that seems active.
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301 https://www.nwra.com/
Hi everyone! Since it's a new year and a new decade [*], it seems like a
good time to look forward and talk about what we want the Fedora Project to
be in the next five and even ten years. How do we take the awesome
foundation we have now and build and grow and make something that continues
to thrive and be useful, valuable, and fun?
[My thoughts below. Feel free to respond to those, or cut here and start
I see three big themes I think we need to tackle.
First, I'd like to see Fedora become more of an "operating system factory".
The direction we took with the Fedora Editions has been a success — Fedora's
general growth and popularity bears that out. But now it's a good time to
re-examine the positioning. The Editions were meant to fit big, broad
use-cases defined by (at the time) the Fedora Board and FESCo. Since then,
everything's become more complicated, with Atomic and then CoreOS, and IoT,
and Silverblue — and we never really found a satisfying way to present the
work of our other desktop SIGs.
So, I think we should revisit the top-level design for Get Fedora. I'm not a
designer and I don't have a particular answer in mind, but I think we should
try an approach which showcases all of our different outputs in some way
which also makes it easy for new users to find the right solution quickly
(and to understand the support options and expecations for their choice).
In support of that, I'd like to also have that page steer people into
tooling for creating new spins —- and I'd like to see us invest in and
rebuild the spin creation processes. (Particularly, I'd like spin releases
to be decoupled from the main OS release, and for those to be self-service
by their SIGs with minimal rel-eng involvement needed.)
Second, we need to figure out how to work with language-native packaging
formats and more directly with code that's distributed in git repos rather
than as tarball releases.
We're not adding meaningful end-user value by manually repackaging these in
our own format. We _do_ add value by vetting licenses and insuring
availability and consistency, but I think we can find better ways to do
that. I think the "source git" project is an interesting step here.
These two things are linked. I want application developers to find Fedora a
convenient and easy way to get their software to users. Pulling from the
Fedora container and flatpak registries should give the same feeling of
trust and safety that installing and RPM from our repos does today. We're
not going to get either of those things with the system we have now. Our
value is unclear to both developers and end users, so we just get left out.
If we don't address this, we're ultimately going to be reduced to a
barely-differentiated implementation of a base OS that no one really cares
about, not the rich software ecosystem we've always aspired to build.
Third, we really need to continue to grow the project as more than coding
Obviously that engineering work is the core of the project
(and we should grow that too!), but it doesn't matter what we build if no
one can find it or find how to use it. We need to feed and grow our
documentation and support communities around the world. Marie (our new
FCAIC, in case you missed that!) and I have been talking about this, and we
hope to really expand the $150-mini-event Mindshare program in the next
year, and hopefully build on that further in the coming ones.
Those are my thoughts. What other challenges and opportunities do you see,
and what would you like us to focus on?
(Also, on a more personal note: I've been SUPER swamped with email. If you
sent me something over the holiday break and I didn't answer, it's not you,
it's me. If I dropped something important, please send again. I'm declaring
email bankrupcy and starting the year fresh.)
Fedora Project Leader
I intend to unretire python-dockerpty, which was retired four weeks ago due to being orphaned. It is a dependency of docker-compose, which cannot build in f32 without it, and for which I'm the maintainer. I've submitted releng issue https://pagure.io/releng/issue/9288