Services/SoftwareRepository: Difference between revisions

From DcUsers
(Created page with "{{Template:Service | description = Packages repository, currently Debian packages only. Provide fixes and backported packages for DuckCorp. Specific sections can be created fo...")
 
mNo edit summary
Line 20: Line 20:
* '''extra''': other packages for any other use (desktop, various user tools…)
* '''extra''': other packages for any other use (desktop, various user tools…)


=== Build for this Repository ===
== Build for this Repository ==


To build for this repository you have to care about:
To build for this repository you have to care about:
Line 30: Line 30:
** for subsequent uploads (except binary only for another architecture) you will most likely use these sbuild options: -A
** for subsequent uploads (except binary only for another architecture) you will most likely use these sbuild options: -A


=== Upload to this Repository ===
== Upload to this Repository ==


First, sign with your GPG key (using ''debsign'').
First, sign with your GPG key (using ''debsign'').

Revision as of 19:29, 2 May 2018

Service 'SoftwareRepository'
Description Packages repository, currently Debian packages only. Provide fixes and backported packages for DuckCorp. Specific sections can be created for users. No prerequisite for read access.
Prerequisite None
Account Local (registration required) IPv6 Ready Yes
Security Notes This service is secure.

Access

To install packages you can add the following in your /etc/apt/sources.list:

deb https://repository.duckcorp.org/debian stretch dc-net

At the moment uploading is limited to users having shell access.

Sections

It is configured to allow these sections:

  • dc-net: packages automatically available to DC machines
  • extra: other packages for any other use (desktop, various user tools…)

Build for this Repository

To build for this repository you have to care about:

  • use a proper version numbering:
    • ~<suite> for backports
    • ~dc<i> / +dc<i> if there are DC-specific changes (the later can be appended to the backports suffix)
  • build with or without sources and orig tarball depending if this is your first upload to the DC repo or not
    • for a first upload, or NUR, you will most likely use these sbuild options: -s -A --force-orig-source
    • for subsequent uploads (except binary only for another architecture) you will most likely use these sbuild options: -A

Upload to this Repository

First, sign with your GPG key (using debsign).

You can upload using this dupload configuration snippet:

# dupload does not support FTP TLS :-/
$cfg{'duckcorp'} = {
       fqdn => "toushirou.duckcorp.org",
       method => "scpb",
       incoming => "/srv/ftp/ftp.duckcorp.org/repository/dc-debian-incoming",
       # The dinstall on ftp-master sends emails itself
       dinstall_runs => 1,
};

Technical Details

This service is made using: