From aurelien at aurel32.net Tue Apr 11 11:02:50 2017 From: aurelien at aurel32.net (Aurelien Jarno) Date: Tue, 11 Apr 2017 13:02:50 +0200 Subject: [Debian-ports-devel] [website] [PATCH] Remove a reference to debian-ports.org In-Reply-To: <20170312032020.10386-1-pabs@debian.org> References: <20170312032020.10386-1-pabs@debian.org> Message-ID: <20170411110250.cltlek5uym6nafnw@aurel32.net> On 2017-03-12 11:20, Paul Wise wrote: > --- > htdocs/archive.xhtml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/htdocs/archive.xhtml b/htdocs/archive.xhtml > index 42c42af..62da2c0 100644 > --- a/htdocs/archive.xhtml > +++ b/htdocs/archive.xhtml > @@ -45,7 +45,7 @@ >

Packages authentication

>

> If you want apt to verify the downloaded packages, you can either install the > - debian-ports-archive-keyring package or manually import debian-ports.org archive's key into apt: > + debian-ports-archive-keyring package or manually import the Debian ports archive key into apt: >

>
>   gpg --keyserver hkp://subkeys.pgp.net --recv-keys 2FF7A9F4

Thanks, I have applied the patch.


-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien at aurel32.net                 http://www.aurel32.net


From aurelien at aurel32.net  Tue Apr 11 11:06:18 2017
From: aurelien at aurel32.net (Aurelien Jarno)
Date: Tue, 11 Apr 2017 13:06:18 +0200
Subject: [Debian-ports-devel] [website] [PATCH] Sync list of mirrors
 with the official Mirrors.masterlist
In-Reply-To: <20170311054530.27020-1-pabs@debian.org>
References: <20170311054530.27020-1-pabs@debian.org>
Message-ID: <20170411110618.otv46qk5le2xjhdj@aurel32.net>

On 2017-03-11 13:45, Paul Wise wrote:
> Adds ftp.kr.debian.org and debian.nctu.edu.tw
> 
> Changes-from: https://anonscm.debian.org/cgit/mirror/mirror-masterlist.git/plain/Mirrors.masterlist
> ---
>  htdocs/mirrors.xhtml | 26 ++++++++++++++++++++++++++
>  1 file changed, 26 insertions(+)
> 
> diff --git a/htdocs/mirrors.xhtml b/htdocs/mirrors.xhtml
> index 43cdd17..7d9d4a9 100644
> --- a/htdocs/mirrors.xhtml
> +++ b/htdocs/mirrors.xhtml
> @@ -45,6 +45,32 @@
>            No
>            All
>          
> +        
> +          
> +          ftp.kr.debian.org
> +          KR
> +          
> +            http,
> +            ftp,
> +            rsync
> +          
> +          Yes
> +          No
> +          All
> +        
> +        
> +          
> +          debian.nctu.edu.tw
> +          TW
> +          
> +            http,
> +            ftp,
> +            rsync
> +          
> +          Yes
> +          No
> +          All
> +        
>        
>  
>        

Adding new mirrors

Thanks I have applied the patch. Note that we tried to contact the maintainers of these mirrors when moving debian ports to an official service so that we can continue sending them a push signal, but we never got any answer. I am glad the mirror team finally have been able to arrange that. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien at aurel32.net http://www.aurel32.net From pabs at debian.org Tue Apr 11 13:23:31 2017 From: pabs at debian.org (Paul Wise) Date: Tue, 11 Apr 2017 21:23:31 +0800 Subject: [Debian-ports-devel] [website] [PATCH] Sync list of mirrors with the official Mirrors.masterlist In-Reply-To: <20170411110618.otv46qk5le2xjhdj@aurel32.net> References: <20170311054530.27020-1-pabs@debian.org> <20170411110618.otv46qk5le2xjhdj@aurel32.net> Message-ID: <1491917011.9262.5.camel@debian.org> On Tue, 2017-04-11 at 13:06 +0200, Aurelien Jarno wrote: > Thanks I have applied the patch. Note that we tried to contact the > maintainers of these mirrors when moving debian ports to an official > service so that we can continue sending them a push signal, but we never > got any answer. I am glad the mirror team finally have been able to > arrange that. I'm not sure that is the case; at least the .tw mirror is outdated. I've asked on #debconf18-taiwan if anyone has contacts at nctu.edu.tw, which will be the venue for DebConf next year. -- bye, pabs https://wiki.debian.org/PaulWise -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From aurel32 at debian.org Tue Apr 11 15:11:26 2017 From: aurel32 at debian.org (Aurelien Jarno) Date: Tue, 11 Apr 2017 17:11:26 +0200 Subject: [Debian-ports-devel] [PATCH] Add automatic by-hand processing of d-i's raw-installer images In-Reply-To: <20170211215617.hwcr4rfomp3rdoki@debian> References: <20170211215617.hwcr4rfomp3rdoki@debian> Message-ID: <20170411151126.xivuhw3cwmmgwnlq@aurel32.net> Hi, On 2017-02-11 21:56, James Clarke wrote: > --- > > Hi, > Since debian-installer has now been fixed for (some) ports, the next > upload will see the buildds uploading installer images. Currently > mini-dak does not process these; this patch intends to function > similarly to dak's auto by-hand processing of d-i images. The > archive-byhand-di was taken from scripts/debian/byhand-di and slightly > modified to use mini-dak's config. > > I have tested this with a local mini-dak setup and it seems to work, > unpacking to the installer-$arch directory. However, I expect there are > things I have missed, and this may not be implemented in the way you > would like. Comments? Thanks for the patch and sorry for the delay. I haven't tried the patch, but after review it seems overall good. My main concern is that we should try to catch errors earlier than in the queue_accepted() function. See below for more detailed comments. > diff --git a/bin/archive-byhand-di b/bin/archive-byhand-di > new file mode 100755 > index 0000000..6443a4d > --- /dev/null > +++ b/bin/archive-byhand-di > @@ -0,0 +1,111 @@ > +#!/bin/bash > + > +. archive-lib > + > +set -u > +set -e > +set -o pipefail > + > +if [ $# -lt 5 ]; then > + echo "Usage: $0 filename version arch changes_file suite" > + exit 1 > +fi > + > +TARBALL="$1" # Tarball to read, compressed with gzip > +VERSION="$2" > +ARCH="$3" > +CHANGES="$4" # Changes file for the upload > +SUITE="$5" > + > +error() { > + echo "$*" > + exit 1 > +} I think this should be converted to use the log function, so that the reason for the failure is logged. It won't be propagated to the reject mail, but at least it will be available somewhere. [...] > diff --git a/bin/archive-queue b/bin/archive-queue > index 1268e68..f5eff0d 100755 > --- a/bin/archive-queue > +++ b/bin/archive-queue [...] > @@ -102,7 +108,7 @@ verify_gpg_signature () > verify_dpkg_signature () > { > local archive_file=$1 > - local files=`fetch_secure_files < $archive_file | grep '\.u\?deb$'` > + local files=`fetch_secure_files < $archive_file | grep '\.u\?deb$|\.tar\.gz$'` This won't work, dpkg-sig can't verify .tar.gz file (ok in practice dpkg-sig is not used, but well let's not break it). [...] > +queue_process_autobyhand_d_i_images () > +{ > + local changes_file=$1 > + local archive_file=$2 > + # Get full file path, since archive-byhand-di runs with CWD as bin_dir > + local file=$(readlink -f $3) > + local version=`fetch_field "Version" < $archive_file` > + local target_arches=`strip_gpg < $changes_file | fetch_field "Architecture"` > + local arch=`filter_real_arches $target_arches` > + local suite=`fetch_field "Distribution" < $archive_file` > + > + if test `echo $arch | wc -w` -ne 1 ; then > + log queue "queue_process_autobyhand_d_i_images ${archive_file##*/} $file changes has arches != 1: $arch" > + return 1 > + fi > + > + if ! (cd $bin_dir && ./archive-byhand-di $file $version $arch $changes_file $suite); then > + return 1 > + fi > + I understand that you would like to diverge as few as possible from the original dak version of byhand-di, but what would be the cost of not requiring changing CWD? I would prefer if possible that all scripts are called consistently. > @@ -212,6 +292,18 @@ queue_accepted () > local files_install="$files $changes_file $archive_file" > local suite=`fetch_field "Distribution" < $archive_file` > > + for file in $files; do > + if queue_is_autobyhand $changes_file $archive_file $file; then > + if queue_process_autobyhand $changes_file $archive_file $file; then > + log queue "queue_process_autobyhand_success ${archive_file##*/} $file" > + else > + script_error "queue_accepted" "$?" > + log queue "queue_process_autobyhand_failed ${archive_file##*/} $file" > + return 1 > + fi > + fi > + done > + > files_owner_perms $files_install > > if mv $files_install $accepted_dir; then We should probably check for possible errors earlier than in queue_accepted(), at least for the ones which can occur due to issues in the incoming files. Otherwise it means that no ACCEPTED or REJECTED mail is sent, and that the files stay in the uncheck directory. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien at aurel32.net http://www.aurel32.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From aurelien at aurel32.net Tue Apr 11 15:49:23 2017 From: aurelien at aurel32.net (Aurelien Jarno) Date: Tue, 11 Apr 2017 17:49:23 +0200 Subject: [Debian-ports-devel] [PATCH mini-dak] archive-queue: Send mail to the maintainer if it's one of the signing key's uids In-Reply-To: <20170302210246.32aygk7gczfjeg3b@debian> References: <20170302210246.32aygk7gczfjeg3b@debian> Message-ID: <20170411154923.4gikb45ankkkqjkp@aurel32.net> On 2017-03-02 21:02, James Clarke wrote: > --- > Hi Aurelien, > Instead of ignoring the Maintainer field, this patch will see if there's > a corresponding valid uid for the signing key and use that instead of > the primary uid. This will allow a buildd to have one shared GPG key > between all its local users (with a uid for each), whilst still stopping > unwanted messages going to the package maintainers. This also has a > noticeable affect for porters doing uploads, too, since it will go to > their preferred email address for Debian work, rather than whatever > their primary uid is. > > I've tested it locally and it seems to do the right thing, but it's > always possible I've missed unusual cases. The `sort -u` is in case GPG > ends up looking at any default keyrings, in which case the uid may > appear twice in the output. Given there's a `grep -Fx` to select only > lines which are the same as `$maintainer`, these should already be > identical, so that could be a `head -n 1` instead. Thanks, I have just pushed the changes. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien at aurel32.net http://www.aurel32.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From aurel32 at debian.org Tue Apr 11 19:17:45 2017 From: aurel32 at debian.org (Aurelien Jarno) Date: Tue, 11 Apr 2017 21:17:45 +0200 Subject: [Debian-ports-devel] [PATCH] Add automatic by-hand processing of d-i's raw-installer images In-Reply-To: <20170411151126.xivuhw3cwmmgwnlq@aurel32.net> References: <20170211215617.hwcr4rfomp3rdoki@debian> <20170411151126.xivuhw3cwmmgwnlq@aurel32.net> Message-ID: <20170411191745.altry3nypf5fgcgb@aurel32.net> On 2017-04-11 17:11, Aurelien Jarno wrote: > Hi, > > On 2017-02-11 21:56, James Clarke wrote: > > --- > > > > Hi, > > Since debian-installer has now been fixed for (some) ports, the next > > upload will see the buildds uploading installer images. Currently > > mini-dak does not process these; this patch intends to function > > similarly to dak's auto by-hand processing of d-i images. The > > archive-byhand-di was taken from scripts/debian/byhand-di and slightly > > modified to use mini-dak's config. > > > > I have tested this with a local mini-dak setup and it seems to work, > > unpacking to the installer-$arch directory. However, I expect there are > > things I have missed, and this may not be implemented in the way you > > would like. Comments? > > Thanks for the patch and sorry for the delay. I haven't tried the > patch, but after review it seems overall good. My main concern is that > we should try to catch errors earlier than in the queue_accepted() > function. See below for more detailed comments. In the meantime, I have pushed a patch to allow .tar.gz files in changes file. It's not ideal, but will allow the debian-installer tarballs to appear in the pool directory. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien at aurel32.net http://www.aurel32.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From glaubitz at physik.fu-berlin.de Tue Apr 11 19:23:40 2017 From: glaubitz at physik.fu-berlin.de (John Paul Adrian Glaubitz) Date: Tue, 11 Apr 2017 21:23:40 +0200 Subject: [Debian-ports-devel] [PATCH] Add automatic by-hand processing of d-i's raw-installer images In-Reply-To: <20170411191745.altry3nypf5fgcgb@aurel32.net> References: <20170211215617.hwcr4rfomp3rdoki@debian> <20170411151126.xivuhw3cwmmgwnlq@aurel32.net> <20170411191745.altry3nypf5fgcgb@aurel32.net> Message-ID: <2d67668c-7703-058c-f09d-40ccae34d492@physik.fu-berlin.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 04/11/2017 09:17 PM, Aurelien Jarno wrote: > In the meantime, I have pushed a patch to allow .tar.gz files in changes file. It's not ideal, but will allow the debian-installer tarballs to appear in > the pool directory. Cool, that's already a step in the right direction \o/. Really exciting to see all this progress! Thanks a lot to everyone involved! Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz at debian.org `. `' Freie Universitaet Berlin - glaubitz at physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAljtLTgACgkQdCY7N/W1 +RMUFA/9FalR1iykeCJ9W0WuSYZjNXD56gZclxek8nUZR6j/QU6kxp/GGkUuv85s 22YuhzXxhDJWnwT4s1Drr7sZkPZjtDTXX7yJtAbKL9a7zpbwdQT+OINvvJB2bsQd Y5JIDL9p88xYt02H+3BcP3ovn+6J3w6j+KGXPcxaF1ha5oHO4auD7fFyw9Tfc+VZ B+izeVNkL4nGbv21Q47BM5Y4gKuMjvRAzoLVj7WfpzRkbk40T0uro8LfGhZECJrW QAENJ2ZJKvBIzB39nRECYUeSgt0XYZXMWWk4qju0ly+XVcJsD0OqlYW5TYXx7og3 B+pu6Yz2XAb4pSqovbDjO8hw7ni0hO4AFUzqVbnqpIKEwN0MGGnfBkFmUAHJjekQ FfMsRVRgJ6Lacyj5Dh2CL4hDB0jfmcxmGK4gkLEkhl4h7wf8HAgL2+TspVPO14WD DZlgWEO6lrdBv4umIS9e2jA9wuroHkqD2jKkHCeg0HWnjJkXp+AYakAnZBP9zEHx S/2qAlKmb9QghvyqiBojTv1H3afsB5qajYrf3tYjgjtgq5Iur05YTb8+XYXPYgvi 6IJQbJrUkhmp4mZKujqLNv1k/+BCFlWkFST2qB9abCBIbWtCKUG89e1z/YZoWasd XV0bMxC336PsJL3nyJUIs/yWzJO7OjJH6GUGKHUWDjNSs5KMoco= =MxCy -----END PGP SIGNATURE----- From sthibault at debian.org Wed Apr 12 13:01:02 2017 From: sthibault at debian.org (Samuel Thibault) Date: Wed, 12 Apr 2017 15:01:02 +0200 Subject: [Debian-ports-devel] debian-installer now available in Ports In-Reply-To: <20170412125507.GD38395@pyro.eu.org> References: <98958442-55b8-17df-5ff7-8b32830196e0@physik.fu-berlin.de> <20170412125507.GD38395@pyro.eu.org> Message-ID: <20170412130102.lngmcflykhqv7dmp@var.youpi.perso.aquilenet.fr> Steven Chamberlain, on mer. 12 avril 2017 13:55:08 +0100, wrote: > I expect there might be problems trying to build linux arches from a > kfreebsd host. But we should try to find out, and then maybe fix it. FWIW, I have been building hurd-i386 images from a linux box for a long time without problems. Samuel From steve at einval.com Wed Apr 12 13:14:31 2017 From: steve at einval.com (Steve McIntyre) Date: Wed, 12 Apr 2017 14:14:31 +0100 Subject: [Debian-ports-devel] debian-installer now available in Ports In-Reply-To: <20170412125507.GD38395@pyro.eu.org> References: <98958442-55b8-17df-5ff7-8b32830196e0@physik.fu-berlin.de> <20170412125507.GD38395@pyro.eu.org> Message-ID: <20170412131431.GA15831@einval.com> On Wed, Apr 12, 2017 at 01:55:08PM +0100, Steven Chamberlain wrote: >John Paul Adrian Glaubitz wrote: >> Thus, I was wondering whether any volunteers would be willing to help building >> ISO images for the various architectures. > >I'm already doing this for kfreebsd-amd64, but only the jessie-kfreebsd >suite: >http://jenkins.kfreebsd.eu/jenkins/view/cd/job/debian-cd_jessie-kfreebsd/lastBuild/console >and I had to patch debian-cd before it worked. (Didn't yet find time to >file bugs or submit those patches). Please post them! >I could probably set up similar jobs for kfreebsd-* sid now. > >> It's not necessary to run debian-cd on the same architecture as the >> target architecture of the ISO images. Exactly. There are sometimes difficulties with the tools needed to set up boot files etc., but they tend to be portable. >I did not even realise that. So I will add kfreebsd-i386 next. > >I expect there might be problems trying to build linux arches from a >kfreebsd host. But we should try to find out, and then maybe fix it. We were happily building kfreebsd-* images from a Linux host, so I'd expect it to work OK. I've offered before: I don't have the time personally to work on building ports images, but I'm more than happy to help other people getting them building on our official infrastructure... -- Steve McIntyre, Cambridge, UK. steve at einval.com Who needs computer imagery when you've got Brian Blessed? From steven at pyro.eu.org Wed Apr 12 12:55:08 2017 From: steven at pyro.eu.org (Steven Chamberlain) Date: Wed, 12 Apr 2017 13:55:08 +0100 Subject: [Debian-ports-devel] debian-installer now available in Ports In-Reply-To: <98958442-55b8-17df-5ff7-8b32830196e0@physik.fu-berlin.de> References: <98958442-55b8-17df-5ff7-8b32830196e0@physik.fu-berlin.de> Message-ID: <20170412125507.GD38395@pyro.eu.org> Hello, John Paul Adrian Glaubitz wrote: > Thus, I was wondering whether any volunteers would be willing to help building > ISO images for the various architectures. I'm already doing this for kfreebsd-amd64, but only the jessie-kfreebsd suite: http://jenkins.kfreebsd.eu/jenkins/view/cd/job/debian-cd_jessie-kfreebsd/lastBuild/console and I had to patch debian-cd before it worked. (Didn't yet find time to file bugs or submit those patches). I could probably set up similar jobs for kfreebsd-* sid now. > It's not necessary to run debian-cd on the same architecture as the > target architecture of the ISO images. I did not even realise that. So I will add kfreebsd-i386 next. I expect there might be problems trying to build linux arches from a kfreebsd host. But we should try to find out, and then maybe fix it. Regards, -- Steven Chamberlain steven at pyro.eu.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 648 bytes Desc: Digital signature URL: From intermediadc at hotmail.com Wed Apr 12 14:15:47 2017 From: intermediadc at hotmail.com (luigi burdo) Date: Wed, 12 Apr 2017 14:15:47 +0000 Subject: [Debian-ports-devel] debian-installer now available in Ports In-Reply-To: <98958442-55b8-17df-5ff7-8b32830196e0@physik.fu-berlin.de> References: <98958442-55b8-17df-5ff7-8b32830196e0@physik.fu-berlin.de> Message-ID: Thanks for the great news! Luigi ________________________________ Da: John Paul Adrian Glaubitz Hi! Thanks to the recent efforts within the Debian Ports projects, debian-installer is finally available for the Debian Ports architectures [1]. Previously, the installer images had to be built manually because building on the buildds always required a testing repository to be available for a given architecture. With the latest release of debian-installer, the build falls back to the unstable and unreleased repositories for the required udebs. The generated d-i images for powerpc, kfreebsd-* and hurd-i386 can be found here: > ftp://ftp.debian.org/debian/dists/sid/main/installer-$ARCH For the remaining Ports architectures: > http://ftp.ports.debian.org/debian-ports/pool-$ARCH/main/d/debian-installer/ Now, since the process of building installer images no longer requires manual intervention, the process for building CD images has been simplified as well, still requires some manual work. Thus, I was wondering whether any volunteers would be willing to help building ISO images for the various architectures. A rough guide can be found in [2] from which the the d-i part can be omitted, however, a local mirror available through the filesystem is still necessary (see MIRROR in CONF.sh). So, reprepro needs to be used to set up a local mirror or the remote mirror needs to be mounted with a FUSE module or similar. In order to use the debian-installer images for building CD images, they have to be downloaded and extracted (for the remaining Ports architectures above) and placed into the directory pointed to by DI_DIR in the easy-build.sh script, e.g.: export DI_DIR="/srv/d-i/debian-installer/installer/build/tmp/cdrom/. Would be great if we could get several people work on this and create ISOs for alpha, hppa, powerpc, ppc64 and so on. Please note: It's not necessary to run debian-cd on the same architecture as the target architecture of the ISO images. Hence, using an amd64 host should be fine. Thanks, Adrian -------------- next part -------------- An HTML attachment was scrubbed... URL: From aurelien at aurel32.net Wed Apr 12 16:56:36 2017 From: aurelien at aurel32.net (Aurelien Jarno) Date: Wed, 12 Apr 2017 18:56:36 +0200 Subject: [Debian-ports-devel] Debian Ports no longer accepts SHA-1 signatures Message-ID: <20170412165636.mqkc3q4kzodfph5n@aurel32.net> Dear all, Following the changes on the main archive [1], mini-dak on the Debian Ports archive now requires that uploads are signed by a strong SHA 224 to 512 algorithm. The same way the .dsc and .changes files are now verified using the SHA-256 checksums. Please ensure that GPG is configured correctly. That should be the case for build daemons running sid, for the one using stable, please make sure that you add personal-digest-preferences SHA256 (or another strong algorithm) to ~/.gnupg/gpg.conf. To my knowledge, the only recent builds rejected due to this changes are the x32 ones built on frobozz. Daniel, could you please update the GPG configuration? Thanks, Aurelien [1] https://lists.debian.org/debian-devel-announce/2017/02/msg00007.html -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien at aurel32.net http://www.aurel32.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From oemb1905 at jonathanhaack.com Wed Apr 12 18:18:04 2017 From: oemb1905 at jonathanhaack.com (Jonathan Haack) Date: Wed, 12 Apr 2017 12:18:04 -0600 Subject: [Debian-ports-devel] debian-installer now available in Ports In-Reply-To: <98958442-55b8-17df-5ff7-8b32830196e0@physik.fu-berlin.de> References: <98958442-55b8-17df-5ff7-8b32830196e0@physik.fu-berlin.de> Message-ID: <276EE9D5-FEBE-49C5-8C75-078410A359A4@jonathanhaack.com> I would be willing to help with ppc and ppc64. I am just a self-trained sysadmin, however, so I cannot guarantee it will be quick or easy, but I use ppc machines as project machines all the time and so I want to help. I will read the resources below. Please email me next steps. Jonathan jonathanhaack.com > On Apr 12, 2017, at 6:40 AM, John Paul Adrian Glaubitz wrote: > > Hi! > > Thanks to the recent efforts within the Debian Ports projects, debian-installer > is finally available for the Debian Ports architectures [1]. Previously, the > installer images had to be built manually because building on the buildds always > required a testing repository to be available for a given architecture. With > the latest release of debian-installer, the build falls back to the unstable > and unreleased repositories for the required udebs. > > The generated d-i images for powerpc, kfreebsd-* and hurd-i386 can be found here: > >> ftp://ftp.debian.org/debian/dists/sid/main/installer-$ARCH > > For the remaining Ports architectures: > >> http://ftp.ports.debian.org/debian-ports/pool-$ARCH/main/d/debian-installer/ > > Now, since the process of building installer images no longer requires manual > intervention, the process for building CD images has been simplified as > well, still requires some manual work. > > Thus, I was wondering whether any volunteers would be willing to help building > ISO images for the various architectures. A rough guide can be found in [2] > from which the the d-i part can be omitted, however, a local mirror available > through the filesystem is still necessary (see MIRROR in CONF.sh). So, reprepro > needs to be used to set up a local mirror or the remote mirror needs to be > mounted with a FUSE module or similar. > > In order to use the debian-installer images for building CD images, they have > to be downloaded and extracted (for the remaining Ports architectures above) > and placed into the directory pointed to by DI_DIR in the easy-build.sh > script, e.g.: export DI_DIR="/srv/d-i/debian-installer/installer/build/tmp/cdrom/. > > Would be great if we could get several people work on this and create ISOs > for alpha, hppa, powerpc, ppc64 and so on. Please note: It's not necessary > to run debian-cd on the same architecture as the target architecture of > the ISO images. Hence, using an amd64 host should be fine. > > Thanks, > Adrian > >> [1] https://buildd.debian.org/status/package.php?p=debian-installer&suite=sid >> [2] https://wiki.debian.org/PortsDocs/CreateDebianInstallerImages > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaubitz at debian.org > `. `' Freie Universitaet Berlin - glaubitz at physik.fu-berlin.de > `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From glaubitz at physik.fu-berlin.de Wed Apr 12 18:29:47 2017 From: glaubitz at physik.fu-berlin.de (John Paul Adrian Glaubitz) Date: Wed, 12 Apr 2017 20:29:47 +0200 Subject: [Debian-ports-devel] debian-installer now available in Ports In-Reply-To: <20170412131431.GA15831@einval.com> References: <98958442-55b8-17df-5ff7-8b32830196e0@physik.fu-berlin.de> <20170412125507.GD38395@pyro.eu.org> <20170412131431.GA15831@einval.com> Message-ID: <1788966f-8e83-1a06-9e8f-104fff8cf5f8@physik.fu-berlin.de> Hi Steve! On 04/12/2017 03:14 PM, Steve McIntyre wrote: > I've offered before: I don't have the time personally to work on > building ports images, but I'm more than happy to help other people > getting them building on our official infrastructure... That's an offer I am happily picking up. Would it be possible to get an account on the CD building machine? My biggest grief with the CD building process is the need for syncing the repositories locally. I assume you have a means of mounting the FTP servers through NFS? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz at debian.org `. `' Freie Universitaet Berlin - glaubitz at physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 From steven at pyro.eu.org Wed Apr 12 19:34:31 2017 From: steven at pyro.eu.org (Steven Chamberlain) Date: Wed, 12 Apr 2017 20:34:31 +0100 Subject: [Debian-ports-devel] debian-installer now available in Ports In-Reply-To: <20170412125507.GD38395@pyro.eu.org> References: <98958442-55b8-17df-5ff7-8b32830196e0@physik.fu-berlin.de> <20170412125507.GD38395@pyro.eu.org> Message-ID: <20170412193430.GQ38395@pyro.eu.org> I've set up some additional jobs at http://jenkins.kfreebsd.eu/jenkins/view/cd/ and after much trial-and-error, there are now (untested) sid netinst images built for: hurd-i386 kfreebsd-amd64 kfreebsd-i386 powerpc You can find the .iso images within each job's workspace e.g.: http://jenkins.kfreebsd.eu/jenkins/view/cd/job/debian-cd_sid_hurd-i386/ws/build/ It's building on a kfreebsd-amd64 host, in a jessie-kfreebsd chroot, with current Git master of debian-cd, my patches for #860187 and #860204 applied, and the attached diff against CONF.sh. I started each build like this: $ export CODENAME=sid $ export ARCHES=hurd-i386 $ CONF.sh && ./build.sh Regards, -- Steven Chamberlain steven at pyro.eu.org -------------- next part -------------- A non-text attachment was scrubbed... Name: CONF.sh.diff Type: text/x-diff Size: 4600 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 648 bytes Desc: Digital signature URL: From steve at einval.com Wed Apr 12 19:41:15 2017 From: steve at einval.com (Steve McIntyre) Date: Wed, 12 Apr 2017 20:41:15 +0100 Subject: [Debian-ports-devel] debian-installer now available in Ports In-Reply-To: <1788966f-8e83-1a06-9e8f-104fff8cf5f8@physik.fu-berlin.de> References: <98958442-55b8-17df-5ff7-8b32830196e0@physik.fu-berlin.de> <20170412125507.GD38395@pyro.eu.org> <20170412131431.GA15831@einval.com> <1788966f-8e83-1a06-9e8f-104fff8cf5f8@physik.fu-berlin.de> Message-ID: <20170412194115.GI8529@einval.com> On Wed, Apr 12, 2017 at 08:29:47PM +0200, John Paul Adrian Glaubitz wrote: >Hi Steve! > >On 04/12/2017 03:14 PM, Steve McIntyre wrote: >> I've offered before: I don't have the time personally to work on >> building ports images, but I'm more than happy to help other people >> getting them building on our official infrastructure... > >That's an offer I am happily picking up. Would it be possible to get >an account on the CD building machine? My biggest grief with the CD >building process is the need for syncing the repositories locally. OK, let's go ahead with that. >I assume you have a means of mounting the FTP servers through NFS? No, the build machine has a full local mirror. debian-cd really wants to be able to write to the same filesystem, creating hard links as it goes. You'll need to get debian-ports mirrored to the build machine again - check with DSA for that. -- Steve McIntyre, Cambridge, UK. steve at einval.com < Aardvark> I dislike C++ to start with. C++11 just seems to be handing rope-creating factories for users to hang multiple instances of themselves. From steven at pyro.eu.org Wed Apr 12 20:01:18 2017 From: steven at pyro.eu.org (Steven Chamberlain) Date: Wed, 12 Apr 2017 21:01:18 +0100 Subject: [Debian-ports-devel] debian-installer now available in Ports In-Reply-To: <20170412194115.GI8529@einval.com> References: <98958442-55b8-17df-5ff7-8b32830196e0@physik.fu-berlin.de> <20170412125507.GD38395@pyro.eu.org> <20170412131431.GA15831@einval.com> <1788966f-8e83-1a06-9e8f-104fff8cf5f8@physik.fu-berlin.de> <20170412194115.GI8529@einval.com> Message-ID: <20170412200117.GA6374@pyro.eu.org> Steve McIntyre wrote: > On Wed, Apr 12, 2017 at 08:29:47PM +0200, John Paul Adrian Glaubitz wrote: > >I assume you have a means of mounting the FTP servers through NFS? > > No, the build machine has a full local mirror. debian-cd really wants > to be able to write to the same filesystem, creating hard links as it > goes. All I needed was a read-only NFS mount...? Regards, -- Steven Chamberlain steven at pyro.eu.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 648 bytes Desc: Digital signature URL: From dschepler at gmail.com Wed Apr 12 21:57:50 2017 From: dschepler at gmail.com (Daniel Schepler) Date: Wed, 12 Apr 2017 14:57:50 -0700 Subject: [Debian-ports-devel] Debian Ports no longer accepts SHA-1 signatures In-Reply-To: <20170412165636.mqkc3q4kzodfph5n@aurel32.net> References: <20170412165636.mqkc3q4kzodfph5n@aurel32.net> Message-ID: On Wed, Apr 12, 2017 at 9:56 AM, Aurelien Jarno wrote: > To my knowledge, the only recent builds rejected due to this changes are > the x32 ones built on frobozz. Daniel, could you please update the GPG > configuration? Done. -- Daniel Schepler From glaubitz at physik.fu-berlin.de Thu Apr 13 07:09:44 2017 From: glaubitz at physik.fu-berlin.de (John Paul Adrian Glaubitz) Date: Thu, 13 Apr 2017 09:09:44 +0200 Subject: [Debian-ports-devel] debian-installer now available in Ports In-Reply-To: <20170412193430.GQ38395@pyro.eu.org> References: <98958442-55b8-17df-5ff7-8b32830196e0@physik.fu-berlin.de> <20170412125507.GD38395@pyro.eu.org> <20170412193430.GQ38395@pyro.eu.org> Message-ID: <72c7f244-5060-596d-5072-49fe113162a5@physik.fu-berlin.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 04/12/2017 09:34 PM, Steven Chamberlain wrote: > You can find the .iso images within each job's workspace e.g.: http://jenkins.kfreebsd.eu/jenkins/view/cd/job/debian-cd_sid_hurd-i386/ws/build/ Ok, great. So, powerpc users have a way of performing an installation with up-to-date images - since some people were already asking. Anyone here on the debian-powerpc mailing list could test the images? > http://jenkins.kfreebsd.eu/jenkins/view/cd/job/debian-cd_sid_powerpc/ws/ Thanks, Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz at debian.org `. `' Freie Universitaet Berlin - glaubitz at physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAljvJDgACgkQdCY7N/W1 +RO1MRAAxzaRCuh58T51BjK9s4eIovwELFMLRrs000dpShcBkKqElPxLfj9s4QF3 6frG8GuHymJuPZj5iiq3S+GKET9o3MePm7+bxYK+1+HziUxJ9XcF32OTmrlNOKkR eY3t5God9IndnwsH1B5N6LoOZtv+/F+ATVcnG6FFqNABSQBHVwTBvuudcsydZExQ JiNb0t4TC1XPTH/xdomOPQJaDYqhznWReI34jgIQ2U42kw0HqngaT+gLbAqtItOo evP0XDGytYKbBHDv6GO+PNF/zz+9cuTlpp9sTspEmxOSA3zKojq3/ROR7QNC7j0z oHwj4GyJdNlRK2Fc3ty6nw6l422GlKJylCD51oa8+SxkIOW3uL0RH2MQ+bwCar1w ZFKhUOIWB8Xhsn939S+IrWiPUJ4uj+y+f1sSpgnj9dvRgIQxN+hwOiYWv/2ua9ep 0G3PZFTVcvNPQhATqqCf4gVvPrikgszwzb6LCuyBIC1kjIvB5q4Thp1OQiIZkzEv mljXFIK62jIOR26+/v5bBWzSrjMI7fSvKf6BTM6pzq3K929aDUEAor48NZEniJa4 E0jhdputDfdpEzJpMo3WqjZeBbzKcJxy1XqChOL8NefUCLV7JjwvplVGhHIDVGq3 HTWqvkbDc1BpY2nOfawyDuWbHGy6wri2ro56D/k35WCOab1csdY= =svIY -----END PGP SIGNATURE----- From steve at einval.com Thu Apr 13 15:29:49 2017 From: steve at einval.com (Steve McIntyre) Date: Thu, 13 Apr 2017 16:29:49 +0100 Subject: [Debian-ports-devel] debian-installer now available in Ports In-Reply-To: <20170412200117.GA6374@pyro.eu.org> References: <98958442-55b8-17df-5ff7-8b32830196e0@physik.fu-berlin.de> <20170412125507.GD38395@pyro.eu.org> <20170412131431.GA15831@einval.com> <1788966f-8e83-1a06-9e8f-104fff8cf5f8@physik.fu-berlin.de> <20170412194115.GI8529@einval.com> <20170412200117.GA6374@pyro.eu.org> Message-ID: <20170413152949.GC19708@einval.com> On Wed, Apr 12, 2017 at 09:01:18PM +0100, Steven Chamberlain wrote: >Steve McIntyre wrote: >> On Wed, Apr 12, 2017 at 08:29:47PM +0200, John Paul Adrian Glaubitz wrote: >> >I assume you have a means of mounting the FTP servers through NFS? >> >> No, the build machine has a full local mirror. debian-cd really wants >> to be able to write to the same filesystem, creating hard links as it >> goes. > >All I needed was a read-only NFS mount...? Yup - that works, but it's massively quicker to use hard links. -- Steve McIntyre, Cambridge, UK. steve at einval.com Is there anybody out there?