unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: 70081@debbugs.gnu.org
Cc: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Subject: [bug#70081] [PATCH 0/2] debootstrap: Add PureOS support.
Date: Fri, 29 Mar 2024 19:23:59 +0100	[thread overview]
Message-ID: <cover.1711668771.git.GNUtoo@cyberdimension.org> (raw)

Hi,

In the previous patchset I added Trisquel support in debootstrap and I could
not include the code that added PureOS support because debootstraping PureOS
didn't work due to a change in the PureOS repository structure.

Now that it's fixed upstream (in PureOS and/or newer debootstrap versions),
after installing the debootstrap included in this patchset we can easily
debootstrap PureOS byzantium:
    $ sudo -E debootstrap byzantium rootfs https://repo.puri.sm/pureos
    $ sudo chroot rootfs/ /bin/cat /etc/os-release
    ID=pureos
    NAME=PureOS
    PRETTY_NAME="PureOS 10 (Byzantium)"
    
    VERSION_ID="10"
    VERSION_CODENAME=byzantium
    
    HOME_URL="https://pureos.net/"
    SUPPORT_URL="https://puri.sm/faq/#faq-WherecanIfindoutmoreaboutPureOS"
    BUG_REPORT_URL="https://tracker.pureos.net/"
    
    LOGO=pureos-logo-icon

Denis 'GNUtoo' Carikli (2):
  gnu: Add pureos-archive-keyring.
  gnu: debootstrap: Use pureos-archive-keyring.

 gnu/packages/debian.scm | 34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)


base-commit: 0ff72d105ca03a82de6bb5193266fd05fce72daf
-- 
2.41.0





             reply	other threads:[~2024-03-29 18:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29 18:23 Denis 'GNUtoo' Carikli [this message]
2024-03-30  7:55 ` [bug#70081] [PATCH 1/2] gnu: Add pureos-archive-keyring Denis 'GNUtoo' Carikli
2024-03-30  7:55 ` [bug#70081] [PATCH 2/2] gnu: debootstrap: Use pureos-archive-keyring Denis 'GNUtoo' Carikli
2024-04-02 18:16 ` bug#70081: [PATCH 0/2] debootstrap: Add PureOS support Efraim Flashner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1711668771.git.GNUtoo@cyberdimension.org \
    --to=gnutoo@cyberdimension.org \
    --cc=70081@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).