Re: Future of kFreeBSD in Debian unstable

[James Clarke <jrtc27@debian.org>]

On 2 May 2018, at 10:52, Svante Signell <svante.signell@gmail.com> wrote:
> On Mon, 2018-04-02 at 20:16 +0100, James Clarke wrote:
>> On 2 Apr 2018, at 20:04, Svante Signell <svante.signell@gmail.com> wrote:
>>> On Mon, 2018-04-02 at 19:33 +0200, Svante Signell wrote:
>>>> On Sat, 2018-03-31 at 10:51 +0100, James Clarke wrote:
>>>>> 
>>>>> Yeah, it hasn't been added yet, I guess to see if there are any
>>>>> comments
>>>>> from wb-team@buildd.debian.org first.
> 
> Hi again,
> 
> Sorry to bother you when preparing for your thesis, but I think we have some
> problems:
> 
> 1) No iso files are available any longer. Is seems like kfreebsd.eu is gone. How
> do we enable builds of the debian installer, at least mini.iso?
> https://d-i.debian.org/daily-images/kfreebsd-* is empty!

Normally the d-i builds run on the DSA porterboxes as a daily cron job. We
don't have anything similar for debian-ports and just do the occasional manual
build. I guess if we liaise with -boot people then we might be able to have a
cronjob on kamp publish its results (and possibly for debian-ports arches too).

> 2) People seems to want asdfasdf and io back. How?
> From https://www.debian.org/ports/kfreebsd-gnu/
> asdfasdf.debian.net (kfreebsd-amd64) and io.debian.net (kfreebsd-i386) are
> available to Debian developers for porting work.
> Who was hosting those boxes?

The DNS entries are Aurelien's who may be able to shed some light?

> 3) The buildd kamp is stuck in dependency loops due to circular dependencies and
> due to earlier versions of some packages not being available. 
> 
> kfreebsd-amd64: mpfr4-4.0.1:
> Add debian/libmpfr6.symbols.kfreebsd-amd64 created from the build
> see #897416
> 
> dpkg-buildpackage
> ...
> dpkg-checkbuilddeps: error: Unmet build dependencies: build-essential:native
> 
> build-essential 12.5:
> apt-get install build-essential
> The following packages have unmet dependencies:
>  build-essential : Depends: gcc (>= 4:7.3) but 4:7.2.0-1d1 is to be installed
>                    Depends: g++ (>= 4:7.3) but 4:7.2.0-1d1 is to be installed
> E: Unable to correct problems, you have held broken packages.
> 
> Workaround:
> Install build-essential 12.4
> wget snapshot.debian.org/archive/debian/20170917T214533Z/pool/main/b/build-
> essential/build-essential_12.4_kfreebsd-amd64.deb
> 
> Build and install gcc-7-7.3.0-17
> Install build-essential 12.5
> ...
> 
> kfreebsd-i386: mpclib3:
> mpclib3 1.1.0-1 build-depends on libmpfr-dev+libmpfr6>= 4.0.0 , which conflicts
> wit  libmpc3 < 1.1.0-1~
> 
> Solved by manually building libmpfr-dev+libmpfr6 4.0.0, removing the dependency
> on texlive-latex-base, which depends on texlive-binaries which build-depends on
> libmpfr-dev.
> 
> Build and install mpclib3
> Upgrade libmpfr6 to 4.01-1
> Build and install texlive-bin
> Build and install gcc-7-7.3.0-17
> Install build-essential 12.5
> ...
> 
> On IRC:
> youpi replied on #debian-hurd:
> (21:36:07) srs: youpi: Any ideas? (19:26:09) srs: jrtc27: or whoever knows:
> Seems like manually building and installing mpclib3 is needed: How?
> (21:36:07) srs: (19:26:55) srs: We have a (maybe more) lock-up situation !!
> (21:49:35) youpi: you can do that by hand
> (21:49:42) youpi: just chroot into the build chroot
> (21:50:09) youpi: build&install the lib by hand
> (21:50:13) youpi: so you can build the needed deb package
> (21:50:24) youpi: and then redo this with the deb package instead of manually-
> installed library
> (21:50:33) youpi: and the result of that, you can upload
> (21:51:04) youpi: (and better even redo yet another build, so that last build
> can be reproduced from the uploaded boostrap binaries
> 
> Do you think you (or somebody else) can aid me to build those needed packages on
> kamp?

Which bit do you need help with? There are the sid-kfreebsd-{amd64,i386}-sbuild
chroots; you can start a session with `schroot -b -c sid-...-sbuild -n foo`, run
commands inside the chroot with `schroot -r -c foo` (with sudo if you need to
install things) and end the session with `schroot -e -c foo`. /home isn't mounted
inside the session, so you may need to copy files into /run/schroot/mount/foo/.

James