Friday, February 16, 2018

libmodulemd: SOname bump coming to released Fedora

I'm going to be submitting an update for libmodulemd today for all released branches of Fedora. This is *technically* in conflict with the Stable Updates Policy, but it is both necessary and should be safe to accomplish.

1) The teams that were planning to switch to it from the previous python-modulemd have not yet done so or are just starting to, so it's not believed there is anything currently running in production with the older version.
2) The API is *source*-compatible, but not binary-compatible (hence the soname bump), so it will just require a rebuild if anyone *is* using it.
3) The reason for the API change is that certain semantics around ownership of memory have changed. This mostly impacts the GObject Introspection bindings for other languages such as Python, but as it technically changes the ABI contract, bumping soname was the correct thing to do.

F29 System Wide Change: Remove GCC from BuildRoot

Proposed System Wide Change: Remove GCC from BuildRoot
https://fedoraproject.org/wiki/Changes/Remove_GCC_from_BuildRoot


Owner(s):
* Igor Gnatenko <ignatenkobrain at fedoraproject dot org>


Removing gcc and gcc-c++ from default buildroot in Koji and mock.



== Detailed description ==
Since beginning of Fedora, gcc (and gcc-c++) are installed in every
buildroot. Times have changed and nowadays many of packages are not
written in C/C++, they are written in Python, Ruby, Node.js, Go, Rust,
OCaml, Perl and so on so they don't need to have C/C++ compiler.
Installing gcc and gcc-c++ takes time so if we remove it, we can
improve build times for many of the packages.


== Scope ==
* Proposal owners:
Remove gcc, gcc-c++ from build group in Koji and from buildsys-build
group in comps.

* Other developers:
Maintainers should follow guidelines and add BuildRequires: gcc if
they need it during build (this guideline exists for long time).

* Release engineering: [https://pagure.io/releng/issue/7317 #7317]

** List of deliverables:
N/A (not a System Wide Change)

* Policies and guidelines:
Nothing needed, guidelines already have paragraph about listing all
required BuildRequires.

* 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
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org

F29 Self Contained Change: Drop Legacy GTK+ GUI in wireshark

Proposed Self Contained Change: Drop Legacy GTK+ GUI in wireshark
https://fedoraproject.org/wiki/Changes/Drop_Legacy_GTK+_GUI_in_wireshark

Owner(s):
* Michal Ruprich <mruprich at redhat dot com>



== Detailed description ==
Since wireshark-2.0 there are two GUIs availble for use. One is based
on GTK+ and the other on Qt. The upstream focuses on the development
of the Qt-based GUI and the GTK-based GUI has been marked as legacy.
Since wireshark 2.4.0 the GTK-based GUI is not supported anymore and
it is disabled by default. We should drop the GTK-based wireshark in
Fedora 29.


== Scope ==
* Proposal owners:
This is an isolated change. The new GUI is more or less the same as
the new one. It does not affect any functionality of wireshark
package. This will be a very easy change from developer point of view.

* Other developers:
N/A (not a System Wide Change)

* Release engineering:
[https://pagure.io/releng/issue/7319 #7319]

**List of deliverables:
N/A (not a System Wide Change)

* Policies and guidelines:
N/A (not a System Wide Change)

* 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
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org

F29 Self Contained Change: True Noarch Erlang Packages

Proposed Self Contained Change: True Noarch Erlang Packages
https://fedoraproject.org/wiki/Changes/TrueNoarchErlangPackages


Owner(s):
* Randy Barlow <bowlofeggs at fedoraproject dot org>


Erlang packages are currently all installed into
%{_libdir}/erlang/lib, despite most of them being noarch packages.
This proposal is to modify Erlang to search %{_datadir}/erlang/lib in
addition to %{_libdir}/erlang/lib when searching for dependencies.



== Detailed description ==
The Erlang VM is currently hardcoded to search for dependencies in
%{_libdir}/erlang/lib (on x86_64 this is /usr/lib64/erlang/lib). Due
to this, all Erlang packages are currently compiled "archful", despite
most of them being pure Erlang and thus truly noarch. This leads to
longer build times for Erlang packages, and more storage used in Koji
and on the mirrors.
This change proposes to add an additional path to be searched by the
Erlang VM when finding dependencies at %{_datadir}/erlang/lib (on
x86_64 this is /usr/share/erlang/lib). Additionally, the build macros
will be udpated to automatically use this new path for installation
for noarch packages. "Archful" packages will continue to store their
files where they do today.


== Scope ==
* Proposal owners:
** Write a small patch for the Erlang VM to search two paths instead
of one when loading dependencies. We will attempt to get this patch
accepted upstream first, but we will then carry the patch downstream
until accepted by upstream.
** Modify the Erlang RPM macros to use the new path for noarch packages.

* Other developers:
** Any developers who are not using the Erlang install RPM macro
should modify their spec file to either use the macro, or to install
their noarch packages to the new location.

* Release engineering:
[https://pagure.io/releng/issue/6685 #6685]
** We could mass-rebuild Erlang packages, but everything should keep
working without doing a mass rebuild so it is probably not necessary
or worthwhile, unless we want to more immediately clear up a little
disk space. The recommendation is to wait until the next mass rebuild
since there will be no interruptions for existing packages, i.e., no
effort required from Releng.
** Any erlang packages that switch from being archful to being noarch
will need all their dependent packages to be rebuilt, since they will
no longer provide archful versions of themselves. However, this can be
done at the time each package switches to being noarch. This change
will not switch any particular packages to noarch.

**List of deliverables: N/A (not a System Wide Change)

* Policies and guidelines:
** Erlang packages do not have formal packaging guidelines yet, though
this document does exist:
https://fedoraproject.org/wiki/User:Peter/Erlang_Packaging_Guidelines
*** We should update the WIP guidelines.

* 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
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org

F29 Self Contained Change: No more automagic Python bytecompilation

Proposed Self Contained Change: No more automagic Python bytecompilation
https://fedoraproject.org/wiki/Changes/No_more_automagic_Python_bytecompilation


Owner(s):
* Miro Hrončok <mhroncok at redhat dot com>
* Petr Viktorin <pviktori at redhat dot com>


The current way of automatic Python byte-compiling of files outside
Python-specific directories is too magical and error-prone. It is
built on heuristics that are increasingly wrong.
We will provide a way to opt-out of it and adjust the guidelines to
prefer explicit bytecompilation of such files. Later, the old behavior
will be opt-in only or will cease to exist.
Note that bytecompilation in Python-specific directories (e.g.
/usr/lib/python3.6/) is not affected.



== Detailed description ==
[Change wrangler note]: As the detailed description of this Change
proposal is quite extensive I am just referring to the Change Proposal
wiki page: https://fedoraproject.org/wiki/Changes/No_more_automagic_Python_bytecompilation#Detailed_Description
. Please review the proposal following the link.


== Scope ==
* Proposal owners:
Make it work technically, propose the new guidelines, file pull
requests for python3 modules that follow the current guidelines.

* Other developers:
Maintainers of python3 packages that redefine %__python should merge
provided pull requests. Others may opt-in for the new behavior or
explicitly stick with the old one (not a System Wide Change, they
don't have to do anything).

* Release engineering:
[https://pagure.io/releng/issue/7315 #7315]

* Policies and guidelines:
will be changed as described in description

* Trademark approval:
not needed
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org

F29 System Wide Change: Enable dbus-broker

Proposed System Wide Change: Enable dbus-broker
https://fedoraproject.org/wiki/Changes/EnableDbusBroker


Owner(s):
* David Herrmann <dh dot herrmann at gmail dot com>
* Tom Gundersen <teg at jklm dot no>


Enable dbus-broker.service to use dbus-broker as system and session
message bus backend.



== Detailed description ==
The dbus-broker project is an implementation of a message bus as
defined by the D-Bus specification. Its aim is to provide high
performance and reliability, while keeping compatibility to the D-Bus
reference implementation. It is exclusively written for linux systems,
and makes use of many modern features provided by recent linux kernel
releases.
The main focus points of dbus-broker are reliability, scalability and
security. The dbus-broker project tries to improve on these points
over dbus-daemon, and thus provide a better alternative. And in-depth
analysis can be found in the initial
[https://dvdhrm.github.io/rethinking-the-dbus-message-bus/
announcement] of dbus-broker. An excerpt:
* [https://github.com/bus1/dbus-broker/wiki/Accounting Accounting]:
dbus-broker maintains per-user accounting, including inter-user
quotas. This guarantees that no single user can cause irregularly high
memory consumption in the daemon. Unlike dbus-broker, dbus-daemon
accounts memory in a multi-tier system, based on plain resource
counters on users, connections, and other resources. The multi-tier
system suffers from resource-chaining-exhaustion, where clients
effectively circumvent the accounting by creating multiple
connections/objects, which themselves grant them each a new set of
quotas. The [https://github.com/bus1/dbus-broker/wiki/Accounting
single-tier
accounting] scheme of dbus-broker avoids this, while at
the same time adding inter-user quotas to prevent misuse even across
clients.
* [https://github.com/bus1/dbus-broker/wiki/Reliability Reliability]:
While D-Bus is used on reliable transports, dbus-daemon might still
silently drop messages and given circumstances. This is the only
possible solution dbus-daemon has, given several of its runtime
guarantees. The dbus-broker project changed the architecture of the
bus daemon to a degree, that it can provide many
[https://github.com/bus1/dbus-broker/wiki/Reliability guarantees],
including that no message will be silently, or unexpectedly, dropped.
* [https://github.com/bus1/dbus-broker/wiki/Scalability Scalability]:
The message bus broker is a crucial infrastructure on modern linux
system, which is a hot-path for almost all IPC going on. Hence, the
broker should perform fast and be scalable to its users. dbus-daemon
has several **global** data-structures that affect the overall
scalability of independent message transactions. dbus-broker does not
employ any global data-structures (unless required by the spec), as
such any message transaction is only affected by the data provided by
the involved peers. Moreover, even for spec-defined global behavior,
dbus-broker avoids global data-structures, unless clients actually
make use of these obscure features. In several other cases,
dbus-daemon scales O(n) time looking up message targets and related
data. dbus-broker runs all these in O(log(n)) time.
* Linux-specific: The dbus-broker project was explicitly designed for
linux system, making use of many linux-specific APIs and behavior.
This allows mitigation of several possible DoS attacks.


== Scope ==
* Proposal owners:
** Fix regressions.
** Enabledbus-broker.service in system and user-global context of
systemd (via systemd presets).
** Pull in dbus-broker package from dbus package.

* Other developers:
** Watch for regressions

* Release engineering:
[https://pagure.io/releng/issues/7262 #7262]

** List of deliverables:
N/A

* Policies and guidelines:
No changes needed.

* Trademark approval:
No changes needed.
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org

F29 Self Contained Change: BINUTILS 2.30

Proposed Self Contained Change: BINUTILS 2.30
https://fedoraproject.org/wiki/Changes/BINUTILS230


Owner(s):
* Nick Clifton <nickc at redhat dot com>


Rebase the binutils package from version 2.29 .1 to version 2.30. This
will bring in bug-fixes and some new features.



== Detailed description ==
Switch the binutils package from being based on the 2.29.1 release of
the FSF binutils to being based on the 2.30 release. This release
includes bug-fixes and new features.


== Scope ==
* Proposal owners:
Replace the 2.29.1 source tarball with the 2.30 source tarball and
update the Fedora specific patches. (This work has already been
completed locally and is ready for comitting).

* Other developers:
None.

* Release engineering:
https://pagure.io/releng/issue/7282 - A mass rebuild is required.

** List of deliverables:
Just the binutils packages.

* Policies and guidelines:
No updates 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
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org

Thursday, February 15, 2018

[USN-3573-1] Quagga vulnerabilities

==========================================================================
Ubuntu Security Notice USN-3573-1
February 16, 2018

quagga vulnerabilities
==========================================================================

A security issue affects these releases of Ubuntu and its derivatives:

- Ubuntu 17.10
- Ubuntu 16.04 LTS
- Ubuntu 14.04 LTS

Summary:

Several security issues were fixed in Quagga.

Software Description:
- quagga: BGP/OSPF/RIP routing daemon

Details:

It was discovered that a double-free vulnerability existed in the
Quagga BGP daemon when processing certain forms of UPDATE message.
A remote attacker could use this to cause a denial of service or
possibly execute arbitrary code. (CVE-2018-5379)

It was discovered that the Quagga BGP daemon did not properly bounds
check the data sent with a NOTIFY to a peer. An attacker could use this
to expose sensitive information or possibly cause a denial of service.
This issue only affected Ubuntu 17.10. (CVE-2018-5378)

It was discovered that a table overrun vulnerability existed in the
Quagga BGP daemon. An attacker in control of a configured peer could
use this to possibly expose sensitive information or possibly cause
a denial of service. (CVE-2018-5380)

It was discovered that the Quagga BGP daemon in some configurations
did not properly handle invalid OPEN messages. An attacker in control
of a configured peer could use this to cause a denial of service
(infinite loop). (CVE-2018-5381)

Update instructions:

The problem can be corrected by updating your system to the following
package versions:

Ubuntu 17.10:
quagga 1.1.1-3ubuntu0.2
quagga-bgpd 1.1.1-3ubuntu0.2

Ubuntu 16.04 LTS:
quagga 0.99.24.1-2ubuntu1.4

Ubuntu 14.04 LTS:
quagga 0.99.22.4-3ubuntu1.5

After a standard system update you need to restart Quagga to make
all the necessary changes.

References:
https://www.ubuntu.com/usn/usn-3573-1
CVE-2018-5378, CVE-2018-5379, CVE-2018-5380, CVE-2018-5381

Package Information:
https://launchpad.net/ubuntu/+source/quagga/1.1.1-3ubuntu0.2
https://launchpad.net/ubuntu/+source/quagga/0.99.24.1-2ubuntu1.4
https://launchpad.net/ubuntu/+source/quagga/0.99.22.4-3ubuntu1.5

Wednesday, February 14, 2018

[USN-3572-1] FreeType vulnerability

==========================================================================
Ubuntu Security Notice USN-3572-1
February 14, 2018

freetype vulnerability
==========================================================================

A security issue affects these releases of Ubuntu and its derivatives:

- Ubuntu 17.10

Summary:

FreeType could be made to crash if it opened a specially crafted file.

Software Description:
- freetype: FreeType 2 is a font engine library

Details:

It was discovered that FreeType incorrectly handled certain files.
An attacker could possibly use this to cause a denial of service.

Update instructions:

The problem can be corrected by updating your system to the following
package versions:

Ubuntu 17.10:
  libfreetype6                    2.8-0.2ubuntu2.1

After a standard system update you need to restart your session to make
all the necessary changes.

References:
  https://www.ubuntu.com/usn/usn-3572-1
  CVE-2018-6942

Package Information:
  https://launchpad.net/ubuntu/+source/freetype/2.8-0.2ubuntu2.1

[USN-3571-1] Erlang vulnerabilities

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJahF37AAoJEGVp2FWnRL6TR9UP/1eNtVcg9rTeC8uD8pF26eXT
aCsKluhwjNtht39EifQ0InmiR4MgEggMrgb1VsG6Ntsoyt03o4XIpi/e+PXGX16m
M5AN2a89kwrtG5v/K8M9WE249V2dai00l/JErH3dMgkuN+Hq1dGMBRclutb9bs0z
TurkeLxL5xgQp+G/oDGhgR2YC4Sc6j1+eLiOoBmW96azswcXOn8h0N30RSsvevM5
s+KwZxQiRKUJlXsS4Lbzza6uvPopysIyvByfrGwJMpjAsL+zcaN+DhawteIiIaJ5
JJCVLzlH21gg+6YOaChvYYnR04YlgB+9B0fnApRhdGc+pvx9O4QATt+Rvj3Alhxz
3wHXC1Q2arSZqx1CCxaWh8KW3/AQFxRg85Su8p5T+4lJJlFetfgJocwX2XxWo6Vz
NdPWLCqRi4Vk69bHGQHARRrzdi0x88B1SS+v5M27Qn1InWEgEP3D8/dwkrPcb2Sw
q+7mYk8CBYSIZEbsSMDCgTUVKZzmHu8CZVY1OJyyPwswH1WhPSsoNbz+TDQQb+47
/CITSgAUX5pPO07yhVKWtLrDBer/8WbB2ck9cMUzSN91omiOtkKvooD+dnkKPd56
a5c4curIIaLxXo2YeHJF9H9FjdaD6c9qv2KOqlO47E9WPRXQM4KzDyZQxzsW9z21
gwzjFPj4InD5HyLHiN9U
=v+YV
-----END PGP SIGNATURE-----
==========================================================================
Ubuntu Security Notice USN-3571-1
February 14, 2018

erlang vulnerabilities
==========================================================================

A security issue affects these releases of Ubuntu and its derivatives:

- Ubuntu 17.10
- Ubuntu 16.04 LTS
- Ubuntu 14.04 LTS

Summary:

Several security issues were fixed in Erlang.

Software Description:
- erlang: Concurrent, real-time, distributed functional language

Details:

It was discovered that the Erlang FTP module incorrectly handled certain
CRLF sequences. A remote attacker could possibly use this issue to inject
arbitrary FTP commands. This issue only affected Ubuntu 14.04 LTS.
(CVE-2014-1693)

It was discovered that Erlang incorrectly checked CBC padding bytes. A
remote attacker could possibly use this issue to perform a padding oracle
attack and decrypt traffic. This issue only affected Ubuntu 14.04 LTS.
(CVE-2015-2774)

It was discovered that Erlang incorrectly handled certain regular
expressions. A remote attacker could possibly use this issue to cause
Erlang to crash, resulting in a denial of service, or execute arbitrary
code. This issue only affected Ubuntu 16.04 LTS. (CVE-2016-10253)

Hanno Böck, Juraj Somorovsky and Craig Young discovered that the Erlang
otp TLS server incorrectly handled error reporting. A remote attacker could
possibly use this issue to perform a variation of the Bleichenbacher attack
and decrypt traffic or sign messages. (CVE-2017-1000385)

Update instructions:

The problem can be corrected by updating your system to the following
package versions:

Ubuntu 17.10:
erlang 1:20.0.4+dfsg-1ubuntu1.1

Ubuntu 16.04 LTS:
erlang 1:18.3-dfsg-1ubuntu3.1

Ubuntu 14.04 LTS:
erlang 1:16.b.3-dfsg-1ubuntu2.2

After a standard system update you need to reboot your computer to make
all the necessary changes.

References:
https://www.ubuntu.com/usn/usn-3571-1
CVE-2014-1693, CVE-2015-2774, CVE-2016-10253, CVE-2017-1000385

Package Information:
https://launchpad.net/ubuntu/+source/erlang/1:20.0.4+dfsg-1ubuntu1.1
https://launchpad.net/ubuntu/+source/erlang/1:18.3-dfsg-1ubuntu3.1
https://launchpad.net/ubuntu/+source/erlang/1:16.b.3-dfsg-1ubuntu2.2

[USN-3570-1] AdvanceCOMP vulnerability

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJahF3pAAoJEGVp2FWnRL6TtGMP/0PnwI2z3XogDv6Cv6xfS2fP
zwYkSih7F/efjIUzvke8PpFnoadDdiOWzbgsUvnxi2lVSuMImcL5IgSZrj56+r0k
VAWh2/YVtYmajmSERzftCkRcM4bO75VDhfQN21IcaviyxAzlihRhgrr4XXIIJsYG
83QQ5JS2yH/nZs9XDMBFoUITTeNn+B4rLMKtSxj5hsH7Y0Ehb3Ziw1qy3TpJHl/S
pJA8BncbaZFF1HbJQAVgmjK7BpOuQgJ0QdPFb5Bs4OML7wfxkDg0tfLqZMtWmaAx
xL2+OjpsLc+gW8HIYf3yCk3cemvrUvgIOeUv2RkWdPIkG5hYvCN9mxdnd6hs83to
7//9PrZjUMOmGLrZzXmdBOFl+iInUkdW0DYWKXZh8yzLvYmWK2B8dwA1MLNKJIn0
mW5clpstfE0CZ8Dpg/pTIsdIZbIAmJOIuZU3CdZH4Hav1eRjv7FN/1OnrLvobvSf
ZxezgqgbEDZ2wIz3SyB+fBvgKQdTDdVFGiMgl8HjWwkcbW1Ds22K805nZLHcl1U0
uoN+cmRU8jLHIhqt7dUDjozWDW191PuwnQIbM8fZfMSlnwdMLuZUj4eoW7IFC/xR
ugKNP1vJ80JPq0WbjTO9Jj4rEsPVyT+NlYNmUQM5jrq5xg1ftH0CGg7guFFcuAmW
Dgic72oRjTv+GxaIGheb
=pgTX
-----END PGP SIGNATURE-----
==========================================================================
Ubuntu Security Notice USN-3570-1
February 14, 2018

advancecomp vulnerability
==========================================================================

A security issue affects these releases of Ubuntu and its derivatives:

- Ubuntu 17.10
- Ubuntu 16.04 LTS
- Ubuntu 14.04 LTS

Summary:

AdvanceCOMP could be made to crash or run programs if it opened a specially
crafted file.

Software Description:
- advancecomp: collection of recompression utilities

Details:

Joonun Jang discovered that AdvanceCOMP incorrectly handled certain
malformed zip files. If a user or automated system were tricked into
processing a specially crafted zip file, a remote attacker could cause
AdvanceCOMP to crash, resulting in a denial of service, or possibly
execute arbitrary code.

Update instructions:

The problem can be corrected by updating your system to the following
package versions:

Ubuntu 17.10:
advancecomp 2.0-1ubuntu0.1

Ubuntu 16.04 LTS:
advancecomp 1.20-1ubuntu0.1

Ubuntu 14.04 LTS:
advancecomp 1.18-1ubuntu0.1

In general, a standard system update will make all the necessary changes.

References:
https://www.ubuntu.com/usn/usn-3570-1
CVE-2018-1056

Package Information:
https://launchpad.net/ubuntu/+source/advancecomp/2.0-1ubuntu0.1
https://launchpad.net/ubuntu/+source/advancecomp/1.20-1ubuntu0.1
https://launchpad.net/ubuntu/+source/advancecomp/1.18-1ubuntu0.1

[HEADS UP] Package wireshark-gtk going away

Hi,

the wireshark-gtk is no longer supported by the upstream since
wireshark-2.4.0. You may have noticed that there is new GUI based on Qt
since wireshark-2.0. This GUI will become default and the GTK-based GUI
will be dropped and no longer provided. This change should appear in
Fedora 29.

--
Michal Ruprich
Associate Software Engineer

Email: mruprich@redhat.com
Web: www.cz.redhat.com
Red Hat Czech s.r.o., Purkyňova 115, 612 00, Brno, Czech Republic

_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org