On Mon, Aug 13, 2007 at 04:52:53PM -0500, Peter Samuelson <[EMAIL PROTECTED]>
wrote:
>
> [Mike Hommey]
> > Frankly, I'm not even sure the bump of soname is necessary on the
> > library.
>
> That's an upstream question, though, right? Keeping an old soname in
> Debian when everyone outside Debia
On Aug 13, Stephan Seitz <[EMAIL PROTECTED]> wrote:
> iface bond0 inet manual
> slaves eth0 eth1
> pre-up /sbin/ifconfig bond0 up
pre-up ip link set $IFACE up
down ip link set $IFACE down
--
ciao,
Marco
signature.asc
Description: Digital signature
[Mike Hommey]
> Frankly, I'm not even sure the bump of soname is necessary on the
> library.
That's an upstream question, though, right? Keeping an old soname in
Debian when everyone outside Debian is using a new one would seem to
cause more problems than it avoids.
Of course the reverse is occ
Am Montag, den 13.08.2007, 15:50 -0400 schrieb Joey Hess:
> Policy is actually careful to set up the invarient that "-" anywhere in
> a version number means the package is not native. I don't know why the
> developers reference choses to ignore that. Is there something wrong
> with using a version
Bart Martens wrote:
> Now imagine that someone would do an NMU of dh-make-php. The right
> version would be 0.2.3-0.1 according to Debian Policy.
Actually, policy doesn't say any such thing. That syntax was invented by
the developer's reference. And it's IMHO dubious.
Consider two packages:
fo
On Mon, Aug 13, 2007 at 08:21:35PM +0200, Stephan Seitz wrote:
> > iface bond0 inet static
> >address 0.0.0.0
> >netmask 0.0.0.0
> >slaves eth0 eth1
>
> I would use:
> iface bond0 inet manual
Ah, I forgot about the inet manual method.
> slaves eth0 eth1
> pre
In debian.devel.user Guus Sliepen <[EMAIL PROTECTED]> wrote:
> Add the bonding module to /etc/modules, so that bond0 exists when the
> network interfaces are brought up. Then you can do something like:
>
> iface bond0 inet static
>address 0.0.0.0
>netmask 0.0.0.0
>slaves et
On Tue, Aug 14, 2007 at 01:25:49AM +1000, Russell Coker wrote:
> I want to have a server with two Ethernet links in a redundant configuration,
> and to bridge it as the primary interface. So far the below is the only
> configuration in /etc/network/interfaces that I can get to work.
>
> It wou
I want to have a server with two Ethernet links in a redundant configuration,
and to bridge it as the primary interface. So far the below is the only
configuration in /etc/network/interfaces that I can get to work.
It would be cleaner and clearer if I could have a separate bond0 device
specifi
On 2007-08-13, Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
> % type-handling -n ia64
> i386 darwin-i386 freebsd-i386 kfreebsd-i386 knetbsd-i386 netbsd-i386
pts seems to have problems with this:
http://packages.qa.debian.org/w/wine.html - it at least looks quite
ugly.
/Sune
--
To UNSUBSCRI
"Wesley J. Landaker" <[EMAIL PROTECTED]> writes:
> Hey folks,
>
> Is is possible to make the equivalent of an Architecture: any package except
> that it excludes one or two specific architectures?
>
> Basically, I'd like to be able to write, for example:
>
> Architecture: any [!ia64]
>
> I know
On Mon, Aug 13, 2007 at 08:51:31AM -0400, Jay Berkenbilt <[EMAIL PROTECTED]>
wrote:
>
> To all users of ICU, and particularly to maintainers of packages that
> depend upon ICU, I have uploaded a new ICU to experimental. This is a
> "draft" release, as they call it, of ICU 3.8. There are some ne
To all users of ICU, and particularly to maintainers of packages that
depend upon ICU, I have uploaded a new ICU to experimental. This is a
"draft" release, as they call it, of ICU 3.8. There are some new
interfaces and support for several new features as well as a number of
bug fixes.
Starting
Matthew Johnson <[EMAIL PROTECTED]> wrote:
Hi,
> I am the gbib maintainer and despite the fact that it is fairly
> unmaintained upstream I use it regularly and know of no good
> replacement. I would love to port it it to GTK2, and it is a fairly
> Are there any guides, howtos, instructions or an
>
> Perhaps a wishlist bug on pbuilder would be appropriate since keeping
> the build dir would indeed be useful.
>
especially to build a package twice, which is a release goal for Lenny.
Probably an option like --build-twice would be useful, too.
Cheers,
Bernd
--
To UNSUBSCRIBE, email to
15 matches
Mail list logo
