Search results

  • ...kes all the mistakes". Instead we work more as one whole and we all accept responsibility for each other's actions (we trust each other, right? That's why we were as
    2 KB (359 words) - 13:01, 11 December 2020
  • ...leader is the Arch Linux representative in all legal matters. The primary responsibility of the Leader in this role is holding the [[DeveloperWiki:TrademarkPolicy|A
    5 KB (748 words) - 19:22, 6 March 2020
  • ...the problem will not be solved by reporting the bug to Arch developers.''' Responsibility for a bug is said to lie upstream when it is not caused through the distrib If a bug/feature is not under Arch's responsibility, report it upstream. See also [[#Reasons for not being a bug]].
    18 KB (2,916 words) - 05:20, 9 March 2022
  • ...u make, as well as any legal repercussion that result. Arch Linux bears no responsibility at all.}}
    6 KB (828 words) - 12:41, 16 May 2022
  • ...gned packages and a fully-signed set of packages must be made. This is the responsibility of the developers.
    8 KB (1,279 words) - 01:32, 5 December 2021
  • ...dex via a static path in {{ic|indexes.conf}} or a symlink - this will push responsibility for deduplicating results onto the search head and mitigate the advantage o
    10 KB (1,566 words) - 15:29, 18 February 2022
  • ...Discord's Terms of Service] and may get your account banned. You take all responsibility when using such packages. Avoid using outdated or abandoned clients, as the
    10 KB (1,491 words) - 15:54, 8 May 2022
  • ...hniques on systems, hosts or network ranges other than those under the own responsibility is illegal in quite a few jurisdictions. Double-check you scan your own hos
    12 KB (1,869 words) - 14:11, 12 June 2021
  • ...ack and forth on the word basis, deleting words etc. It is also Readline's responsibility to manage [[Readline#History|history]] of input commands. Last, but not lea
    14 KB (2,101 words) - 07:06, 29 January 2022
  • ...ed Windows session will be completely lost. Use this option under your own responsibility.}}
    14 KB (2,310 words) - 10:18, 21 February 2022
  • ...es not attempt to handle all corner cases. Users must be vigilant and take responsibility for maintaining their own system.
    17 KB (2,657 words) - 12:38, 16 May 2022
  • {{Note|The AUR is unsupported, so any packages you install are ''your responsibility'' to update, not pacman's. If packages in the official repositories are upd
    21 KB (3,247 words) - 17:20, 20 February 2022
  • ...reakage are misguided and unproductive, since upstream changes are not the responsibility of Arch devs.
    17 KB (2,704 words) - 12:57, 16 May 2022
  • {{Warning|It is the bubblewrap user’s responsibility to update the filesystem trees regularly.}}
    26 KB (3,780 words) - 08:37, 21 May 2022
  • ...u make, as well as any legal repercussion that result. Arch Linux bears no responsibility at all.}}
    26 KB (3,429 words) - 17:03, 18 March 2022
  • #3) With great power comes great responsibility.
    27 KB (1,083 words) - 18:53, 27 February 2022
  • ...It is your decision whether to trust their maintainers, and you take full responsibility for any consequences of using any unofficial repository.}}
    44 KB (5,960 words) - 13:49, 13 May 2022
  • ...t provide them directly as stated on their forum and frequently blames the responsibility on [https://developers.goodix.com/en/bbs/detail/1d331d41697e4fc6bd5beba55ec
    19 KB (2,838 words) - 11:47, 19 March 2022
  • ...ve layer. On the other hand, the child image becomes invalid and it is the responsibility of the user to clean it up.
    125 KB (19,979 words) - 09:11, 16 May 2022