We seem to be stalled on these two major blockers:
hackage-security: broken on mips/mipsel - could be fixed via
cryptohash-sha256 (#899166) or alternately patching to build
with cryptohash or cryptonite?
pandoc: broken on armhf (due to GHC bug?) and mips and s390x
(via cmark-gfm being broken
On Tue, Jan 25, 2011 at 12:00:37PM +0100, Aurelien Jarno wrote:
> That's indeed another option. Clint, what do you think about it? Note
> it's only something temporary until we fix the real issue on eglibc.
If the only downside is that fakeroot will be broken when backported
to earlier kFreeBSD ve
On Tue, Jan 06, 2009 at 12:35:53PM +0100, Luca Favatella wrote:
> I propose a patch against the jack-audio-connection-kit package
> (suggested by [debian porting]).
> I think changing
> #ifdef __APPLE__
> to
> #if defined(__APPLE__) || defined(__FreeBSD__) || defined(__FreeBSD_kernel__)
> should so
> Which version of libtool are you using? The only one that supports
> GNU/FreeBSD is my hacked package of 1.5, which is the APT repository
> and installed in khazad (/usr/bin/libtool)
ltmain.sh (GNU libtool) 1.5 (1.1220.2.1 2003/04/14 22:48:00)
(I'm using khazad's libtool.)
> If you're using th
> More seriously, does anyone know what POSIX says should happen here?
> I've Cced the bash and ash maintainers in case they have suggestions.
POSIX says that it should work. File bugs.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PRO
> Why bother porting non-base packages, since FreeBSD has linux
> emulation mode?
What? Why emulate when you can compile natively?
> It seems to me that dpkg and apt are not compatible with BSD
> ports. What debian-bsd needs is a good packaging system, that
> handles dependencies properly, dist
> We are mostly trying to create a better package system for FreeBSD in
> combination with the other good aspects of Debian. If I seem to recall
> the discussion at the beginn correctly.
What are "the other good aspects"?
> Well, I think we should leave the BSD libraries where they are and use
>
> Nice to hear. So what are now the important things to work on? I think
> we should try to revitalize the work on this port.
Well, firstly, I'm not what we're trying to create here. Are we
doing Debian with a Free/Open/NetBSD kernel?
If so, we need to identify any conflicts with the base system
> BSD uses its ports system to install the source code and
> build natively; while Linux seems to install the binaries
> and docs only. Why not offer the user both?
apt-get source -b is the Debian equivalent to the ports tree.
> How to integrate current system of BSD ports with Debian's sources?
Err.. why would you do that?
> So how much of the basic decisions have been made on Debian/BSD?
> Is there a project leader, any plans? Has anybody looked at how
> difficult it will be to port dpkg to FreeBSD?
I briefly tried with FreeBSD 3.3 (19991008-STABLE). Everything
but md5sum and dselect compiled with only a few lines
11 matches
Mail list logo
