Search results

...stickers at prominent places on our robots (there is one at the back side as well). It fostered some interest. I was talking to a member of the executiv "The FUDCon Brno 2008 in Brno, CZ has been announced a while ago (previously as being located in Prague, though). But only just yesterday, some basic facts

Self Contained Changes are: * changes to isolated/leaf package without the impact on other packages/rest of the d

# Hypermedia as the engine of application state (HATEOAS) - state transitions (e.g. changin ...at web services will gain some of the desirable properties of the web such as horizontal scalability, de-coupled clients and servers, reduced latency thr

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same nam = Ruby 3.1 =

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same nam ...cted packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

...e underlying system can be performed from a language running on .NET, such as C#. ...een queued to the systemd job queue. It can be any request to systemd such as a request to start a service or a request to restart the system. Every <cod

Self Contained Changes are: * changes to isolated/leaf package without the impact on other packages/rest of the d

Self Contained Changes are: * changes to isolated/leaf package without the impact on other packages/rest of the d

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same nam ...be kept in sync with the generic template: https://fedoraproject.org/wiki/Changes/EmptyTemplate}}

* GNOME 3 desktop environment -- GNOME 3 is the next generation of GNOME 3 by default. GNOME 3 is being developed with extensive

# rbergeron (3) # satellit_ (3)

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same nam The set of core GNU Toolchain packages for Fedora 41 are as follows:

=== 3. Переключение репозитариев === ...ime need to install the Rawhide release RPMs from the 3rd party repository as well (or the standard ones, if switching back).

In Announcements, we have "Announcing Fedora 8 Test 3 (7.92)!" === Announcing Fedora 8 Test 3 (7.92)! ===

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same nam [https://fedoraproject.org/w/index.php?title=Changes/SPDX_Licenses_Phase_1/ Phase 1] dealt with the official adoption of SPDX li

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same nam ...cted packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same nam The set of core GNU Toolchain packages for Fedora 39 are as follows:

...s://bodhi.fedoraproject.org/updates/FEDORA-2018-d2d222fe5c gnome-software-3.28.2-4.fc28] if you are testing F28 to F30 upgrades ...is most probably experiencing the issue because it was initially installed as FC21. After running `grub2-mkconfig -o /boot/grub2/grub.cfg` the boot entri

* jskladan (3) * nirik look into why grub2 isn't showing up as critpath in bodhi

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same nam ...cted packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.