How to subscribe to Bugzilla components?
by Michael Catanzaro
Hi,
Do anyone know how to subscribe to Bugzilla bugs for a particular
component?
I'm trying to watch glib-networking bugs. I'm already watching issues
and PRs at https://src.fedoraproject.org/rpms/glib-networking, but that
only watches for Pagure issues, not Bugzilla.
I'm already watching webkit2gtk3 package issues on Bugzilla and this
works exactly as I would expect, but I think I configured that long ago
with pkgdb back when pkgdb still existed.
This seems pretty basic, so it shouldn't be hard. Any ideas?
Michael
4 years, 7 months
Orphaned paper-icon-theme
by Fabio Valentini
Hi everybody,
I've just orphaned the "paper-icon-theme" package. I no longer use it
and have no interest in maintaining it further. The package is
up-to-date with the latest upstream release (though the upstream
project is pretty much dead now).
Fabio
4 years, 7 months
Minimization Objective report
by Adam Samalik
This is the Minimization Objective [0] update.
Status: Discovery phase
== Regular meeting canceled ==
We have decided to cancel the regular Minimization Team Meeting [1] as we
prefer async discussions on #fedora-devel and devel(a)lists.fp.o. This makes
it more inclusive to people with other commitments or being in timezones
that prevent them attending the meeting at that specific time.
== systemd-sysusers vs. containers ==
We don't want Systemd in containers [2], but we recognise this is a
container-specific problem. So we're asking other groups — Containers SIG
and people working with OpenShift — for how they're approaching this
problem.
== Feedback Pipeline ==
Feedback Pipeline [3] is now automated, refreshing every day.
It also now includes sizes of individual packages in all reports, as well
as a timestamp.
== pcre -> pcre2 ==
Moving grep (one of the last packages using pcre) to pcre2. [4]
== How to get involved ==
See if there is anything interesting to you on action plan [42], or reach
out with something you think is useful but is missing there. Open a ticket
in the tracker [43] or discuss in #fedora-devel on IRC.
Cheers,
Adam
[0] Objective: https://docs.fedoraproject.org/en-US/minimization/
[1] Meeting canceled: https://pagure.io/minimization/issue/14
[2] systemd-sysusers vs. containers: https://pagure.io/minimization/issue/13
[3] Feedback Pipeline: https://minimization.github.io/reports/
[4] switching grep to pcre2:
https://bugzilla.redhat.com/show_bug.cgi?id=1755491
[42] Action plan:
https://docs.fedoraproject.org/en-US/minimization/action-plan/
[43] Issue tracker: https://pagure.io/minimization/issues
--
Adam Šamalík
---------------------------
Senior Software Engineer
Red Hat
4 years, 7 months
Problem with F30 module packages that are built in F32 buildroot (?)
by Till Hofmann
Hi all,
We have an odd issue with a module build of sway for F30: It looks like
the module was actually built with a F32 buildroot.
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1754167
Here's the build:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1376355
The modulemd file contains:
dependencies:
- buildrequires:
platform: [f30]
requires:
platform: [f30]
But then, it built packages with f32 in the package version:
artifacts:
rpms:
- mako-0:1.4-1.module_f32+6140+eb754d2b.src
- mako-0:1.4-1.module_f32+6140+eb754d2b.x86_64
- mako-debuginfo-0:1.4-1.module_f32+6140+eb754d2b.x86_64
- mako-debugsource-0:1.4-1.module_f32+6140+eb754d2b.x86_64
[and more packages]
The package shows up in a F30 repoquery:
$ dnf repoquery --releasever=30 mako
Last metadata expiration check: 0:08:32 ago on Sun 22 Sep 2019 11:25:43
CEST.
mako-0:1.4-1.module_f32+6140+eb754d2b.x86_64
But it requires systemd-libs from F32:
$ dnf repoquery --releasever=30 --requires \
mako-0:1.4-1.module_f32+6140+eb754d2b.x86_64 | grep SYSTEMD
libsystemd.so.0(LIBSYSTEMD_221)(64bit)
libsystemd.so.0(LIBSYSTEMD_222)(64bit)
libsystemd.so.0(LIBSYSTEMD_243)(64bit)
Can someone tell me what's going on here?
Thanks!
Till
4 years, 7 months
CPE Team Weekly Update
by Aoife Moloney
Hi everyone,
I’d like to introduce myself first, my name is Aoife Moloney and I recently
started with the Community Platform Engineering (CPE) team. My role within
this team is going to be a hybrid role of a Product Owner / Project Manager.
As part of that, I want to send a weekly update to the lists to give an
insight into what the CPE team have worked on over the past week or so.
This will also be mirrored as a higher level blog to give maximum
visibility.
We, as a team, welcome your input and comments and please do let us know
how we can improve this community facing information segment!
As you know, the CPE team looks after interests in both Fedora and CentOS,
so this update is also going to include work done on areas that are not
your Community, but for transparency, we are including it :)
High Level Project Updates:
Fedora:
Rawhide Gating: <https://github.com/fedora-infra/bodhi/projects/3>
-
First work around merging side tags has been completed
-
Open PR <https://github.com/fedora-infra/bodhi/pull/3498> that needs
to be finished
-
We need to update our staging environment which broke when we branched
F31 in production:
-
Tracked in: https://pagure.io/releng/issue/8838
-
Koji stuck/full: https://pagure.io/fedora-infrastructure/issue/8240
-
Overview page of the remaining blockers and dependencies organized at:
-
https://hackmd.io/Gbuu9JOPR--Y2yNCBEYI5A?view
-
Input welcome for anything that would be missing
-
https://github.com/fedora-infra/bodhi/projects/3
-
High priority items in the “Ready” column are all hard-dependency
for pushing multi-builds to production
repoSpanner <https://github.com/repoSpanner/repoSpanner>
-
Race condition discovered has been fixed and tested
-
Test suite has a number of issues which are being triaged and worked
through at the moment
-
Performance testing is next on our agenda
Application Retirements
-
Badges has had some further conversations with community members and we
are aligning on a handover date
-
Packagedb-cli is being retired this week
-
Documentation for onboarding contributors to Community OpenShift was
started with a good mail thread on Fedora Devel
-
Pastebin: Ongoing conversations with future maintainer, expecting an
update in the next 2 weeks
-
Elections: Ben Cotton is taking this over and the CPE team are assisting
with moving this to Communishift
-
Fedocal still needs your help, we need a Maintainer here urgently
-
If no one steps up by October 15th, we will be looking at
decommissioning it!
-
Nuancier, we possibly have identified a maintainer here and the team are
engaging in a conversation
Misc highlights from various parts of the ecosystem:
-
FPDC had some light work on it, an instance of Kinto (
http://docs.kinto-storage.org/en/stable/) was deployed in staging at
https://fpdc.stg.fedoraproject.org/v1/
-
Fedora Container base image update for F30, F31 and F32. (Dockerhub
https://github.com/docker-library/official-images/pull/6702,
Registry.fp.o https://pagure.io/releng/issue/8846)
-
Rawhide compose failures, due to podman gating, filed
https://github.com/fedora-infra/bodhi/issues/3512 on it
-
Announced F31 Beta freeze over, adjusted thing
-
F31 Beta saw the team help in various places, everything went smoothly!
-
Fixed pagure stunnel to use tls1.1/1.2 and a valid cert
https://pagure.io/fedora-infrastructure/issue/8231
-
Fixed pagure event server to use valid cert with intermediate:
https://pagure.io/fedora-infrastructure/issue/8224
-
Mdapi app fully moved to OpenShift:
https://pagure.io/fedora-infrastructure/issue/8238
-
Branched versioned Fedora docs for F31
-
Worked on updates to Fedora contributor docs
-
Progressing more fedmsg → fedora messaging conversions on our scripting
-
Fixed the Koji rpm.sign fedora-messaging message (
https://pagure.io/fedora-infrastructure/issue/8158)
-
CentOS:
-
CentOS 8 was released this week :)
-
Core artifacts (repos and install media) were refreshed and sent to
the mirrors
-
CentOS Stream was built and staged
-
Cloud and Container images are outstanding, coming up next
-
Sources and debuginfo content synced to the mirrors
-
Armhfp enablement coming soon
-
Activities related to releasing CentOS 7.7 (17-September) and
subsequently CentOS 8 (24-September) consumed the entire teams time!
--
Aoife Moloney
Feature Driver
Community Platform Engineering Team
Red Hat EMEA <https://www.redhat.com>
Communications House
Cork Road
Waterford
<https://www.redhat.com>
4 years, 7 months
Re: Defining the future of the packager workflow in Fedora
by Petr Pisar
On 2019-09-26, Pierre-Yves Chibon <pingou(a)pingoured.fr> wrote:
> ○ Every changes to dist-git is done via pull-requests
Pull requests are great for proposing your changes to foreign packages.
It does not make sense when maintaining the code. Either when doing
a mass changes like rebuilding all Perl packages against a new perl or
when pushing your own changes. It will become a bureaucracy that adds
a delay and complexity and spams you mailbox. Who is going to merge all
the requests? How do you automate it? We would need "koji watch-task"
for merging the pull requests. I will repeat it: pull requests are
great when you need a review. Otherwise it only consusmes resources.
I'm strongly against this.
> ○ Pull-requests are automatically tested
Nice. But i think this already happens.
> ○ Every commit to dist-git (ie: PR merged) is automatically built in koji
How do you want to implement waiting on propagating build root overrides?
> ○ Every build in koji results automatically in an update in bodhi
How do I merge related updates into on if more packages must be
tested and delivered as one unit? That very often happens with the
overrides.
I smell automated side-tags that has never been implemented.
> ○ Every update in bodhi is automatically tested
This is already a reality.
> ○ If the tests pass, the update is automatically pushed to the repository
>
This also already happens.
-- Petr
4 years, 7 months
HEADS-UP: Asciidoctor 2.0.10
by Todd Zullinger
Hi all,
I'm planning to push asciidoctor-2.0.10 to rawhide in the
next few days. This is a major bump from our current 1.5.8,
but upstream has worked hard to fix regressions found since
the initial 2.0.0 release back in March.
The 2.0.0 release notes can be found at:
https://github.com/asciidoctor/asciidoctor/releases/tag/v2.0.0
The subsequent minor release are covered at:
https://github.com/asciidoctor/asciidoctor/releases
Most packages shouldn't really notice the change. But there
are likely some which have relied on things which worked in
1.5.8 that may have been changed. One notable change is the
removal of docbook 4.5 support (in favor of docbook 5).
This can impact packages which use asciidoctor to generate
intermediate xml that is then fed to xmlto.
(The upstream git project is one such project, though in git
we still default to asciidoc for now. And patches are
landing upstream to support building with asciidoctor 2.x
and docbook 5.)
These srpm's require asciidoctor or rubygems-asciidoctor:
awesome
booth
hugo
ipmctl
js8call
mod_auth_mellon
nanomsg
ndctl
nng
oidentd
qpid-dispatch
tuned
usbguard
weechat
wiki2beamer
wsjtx
I've included those package owners via Bcc:.
If anyone needs me to hold off for a bit, please speak up.
We do want to take this action soon though, so we can ensure
any kinks get worked out well before we branch for f32.
There's also an outstanding FTBFS bug for the current 1.5.8
package which this move to 2.0.10 conveniently fixes.
--
Todd
4 years, 7 months
Schedule for Mondays's FESCo Meeting (2019-09-30)
by Stephen Gallagher
Following is the list of topics that will be discussed in the
FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2019-09-30 15:00 UTC'
Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda
= Discussed and Voted in the Ticket =
F32 Self-Contained Change: PHP 7.4
https://pagure.io/fesco/issue/2235
Accepted (+4, 0, -0)
provenpackager privileges for ankursinha
https://pagure.io/fesco/issue/2234
Accepted (+9, 0, -0)
F32 Self-Contained Change: MariaDB 10.4
https://pagure.io/fesco/issue/2233
Accepted (+5, 0, -0)
F32 Self-Contained Change: Jekyll 4
https://pagure.io/fesco/issue/2232
Accepted (+7, 0, -0)
FESCo blocker bug: Broken upgrades via libgit2
https://pagure.io/fesco/issue/2230
Agreed to accept as F31 Final blocker bug (+7, 0, -0)
= Followups =
= New business =
#topic #2231 F32 System-Wide Change: Firewalld Default to nftables
https://pagure.io/fesco/issue/2231
#topic #2236 Default Stream for Eclipse module
https://pagure.io/fesco/issue/2236
#topic #2238 GIMP: exception to continue using Python 2
https://pagure.io/fesco/issue/2238
= Open Floor =
For more complete details, please visit each individual
issue. The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda
If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
4 years, 7 months
Re: can we merge package.cfg into master ?
by Sérgio Basto
On Sat, 2019-09-28 at 15:18 -0600, Orion Poplawski wrote:
> On 9/27/19 10:29 AM, Sérgio Basto wrote:
> > On Fri, 2019-09-27 at 12:06 -0400, Neal Gompa wrote:
> > > On Fri, Sep 27, 2019 at 12:03 PM Sérgio Basto <sergio(a)serjux.com>
> > > wrote:
> > > > Hi,
> > > > epel 8 brings a new file called package.cfg, I strongly prefer
> > > > to
> > > > keep
> > > > branches mergeable with fast forward , may we merge this into
> > > > master ?
> > > > like I did in pngquant [1]
> > > >
> > >
> > > It disables the normal build behavior for all non-master
> > > branches, so
> > > you don't want to do that.
> >
> > Well , I want keep my branches mergeable !
>
> They are mergeable - just not fast-forward mergeable :)
why package.cfg don't reference which branch is for that targets ?
--
Sérgio M. B.
4 years, 7 months