How to Install and Uninstall python3-magic-wormhole-mailbox-server.noarch Package on Fedora 35

Last updated: October 05,2024

1. Install "python3-magic-wormhole-mailbox-server.noarch" package

Please follow the instructions below to install python3-magic-wormhole-mailbox-server.noarch on Fedora 35


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                python3-magic-wormhole-mailbox-server.noarch
            
                    
    
    Copied

2. Uninstall "python3-magic-wormhole-mailbox-server.noarch" package

Learn how to uninstall python3-magic-wormhole-mailbox-server.noarch on Fedora 35:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                python3-magic-wormhole-mailbox-server.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the python3-magic-wormhole-mailbox-server.noarch package on Fedora 35

Last metadata expiration check: 1:49:27 ago on Wed Sep 7 14:25:02 2022.
Available Packages
Name : python3-magic-wormhole-mailbox-server
Version : 0.4.1
Release : 7.fc35
Architecture : noarch
Size : 85 k
Source : python-magic-wormhole-mailbox-server-0.4.1-7.fc35.src.rpm
Repository : fedora
Summary : Securely transfer data between computers
URL : https://github.com/warner/magic-wormhole-mailbox-server
License : MIT
Description : This package holds the code for the main server that Magic-Wormhole
: clients connect to. The server performs store-and-forward delivery for
: small key-exchange and control messages. Bulk data is sent over a direct
: TCP connection, or through a transit-relay.
:
: Clients connect with WebSockets, for low-latency delivery in the happy
: case where both clients are attached at the same time. Message are
: stored to enable non-simultaneous clients to make forward progress. The
: server uses a small SQLite database for persistence (and clients will
: reconnect automatically, allowing the server to be rebooted without
: losing state). An optional “usage DB” tracks historical activity for
: status monitoring and operational maintenance.