AOSC

 

Welcome to Anthon Open Source Community! We are a group of free and open technology enthusiasts working hard for improvements.

Most good programmers do programming not because they expect to get paid or get adulation by the public, but because it is fun to program. -- Linus Torvalds

LATEST NEWS

  • "aosc-os-abbs" Repository Snapshots Migrated to Git bundlesSEPTEMBER 29, 2016

    Sometime ago, to ease the new packagers to get a copy of our complete ABBS tree (in certain network conditions), we have created a snapshot of our repository once a week in tarball format. Now, to reduce the file size and increase the usability, we decided to use the git bundle format.

    Now, you can find the snapshots at here.

    And here is how to use them:

    1. Grab the latest .bundle file, you can download it with your favorite download tool(s) (we won't blame you if you want to have a historical one...).

    2. Verify the integrity of the bundle file using git bundle verify <file>, if the check passed, you can then proceed to step 3, if errors found or corrupted file found, well, you would need to move back to step 1 and test your luck again (If you are stuck on this step, please file an issue here... and please have a nice sleep while we look into it).

    3. Once the file is checked, navigate to the folder you want to place the repository in and issue:

    Note

    Commands shown below are optional, if you want to contribute to abbs tree. But if you have no direct access to this tree, please change the URL to your personal fork:

    git clone <full_path_to_bundle_file> aosc-os-abbs # Name the folder whatever you like
    git checkout -b staging
    
    # Below are optional, if you want to contribute to abbs tree.
    # But if you have no direct access to this tree, please change the URL
    # to your personal fork.
    
    git remote set-url origin "https://github.com/AOSC-Dev/aosc-os-abbs.git"  
    git branch --set-upstream-to=origin/staging staging

    Then wait for git to prepare the repository for you, this should normally take several seconds and you are all set and good to go.

    Happy hacking, contributing and have a nice day!

    — Zixing Liu (liushuyu)

  • "aosc-os-abbs" Repository Snapshots Migrated to Git bundlesSEPTEMBER 29, 2016

    Sometime ago, to ease the new packagers to get a copy of our complete ABBS tree (in certain network conditions), we have created a snapshot of our repository once a week in tarball format. Now, to reduce the file size and increase the usability, we decided to use the git bundle format.

    Now, you can find the snapshots at here.

    And here is how to use them:

    1. Grab the latest .bundle file, you can download it with your favorite download tool(s) (we won't blame you if you want to have a historical one...).

    2. Verify the integrity of the bundle file using git bundle verify <file>, if the check passed, you can then proceed to step 3, if errors found or corrupted file found, well, you would need to move back to step 1 and test your luck again (If you are stuck on this step, please file an issue here... and please have a nice sleep while we look into it).

    3. Once the file is checked, navigate to the folder you want to place the repository in and issue:

    Note

    Commands shown below are optional, if you want to contribute to abbs tree. But if you have no direct access to this tree, please change the URL to your personal fork:

    git clone <full_path_to_bundle_file> aosc-os-abbs # Name the folder whatever you like
    git checkout -b staging
    
    # Below are optional, if you want to contribute to abbs tree.
    # But if you have no direct access to this tree, please change the URL
    # to your personal fork.
    
    git remote set-url origin "https://github.com/AOSC-Dev/aosc-os-abbs.git"  
    git branch --set-upstream-to=origin/staging staging

    Then wait for git to prepare the repository for you, this should normally take several seconds and you are all set and good to go.

    Happy hacking, contributing and have a nice day!

    — Zixing Liu (liushuyu)

  • "aosc-os-abbs" Repository Snapshots Migrated to Git bundlesSEPTEMBER 29, 2016

    Sometime ago, to ease the new packagers to get a copy of our complete ABBS tree (in certain network conditions), we have created a snapshot of our repository once a week in tarball format. Now, to reduce the file size and increase the usability, we decided to use the git bundle format.

    Now, you can find the snapshots at here.

    And here is how to use them:

    1. Grab the latest .bundle file, you can download it with your favorite download tool(s) (we won't blame you if you want to have a historical one...).

    2. Verify the integrity of the bundle file using git bundle verify <file>, if the check passed, you can then proceed to step 3, if errors found or corrupted file found, well, you would need to move back to step 1 and test your luck again (If you are stuck on this step, please file an issue here... and please have a nice sleep while we look into it).

    3. Once the file is checked, navigate to the folder you want to place the repository in and issue:

    Note

    Commands shown below are optional, if you want to contribute to abbs tree. But if you have no direct access to this tree, please change the URL to your personal fork:

    git clone <full_path_to_bundle_file> aosc-os-abbs # Name the folder whatever you like
    git checkout -b staging
    
    # Below are optional, if you want to contribute to abbs tree.
    # But if you have no direct access to this tree, please change the URL
    # to your personal fork.
    
    git remote set-url origin "https://github.com/AOSC-Dev/aosc-os-abbs.git"  
    git branch --set-upstream-to=origin/staging staging

    Then wait for git to prepare the repository for you, this should normally take several seconds and you are all set and good to go.

    Happy hacking, contributing and have a nice day!

    — Zixing Liu (liushuyu)

  • Updates to the Repository ServerSEPTEMBER 29, 2016

    Along with the removal of RPM packages from the repository server, we have also cleaned up our repository server (which is way over due).

    • Old OS1 and OS2 (AOSC OS from 2013 and 2014) files are moved to the os-archives directory.
    • The mirrorupdater script was rewritten (first since early 2014!), and posted on our repository-scripts Git repo.
      • DPKG repositories now contain a catalog that provides index to multiple versions of a same package, making downgrading packages a lot easier - when need be.

    With such major change to the repository server, we might be experiencing some unstability in service. If you have encountered any issue with updating, refreshing, and installing packages, please file an issue/complaint at aosc-os-abbs.

  • Termination of RPM Package ReleasesSEPTEMBER 29, 2016

    With deep apologies, I must announce that the RPM port of AOSC OS has failed due to the lack of attention and manpower, in addition to the confusing situation that Zypper and RPM are going through in the recent year (updates, RPM dependencies, and PackageKit), it seems no longer viable to maintain such a port (let alone there is absolutely no user for this port).

    RPM packages (/os-*/os3-rpm) were removed from the repository server just shy of 50 minutes ago.

    On the bright side, however. We will continue with completing Autobuild3's RPM backend, and possibly bring Pacman support in the forseeable future.

    — Mingcong (Jeff) Bai

  • AOSC's Google+ Page is here!

  • Fixes Now Available for GNOME Shell 3.22

  • AOSC OS Base and BuildKit Tarball Updates

  • Read more...

PROJECTS OVERVIEW

COMMON SERVICES

  • Public Clipboard

    Our public clipboard service (or pastebin) that you can use for all your clippy needs.

  • Community Repository

    Our community repository server, where AOSC OS installation medias, tarballs, packages, project documentation, etc. are stored.

  • IRC Logs

    Have a look at our chatter room!