Retrace failed. Try again later and if the problem persists report
this issue please.
by Chris Murphy
I'm on a Fedora 27 Workstation system, dnf system-upgrade(d) from
Fedora 26. I've got a few crashes that gnome-abrt (Problem Reporting)
I've clicked on to report, but I get this message for all three of
them:
Retrace job failed
Retrace failed. Try again later and if the problem persists report
this issue please.
The main problem with this is the message itself: I'm not sure where
to report it or what information to include.
This is an example from one of their log windows (I've already
downloaded all the
debuginfos and separately filed bugs for these crashes with coredumpctl gdb
output, but maybe there's an issue with the retrace server (?)
2017-11-28 04:18:12 Analyzing crash data
2017-11-28 04:18:28 WARNING:fedora.client.openidbaseclient:Unable to
create /usr/share/retrace-server/.fedora: [Errno 13] Permission
denied: '/usr/share/retrace-server/.fedora'
ERROR:faf:Unable to import plugin
pyfaf.actions.create_problems_gnome_mmarusak: cannot import name
get_unassigned_reports_w_name
INFO:faf.Coredump2Packages:Executing eu-unstrip
INFO:faf.Coredump2Packages:Mapping build-ids into debuginfo packages
INFO:faf.Coredump2Packages:Getting binary packages from debuginfos
--
Chris Murphy
6 years, 4 months
Package naming question
by Igor Gnatenko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
I would like to hear opinion of other packagers about naming. We have
`parallel` utility implemented in Rust which is drop-in replacement for GNU
parallel. I was thinking how to name package and how people would expect it to
be named. So far options are:
* rust-parallel
* parallel-rust
* parallel-rs
I dislike first one because it is not ending up in completion while second and
third are quite good.
Thoughts?
- --
- -Igor Gnatenko
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlolE00ACgkQaVcUvRu8
X0zcDg/+J4jaboaEmySwsgHiSNDfVqazoxrcZDp0abS8wRO9jSxXCPU0K/MpBgtg
W3LnJOkEhr4WjRtwoC4MmvZf99sfBo4q6ATfd2hOg0WeYkwP36Fu9lVZUAEP6V0E
zVNp44UCuxJNU9IxUvop4XVJOTmaF0Be3pGrJ2LRliZkIgJgzVwOk8pkv/eO1iwp
Y5j2VK7Wjs1Z2/tuL6/u02GqZOpD/0NE145awQUp2PFNwIwYeP70UZ5OjoqdLPNO
LAWybGPSuoaLN7xT7F3FFvqUBhU6Ypsnc2trd01DyJ81v8ITxeAxZpyMy/jLsoyU
0RyP5UJyzI/joGNLHDQimmBnBH3SOcVr68Sx2TIMLxmsyCFaGmv+ehZlTkRWocnM
QWc0fKOD5FC9W7NY21NOCADG6tuIjj+n8Ncw27gbZ0gexbq/drcq9J7aaiKZ0USf
HA7iKya6OiuSKI2GAzKGMcBzp3GKkcUl+3NSBOw2bB/fF1NneXJDL4FkQVhvC+Ta
G9Hmz3MC+f/amozta7y+pPAzswf5yzArc1Lcw/HWx3QG3S/DAlR+fnJntf+Rgz6I
KRYyasi+RLUizzxBnlOXsi3PM3ppErHXmCfewyyhNup0T+DQsW3Na9/q6nWea/1+
I2WA3kZEmoYHEZM5d3r4I3vPliz0QXJQjNkpicqCxg+A85CBH44=
=TEXI
-----END PGP SIGNATURE-----
6 years, 4 months
Fedora Modular 27 compose report: 20171204.n.1 changes
by Fedora Branched Report
OLD: Fedora-Modular-27-20171204.n.1
NEW: Fedora-Modular-27-20171204.n.1
===== SUMMARY =====
Added images: 0
Dropped images: 0
Added packages: 0
Dropped packages: 0
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages: 0 B
Size of upgraded packages: 0 B
Size of downgraded packages: 0 B
Size change of upgraded packages: 0 B
Size change of downgraded packages: 0 B
===== ADDED IMAGES =====
===== DROPPED IMAGES =====
===== ADDED PACKAGES =====
===== DROPPED PACKAGES =====
===== UPGRADED PACKAGES =====
===== DOWNGRADED PACKAGES =====
6 years, 4 months
excess automated emails from Fedora
by Daniel Pocock
Hi,
I've opened a bug report[1] about automatically generated emails from
Fedora Fedmsg and other parts of Fedora infrastructure.
Maybe there are other components of Fedora where bug reports like this
should be opened but that isn't completely clear to me.
I'm sending this email to the community to ask a few things:
- to see if other people have useful information to add to the bug report
- to see if anybody can suggest other components to file bug reports
against, or help do so
- to find out if there is existing policy on this issue, a search of the
wiki didn't reveal anything obvious
- to get any general feedback about how the Fedora community feels about
use of email addresses.
Note that I'm not just writing this to complain about the issue, I've
previously done work on tools to help people build dashboards of their
issues and I've blogged about some of those, including how you can get
Github issues in iCalendar[2], Nagios issues in iCalendar[3], Debian
issues in iCalendar[4]. Bugzilla (used by Fedora, Mozilla and GNOME,
for example) already has native iCalendar support. Harsh Daftary did
work on aggregating[5] things from these sources in a dashboard as a
GSoC project. Putting this all together, even using the Mozilla
Calendar/Lightning plugin, you can easily merge issues from many places
and see them in priority[2] order which is far more comfortable than
being bombarded by emails and trying to work out which is most
important, which is already fixed by somebody else, etc.
- can anybody comment on other tools like this that put the developers
in control rather than bombarding our inboxes with things?
- would anybody like to help contribute to things like this in future,
for example, mentoring another GSoC project on the dashboard concept?
Regards,
Daniel
1. https://github.com/fedora-infra/fmn/issues/266
2. https://danielpocock.com/github-issues-as-an-icalendar-feed
3. https://danielpocock.com/get-your-nagios-issues-as-an-icalendar-feed
4.
https://danielpocock.com/debian-maintainer-dashboard-now-provides-icalend...
5.
https://danielpocock.com/aggregating-tasks-multiple-issue-trackers-gsoc-2...
6 years, 4 months
Help Reviewing a FreeOTP (Android) Pull Request in Korean
by Nathaniel McCallum
Do you speak (I think) Korean and English? Can you code? If so, I
could use your help.
The Fedora-associated FreeOTP project has received this pull request:
https://github.com/freeotp/freeotp-android/pull/165
The comments and commit descriptions are almost entirely in Korean and
I don't know how to make heads or tails of them. Communication with
the patch submitter is also difficult since I don't speak Korean and
they don't speak English. However, I'd really like to give the
submitter a fair shot.
Is there anyone in the Fedora community that would be willing to
assist? This is a great opportunity to demonstrate the diversity of
open source!
6 years, 4 months
is there logstash alternative in Fedora?
by Michal Novotny
Hello,
I am looking for an alternative for Java logstash application (not in
Fedora) that can parse logs (e.g. httpd access.log) and collect stats about
number of occurrences for a given search pattern (basically it can e.g.
group by IP and give number of lines for each IP and then post it to some
url address). Is there anything like this currently? I am about to
implement it but wanted to make sure I won't be doing something which
already exists.
Thank you
clime
6 years, 4 months
[Fedocal] Reminder meeting : F27 Server Final Go/No-Go meeting
by jkurik＠redhat.com
Dear all,
You are kindly invited to the meeting:
F27 Server Final Go/No-Go meeting on 2017-12-07 from 19:00:00 to 21:00:00 Europe/Prague
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Before each public release Development, QA and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the Go/No-Go Meeting. Verifying that the Release criteria are met is the responsibility of the QA Team. Release Candidate (RC) availability and good QA coverage are prerequisites for the Go/No-Go meeting. If you have any bug on the list, please help us with Beta release. If we won't be ready by Thursday, we will use this meeting to review blockers and decide what to do.
More information available at:
[https://fedoraproject.org/wiki/Go_No_Go_Meeting](https://fedoraproject.or...
Source: https://apps.fedoraproject.org/calendar/meeting/8677/
6 years, 4 months
F28 System Wide Change: Reduce Initial Setup Redundancy
by Jan Kurik
= System Wide Change: Reduce Initial Setup Redundancy =
https://fedoraproject.org/wiki/Changes/ReduceInitialSetupRedundancy
Change owner(s):
* Michael Catanzaro <mcatanzaro AT gnome DOT org>
Currently there is a high level of redundancy between the Anaconda
installer and gnome-initial-setup. This change aims to eliminate these
redundancies and streamline the initial user experience in Fedora
Workstation.
== Detailed Description ==
Firstly, please note that the effects of this change will be
restricted to Fedora Workstation. We do not propose any changes that
affect alternative Fedora installers (e.g. Calamares) or initial setup
tools (e.g. the initial-setup package, not to be confused with
gnome-initial-setup).
A few years ago, Fedora Workstation developers discussed with Anaconda
developers the redundancy between many Anaconda settings and
gnome-initial-setup. The Anaconda developers responded by added a
configuration file mechanism, /etc/sysconfig/anaconda, which can be
used to suppress Anaconda spokes if written before Anaconda runs. This
file is also written by Anaconda to tell the initial-setup tool which
Anaconda spokes the user has visited, so that the initial-setup tool
can suppress specific spokes. Although this functionality has existed
for some time now, the Workstation developers until now failed to
follow up and begin using it. We now intend to make use of this
functionality to suppress Anaconda spokes that are redundant with
gnome-initial-setup. Meanwhile, our friends at Endless OS have added a
similar configuration file for gnome-initial-setup that allows us to
suppress some configuration that is best handled in Anaconda. Below,
we discuss what we plan to do with specific settings.
=== Language and Keyboard Layout ===
Although we do not propose it at this time, language and keyboard
layout selection should be presented to the user *before* entering the
live session, as it is currently too difficult for users to change
these settings unless they are already familiar with Fedora, and --
unless you speak English and use a US keyboard -- these settings must
be changed for the live session to be usable. Both Anaconda and
gnome-initial-setup are too late for configuring these settings. (An
exception would be for netinstalls of Fedora Workstation, where
Anaconda is the best place for this configuration.) In the meantime,
until we have a way to prompt users for these settings earlier than
Anaconda, these panels should be removed from gnome-initial-setup,
because Anaconda is clearly a better place than gnome-initial-setup
for this configuration. (This would affect gnome-initial-setup when
creating the first user account. Additional user accounts created
later would still receive these panels in gnome-initial-setup.)
=== Time and Date ===
We want to remove the time and date spoke from Anaconda, since it is
largely redundant with the timezone page in gnome-initial-setup.
However, it might be necessary to remove this page from
gnome-initial-setup instead, as previously there have been technical
concerns raised regarding the necessity of configuring the system
clock before running the installer. This choice will be based on
technical feedback from the Fedora developer community.
=== Network ===
We will remove the network configuration spoke from Anaconda.
Currently this spoke only allows configuring the system hostname, but
it places restrictions on the possible characters in the hostname that
do not match the restrictions used by Fedora Workstation. Fedora
Workstation uses systemd-hostnamed to allow "pretty" hostnames with
Unicode characters and spaces, which we expect to be displayed
properly and consistently in the user interface, but the Anaconda
configuration does not follow this pattern. Additionally, exposing the
hostname as network configuration is confusing. We may consider adding
a simpler "Computer Name" setting that allows "pretty" characters and
is not presented as a networking setting in the future, but it does
not seem necessary to prompt the user to set a hostname at all.
Note: this applies only to USB install, obviously not to netinstall.
We will need some way to differentiate between the two when writing
the Anaconda configuration file.
=== User Account ===
Currently, users have the option of creating the initial user account
in Anaconda, or not. Anaconda does not require this if the user sets a
root password. Users who do not create a user account in Anaconda are
required to create a user account later, by gnome-initial-setup. This
means we currently have two different ways of creating the first user
account in Workstation, with (potentially) two different sets of bugs.
Since Anaconda allows configuring whether the initial user is added to
the wheel group, it also means some initial users will be in wheel and
others will not. We will remove the user account creation spoke in
Anaconda. All users will create the first user account using
gnome-initial-setup, and all initial users will be added to the wheel
group. Of course, this can be easily changed after installation if
desired.
=== Root Account ===
Currently, users have the option of setting a root password in
Anaconda, or not. Anaconda does not require this if the user creates
an initial user account and selects the option to add it to the wheel
group. We will remove the root password creation spoke. All
Workstation installs will have no root password set by default, as in
Ubuntu. Having a root password is not useful for nontechnical users,
and it is confusing to ask users to create multiple passwords. Because
the initial user created by gnome-initial-setup will be added to the
wheel group, all administrative functions will continue to be
available within the desktop environment via Polkit. Additionally, the
initial user will have sudo access to run commands as root. Of course,
a root password can be set after installation using `sudo passwd`.
== Scope ==
* Proposal owners:
Provide a default /etc/config/anaconda file for Fedora Workstation.
This could be e.g. shipped in the gnome-initial-setup package or
written by the firstboot tool before Anaconda runs.
* Other developers:
Anaconda developers to review UI. QA team to review installation tests.
* Release engineering: #6878 [ https://pagure.io/releng/issue/6878 ]
** List of deliverables: No changes needed
* Policies and guidelines:
No changes needed
* Trademark approval:
N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
6 years, 4 months
Fedora Modular 27 compose report: 20171204.n.1 changes
by Fedora Branched Report
OLD: Fedora-Modular-27-20171204.n.1
NEW: Fedora-Modular-27-20171204.n.1
===== SUMMARY =====
Added images: 0
Dropped images: 0
Added packages: 0
Dropped packages: 0
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages: 0 B
Size of upgraded packages: 0 B
Size of downgraded packages: 0 B
Size change of upgraded packages: 0 B
Size change of downgraded packages: 0 B
===== ADDED IMAGES =====
===== DROPPED IMAGES =====
===== ADDED PACKAGES =====
===== DROPPED PACKAGES =====
===== UPGRADED PACKAGES =====
===== DOWNGRADED PACKAGES =====
6 years, 4 months
