On Tue, 21 Mar 2006 23:26:05 +0100
Matthieu Herrb <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I recently had to produce 'lspci -v' output for a machine running
> OpenBSD for some vendor. So I ported pciutils... Here's the result.
> It has some problems on macppc and sparc64 because of limitations in ou
On Wed, 22 Mar 2006, Uwe Dippel wrote:
> On Tue, 21 Mar 2006 14:50:30 +0100, Alf Schlichting wrote:
>
> > The following diff makes the ark archiver from kdeutils3 use gtar instead
> > of
> > OpenBSDs native tar(1).
>
> Almost OT:
> OpenBSD's tar also fails on longer path/filenames (haven't ch
Thinkpad T42 (i386)
# lspci
00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O
Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP
Controller (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (
On Tue, 21 Mar 2006 14:50:30 +0100, Alf Schlichting wrote:
> The following diff makes the ark archiver from kdeutils3 use gtar instead of
> OpenBSDs native tar(1).
Almost OT:
OpenBSD's tar also fails on longer path/filenames (haven't checked
properly; I'd guess around 100+ characters).
Replacing
On Wednesday 22 March 2006 02:52, Lars Hansson wrote:
> On Wednesday 22 March 2006 07:49, viq wrote:
> > I'm still verifying that, as on one box with older snapshot and older qt
> > and qt-mt i was able to build psi, but on a more current box (installed
> > less than a week ago, and now building a
On Wednesday 22 March 2006 07:49, viq wrote:
> I'm still verifying that, as on one box with older snapshot and older qt
> and qt-mt i was able to build psi, but on a more current box (installed
> less than a week ago, and now building a lot of various stuff from ports)
> psi fails building, apparen
Something is wrong with the way aterm uses the termios interface,
at least on OpenBSD.
Start aterm and watch the output of "stty -a".
The "status" special character is set randomly, more often it is not
even a control character, making it impossible to use certain letters
as program input.
The d
Matthieu Herrb wrote:
Hi,
I recently had to produce 'lspci -v' output for a machine running
OpenBSD for some vendor. So I ported pciutils... Here's the result.
It has some problems on macppc and sparc64 because of limitations in
our /dev/pci implementation. I hope to be able to fix that in the
Matthieu Herrb wrote:
Hi,
I recently had to produce 'lspci -v' output for a machine running
OpenBSD for some vendor. So I ported pciutils... Here's the result.
It has some problems on macppc and sparc64 because of limitations in our
/dev/pci implementation. I hope to be able to fix that in the
I'm still verifying that, as on one box with older snapshot and older qt and
qt-mt i was able to build psi, but on a more current box (installed less than
a week ago, and now building a lot of various stuff from ports) psi fails
building, apparently on stuff regarding idn. (and we're talking i38
Jacob Meuser wrote:
As far as I remember it, the consensus was to always bump with updates
and not bother guessing whether it's compatible or not?
they are claiming API/ABI compatability in the release notes, so
I don't think this would be guessing.
I'm fine with not bumping the .so version,
On Tuesday 21 March 2006 17:26, Matthieu Herrb wrote:
> Hi,
>
> I recently had to produce 'lspci -v' output for a machine running
> OpenBSD for some vendor. So I ported pciutils... Here's the result.
> It has some problems on macppc and sparc64 because of limitations in our
> /dev/pci implementatio
On Tue, Mar 21, 2006 at 11:26:05PM +0100, Matthieu Herrb wrote:
| Hi,
|
| I recently had to produce 'lspci -v' output for a machine running
| OpenBSD for some vendor. So I ported pciutils... Here's the result.
| It has some problems on macppc and sparc64 because of limitations in our
| /dev/pci
Hi,
I recently had to produce 'lspci -v' output for a machine running
OpenBSD for some vendor. So I ported pciutils... Here's the result.
It has some problems on macppc and sparc64 because of limitations in our
/dev/pci implementation. I hope to be able to fix that in the future.
--
Matthieu
Hannah Schroeter [2006-03-21, 19:18:32]:
> Hello!
>
> Could this (and the following commit) affect/fix the problem with
> erlang's configure stuff on amd64? Alas, I can't test that myself,
> because I don't have any amd64 box at my hands.
>
> Kind regards,
>
> Hannah.
>
> - Forwarded messag
On Tue, Mar 21, 2006 at 02:50:30PM +0100, Alf Schlichting wrote:
> Hello!
>
> The following diff makes the ark archiver from kdeutils3 use gtar instead of
> OpenBSDs native tar(1).
> With our native tar(1) ark errors out because arks wants to use some
> GNU-extensions. While it would be possible
Hello!
Could this (and the following commit) affect/fix the problem with
erlang's configure stuff on amd64? Alas, I can't test that myself,
because I don't have any amd64 box at my hands.
Kind regards,
Hannah.
- Forwarded message from Otto Moerbeek <[EMAIL PROTECTED]> -
From: Otto Moer
Ian Darwin dixit:
[ /proc ]
> I had thought it was necessary, but have run without it.
The docs say procfs -o linu and /emul/linux/etc/mtab (empty)
were needed, didn't try without...
> Or even just patch out javaldr altogether, if what it wants to do
> can't be done in our environment?
Just pat
On Tue, Mar 21, 2006 at 11:43:15AM +0100, Moritz Grimm wrote:
> Jacob Meuser wrote:
> >>Should the major of the library be changed given this is API/ABI
> >>compatible with alpha4 though?
> >
> >I think the library version should not change.
>
> As far as I remember it, the consensus was to always
On Tue, Mar 21, 2006 at 03:13:34AM -0800, John Danks wrote:
> On 3/19/06, Jacob Meuser <[EMAIL PROTECTED]> wrote:
> > The bsdav package is a set of programs for audio and video reading and
> > writing. The programs use BSD native devices and the source code is
> > free-as-in-BSD licensed as well.
On Tue, Mar 21, 2006 at 11:38:47AM +0100, Tobias Ulmer wrote:
> On Mon, Mar 20, 2006 at 02:52:46PM -0800, Jacob Meuser wrote:
> > On Mon, Mar 20, 2006 at 02:31:07PM -0500, Mathieu Sauve-Frankel wrote:
> > > On Sat, Mar 18, 2006 at 04:44:56PM -0800, Jacob Meuser wrote:
> > > > On Fri, Mar 17, 2006 a
just did it clean on 3.9-snapshot . No Java, no procfs - Seems to work
fine.
You da man!
Tobias Ulmer wrote:
Attached is a port that for the binary version of OpenOffice. I just
wanted to hear, if it's worth my time to continue and extend (other
languages as subpackages) this port or if I jus
On Tue, Mar 21, 2006 at 02:50:30PM +0100, Alf Schlichting wrote:
> Hello!
>
> The following diff makes the ark archiver from kdeutils3 use gtar instead of
> OpenBSDs native tar(1).
> With our native tar(1) ark errors out because arks wants to use some
> GNU-extensions. While it would be possible
Hi...
I'm having a problem building gtk+2 from ports today.
I'm running 3.9-current/amd64 as of March 19th.
I can post the complete build log if you need, but since it is large and that it
might be a known and/or temporary problem, I'd rather only post the error for
now.
But if you need any infor
Srebrenko Sehic [Sat, Mar 11, 2006 at 11:34:47PM +0100] wrote:
>Attached is an update bumping databases/p5-DBI to 1.50 (latest). Our
>1.45 is 1? years old. Changelog for p5-DBI is available at
>http://search.cpan.org/~timb/DBI-1.50/Changes
>
>Update passed regression tests. I've also tested p5-DBD-
Hi,
Since there's now close to no chance that devel/gstreamer will be fixed
in time for release, I think it should be marked as broken at least on
amd64 (I don't have other arches to see if it works or n
Hi!
On Mon, Mar 20, 2006 at 11:06:33PM +0100, Tobias Ulmer wrote:
>Attached is a port that for the binary version of OpenOffice. I just
>wanted to hear, if it's worth my time to continue and extend (other
>languages as subpackages) this port or if I just produced crap that nobody
>needs.
>Current
Hello!
The following diff makes the ark archiver from kdeutils3 use gtar instead of
OpenBSDs native tar(1).
With our native tar(1) ark errors out because arks wants to use some
GNU-extensions. While it would be possible to fix ark to use the native
tar(1), i think it makes more sense to default
Attached is a port that for the binary version of OpenOffice. I just
wanted to hear, if it's worth my time to continue and extend (other
languages as subpackages) this port or if I just produced crap that
> nobody needs.
I find it handy. I previously had copied the files over from a Linux box
a
On 3/19/06, Jacob Meuser <[EMAIL PROTECTED]> wrote:
> The bsdav package is a set of programs for audio and video reading and
> writing. The programs use BSD native devices and the source code is
> free-as-in-BSD licensed as well.
Compiles fine on -current i386. I'm mainly interested in the audio
On Mon, Mar 20, 2006 at 02:52:46PM -0800, Jacob Meuser wrote:
> On Mon, Mar 20, 2006 at 02:31:07PM -0500, Mathieu Sauve-Frankel wrote:
> > On Sat, Mar 18, 2006 at 04:44:56PM -0800, Jacob Meuser wrote:
> > > On Fri, Mar 17, 2006 at 01:29:05PM -0800, Jacob Meuser wrote:
> > > > On Thu, Mar 09, 2006 a
Jacob Meuser wrote:
Should the major of the library be changed given this is API/ABI
compatible with alpha4 though?
I think the library version should not change.
As far as I remember it, the consensus was to always bump with updates
and not bother guessing whether it's compatible or not?
32 matches
Mail list logo
