On 2021-10-02, Graham Inggs wrote:
> * Which architectures are you committing to be an active porter for?
armhf, arm64
> * Please describe recent relevant porter contributions.
Maintaining u-boot (bootloader used on many arm64 and armhf plaforms),
arm-trusted-firmware (arm64 firmware), and oc
On 2020-11-20, Graham Inggs wrote:
> A friendly reminder about the porter roll call for bullseye.
>
> On Mon, 2 Nov 2020 at 22:23, Graham Inggs wrote:
>> We are doing a roll call for porters of all release architectures. If
>> you are an active porter behind one of the release architectures [1]
>
Control: severity 730833 important
On Tue, Feb 18, 2014 at 11:19:29PM +, Robert Millan wrote:
> On 18/02/2014 21:54, Vagrant Cascadian wrote:
> > On Tue, Feb 18, 2014 at 09:35:09PM +, Robert Millan wrote:
> >> On 18/02/2014 19:11, Vagrant Cascadian wrote:
> > If t
On Tue, Feb 18, 2014 at 09:35:09PM +, Robert Millan wrote:
> On 18/02/2014 19:11, Vagrant Cascadian wrote:
> > Looking for help from the *bsd porters on this... We haven't seen a
> > successful build of u-boot on kfreebsd since mid-2012...
> >
> > The short
10:09:36AM -0800, Vagrant Cascadian wrote:
> On Mon, Dec 16, 2013 at 08:43:05AM +, Ian Campbell wrote:
> > On Fri, 2013-12-13 at 13:18 -0800, Ryan Niebur wrote:
> Shipping a different set of includes (that would get out of sync) from another
> source package for building on non-li
On Tue, Jan 10, 2012 at 07:24:31PM +0100, Robert Millan wrote:
> El 10 de gener de 2012 0:21, Vagrant Cascadian ha escrit:
> > would each depend on the current kfreebsd-image-X-* packages, where X was
> > the
> > current preferred/default version in a given release.
>
&g
Source: kfreebsd-8
Severity: wishlist
please consider providing unversioned meta-packages for kfreebsd-image and
related packages, much like the linux-latest package is handled. for example:
kfreebsd-image-486, kfreebsd-image-amd64, kfreebsd-image-686,
kfreebsd-image-xen, etc.
would each de
reopen 550429
reassign 550429 kfreebsd-8
thanks
as far as i know, this is still an outstanding issue for the newer versions of
kfreebsd.
live well,
vagrant
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.deb
On Fri, Nov 13, 2009 at 08:58:23AM +0100, Petr Salinger wrote:
> I just built kfreebsd-8 from current SVN with those options.
> As a result, the kernel tried to get IP address during boot
> via DHCP indefinitely. Luckily kernel.old pointing to kfreebsd-7
> does not contain these options ...
> FWIW,
Package: kfreebsd-image-7.2-1-686
Version: 7.2-10
Severity: grave
Justification: renders package unusable
unfortunately, the fix to:
#550429: kfreebsd-7: add BOOTP kernel options for NFS Root support
causes repeated attempts to look for a BOOTP/DHCP response sufficient to start
NFS root with t
Package: kfreebsd-7
Version: 7.2-9
Severity: wishlist
please consider adding the BOOTP, BOOTP_COMPAT, BOOTP_NFSROOT and BOOTP_NFSV3
options to the kernel configurations. without the above defined options, it
requires a bootloader to set a laundry list of variables (including ip,
netmask, hwaddr an
Package: freebsd-utils
Version: 7.2-8
Severity: normal
when trying to mount nfs filesystems, it appears to be missing the mount_nfs
command:
mount 127.0.0.1:/opt/ltsp /mnt
mount: exec mount_nfs not found: No such file or directory
there appear to be commented out entries in debian/rules, bu
12 matches
Mail list logo
