I've certainly made the mistake of accidentally creating branches
in dist-git and now being stuck with them because we can't delete
them. Now that src.fedoraproject.org (dist-git) is backed by a newer
version of pagure you can prevent creating new branches by `git push`.
For your project in the web UI:
- Go to the `Settings` menu
- Select `Hooks` from the left hand side
- Expand `Prevent creating new branches by git push`
- Click the checkbox
- Click `Update`
I personally think this should be the default for all projects but
I don't know if there is a way to easily make that happen when a project
Hope this helps someone!
Too often there are "non responsive maintainer" messages here.
Sometimes this is because a maintainer has lost their interest in Fedora
and left their responsibilities without communication, which means their
packages can be left unmaintained for long time in repositories before
someone notice that.
At other times the maintainer is still active, but for some reason they
are unreachable to users (email change, etc.).
I would propose some sort of automatic check of maintainer responsivity.
Maybe a tool that checks a packager activity in the last 6 months and if
there is no activity then sends an email asking the maintainer to
confirm they're still involved in Fedora. In case there's no reply,
either automatically orphan their packages or notify someone
(devel-list) to try to reach them.
What do you think?
Hi everybody, I am debugging boinc-manager, and everytime I run
$ gdb boincmgr
then I trigger the crash, after running
(gdb) thread apply all backtrace
I obtain stuff like
[...] argc=<optimized out>
so I need help in tuning the boinc-client spec file in order to avoid that (for example using gcc -O0).
To begin, I started removing -DNDEBUG flag in order to re-enable the wxWidgets debug standard output.
Thank you for your time
Anybody know what's going on with Centos 7.6-1810?
Some packages in EPEL depend on it, but it is apparently not yet available.
This discrepancy is breaking yum updates for me.
For example, xorgxrdp-0.2.8-3.el7 depends on xorg-x11-server-Xorg
1.20.1, which isn't yet available (rather, available on in the cr
repo, not in CentOS updates yet).
I am currently packaging a program whose README and documentation is
licensed under CC-BY-SA-4.0. However,
<https://fedoraproject.org/wiki/Licensing:Main> only lists CC-BY-SA as
meaning version 3.0 of that licence.
Is CC-BY-SA-4.0 a "good" licence according to Fedora? How might one
package a program that uses this licence?
(Apologies for the late notice -- I forgot to do this before the long
Following is the list of topics that will be discussed in the
FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 onirc.freenode.net.
To convert UTC to your local time, take a look at
date -d '2018-11-26 15:00 UTC'
Links to all issues to be discussed can be found at:
= Discussed and Voted in the Ticket =
#topic 2014 F30 System-Wide Change: The GNU C Library version 2.29
DECISION (+6, 0, -0)
= Followups =
#topic #2013 too strict rules for branches deletion alongside with
norules for theirs creations
= New business =
#topic #2015 Preclusion of Firefox automatic download of OpenH264
(#1359) may have been violated at some point
#topic #2016 F29 – rebase of dnf, libdnf, dnf-plugins-core, dnf-plugins-extras
= Open Floor =
For more complete details, please visit each individual
issue. The report of the agenda items can be found at
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.