Package: deluged
Version: 1.3.12-1
Severity: normal
When I start deluged and some of my active torrents use https to connect
to the tracker, deluged hangs. Deleting the torrent from the state
files allows deluged to start, and adding the same torrent after it
starts works fine.
Downgrading
Package: sbuild
Version: 0.63.2-1.1~bpo60+1
Severity: normal
I discovered that the --add-depends-arch is being ignored and not
used at all, unless --arch-all is being used too. Since it should be
adding to the dependancy list for building architecture dependant bits,
it seems needing to build
Package: apt
Version: 0.9.11.3
Severity: normal
I just spent half an hour trying to figure out why I was getting the error:
E: This is not a valid DEB archive, it has no 'data.tar.gz', 'data.tar.bz2' or
'data.tar.lzma' member
Given I knew the package in question was supposed to use .xz, I
would
have the same lets backport $compressor-support in the future.
I was thinking that would be a better string. Avoid translation issues
in the future if additional types are added. The error could get pretty
long too.
Thanks.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist
Source: openjdk-6
Version: 6b27-1.12.5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
When building openjdk-6 on many architectures, the documentation package
ends up empty with no error indicating you shouldn't have tried.
It seems the problem
On Thu, May 16, 2013 at 01:38:47AM -0400, tony mancill wrote:
On 05/15/2013 01:05 PM, Len Sorensen wrote:
So the missing files in geronimo-jta-1.1-spec-java are:
wheezy/usr/share/java:
lrwxrwxrwx 1 root root 99 May 15 15:31 geronimo-jta_1.1_spec-1.1.1.jar -
../maven-repo/org/apache
On Thu, May 16, 2013 at 11:01:20AM -0400, Len Sorensen wrote:
That would appear to fix the problem.
I will try and see if that then solves the jetty compile problem (I
suspect it will).
And it did.
I have now patched maven-debian-helper with the patch from 688043 which
is already included
Package: jetty
Version: 6.1.26-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
I am trying to create a small subset of wheezy that is self contained,
and as part of building things, jetty failed to build. Strangely it looks
a lot like an old bug
hope it picks the
right one based on what the control file asks for.
If you could provide a build log, that would be helpful. If you'd
prefer, you can send it to me directly.
Will do.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
On Wed, May 15, 2013 at 11:36:47AM -0400, Cyril Brulebois wrote:
(Random #-changes reader.)
Len Sorensen lennartsoren...@ruggedcom.com (15/05/2013):
On Wed, May 15, 2013 at 11:17:30AM -0400, tony mancill wrote:
I am able to build the package in a clean wheezy chroot, so I'm not sure
On Wed, May 15, 2013 at 12:12:51PM -0400, Len Sorensen wrote:
I can confirm that is true.
On the other hand it seems if you recompile some of the dependancies it
uses then it breaks.
Now which dependancy could be breaking if you recompile it in wheezy to
cause this problem I wonder
On Wed, May 15, 2013 at 02:55:58PM -0400, Len Sorensen wrote:
And first guess got it:
If I build using wheezy official packages as build-deps, then jetty builds
fine. If I replace just libgeronimo-jta-1.1-spec-java_1.1.1-2_all.deb
with the one I rebuilt myself (in wheezy), then jetty fails
geronimo-jta_1.1_spec.jar -
../maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/1.1.1/geronimo-jta_1.1_spec-1.1.1.jar
I don't know if a change in maven or something else is responsible for
this not working correctly anymore.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist
wondering why it kept creating
partions wrong. What a strange bug this was.
Hopefully the installer can get updated to handle something newer than
parted 2.3 for the next release after wheezy.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
for.
mkpart primary 1024KiB -1s
also works perfectly.
It seems that if you use different units for the two values, and the
first value is 1, then it does something messed up.
Using 1.0MiB doesn't change the behaviour, it is still broken.
--
Len Sorensen
-- System Information:
Debian
would love to see it fixed for the next release after
that though.
* or just to drop the *.h, *.a and *.la from the main package and add
them only when somebody asks for them.
Well certainly including .h, .la and .a seems pointless if nothing ever
intends to use them outside quagga.
--
Len
to discourage
linking against the libraries.
I would leave the bug report open but not as serious, if nobody objects.
I have no problem with that.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
the shared library
into a seperate libquagga is the big question.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: quagga
Version: 0.99.22-1
Severity: serious
Justification: Policy 8.4
As far as I understand packaging policy, header files and static libraries
must go in a -dev package, and not be included in the main package.
After all most people running a program are not going to be compiling
add
Package: openswan
Severity: wishlist
Given the fork by the developers of openswan into libreswan, it would
be nice if Debian would package libreswan now instead of openswan.
Openswan doesn't really seem to have anything happening anymore given
there isn't really anyone left to work on it.
--
Package: dpkg
Version: 1.16.8
Severity: wishlist
We happen to have a small build daemon of our own that runs sbuild for
packages we submit. Since it is in a package itself, when it is upgraded
the environment variable DPKG_MAINTSCRIPT_PACKAGE is set when the daemon
is restarted, which is then
it wishlist after all, since deciding to ignore it could be
a valid choice. It does seem unfortunate to have the test suite get
confused by outside things setting variables the code cares about.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
That has fixed the problem for me.
No need to start patching grub-install.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
?
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: libnl-3-200
Version: 3.2.3-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
libnl3 fails to build since it uses asciidoc and hence needs
source-highlight. However asciidoc only recommends source-highlight
which means buildd's won't have
Package: libcaca
Version: 0.99.beta17-1
Severity: serious
Tags: patch
Justification: fails to build from source
libcaca fails to build due to not finding xcolor.sty and sectsty.sty
which are provided by latex-xcolor and texlive-latex-extra respectively.
As a result the package fails to build.
--
Package: dpkg
Version: 1.15.7.2
Severity: wishlist
I managed to have sufficiently few packages installed that I did not have
/usr/share/man/man7 when I tried to install postgresql-client-common
which has an alternative for various postgres man pages. This failed
due to update-alternatives being
Package: imagemagick
Version: 8:6.6.0.4-3
Severity: normal
I have seen this too. I am building on an 8 core xeon. If I use
DEB_BUILD_OPTIONS=parallel=8, then it almost never fails. If I use
DEB_BUILD_OPTIONS=parallel=16 then it almost always fails.
So there is some race condition in the
FTBFS package I
encountered in squeeze so far, and the fact it really isn't one is great.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
sometimes conflict. Build-conflicts would be nice to avoid, but at
least until a better solution is found, it would be better than nothing
and avoid more bugs being reported.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe
Package: elinks
Version: 0.12~pre5-2
Severity: serious
Justification: fails to build from source
Trying to compile elinks fails. This unfortunately happens both in
unstable, testing and stable (ouch).
This is the error:
[MAKE all] src/ecmascript/spidermonkey
make[4]: Entering directory
occurs.
Yeah I sure hope so.
Ludovic, is there an upload forthcoming, or is it okay for me to upload an NMU
that includes Len's patch? I'm attaching the debdiff for the upload.
Thanks.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
On Wed, Jan 12, 2011 at 11:54:59PM -0500, tony mancill wrote:
On 01/12/2011 09:08 AM, Len Sorensen wrote:
Package: atftpd
Version: 0.7.dfsg-9.2
Severity: important
Version 0.7.dfsg-9.1 broke atftpd in daemon mode. It now listens on a
random port number rather than the port number
.eng.lan (Postfix) with ESMTP id 3099214E30C; Thu, 12 Aug 2010
13:14:56 -0400 (EDT)
Received: from root by rceng03.eng.lan with local (Exim 4.72) (envelope-from
lennartsoren...@ruggedcom.com) id 1OjbMb-0005kH-QC; Thu, 12 Aug 2010
13:14:45 -0400
From: Len Sorensen lennartsoren
Package: atftpd
Version: 0.7.dfsg-9.2
Severity: important
Version 0.7.dfsg-9.1 broke atftpd in daemon mode. It now listens on a
random port number rather than the port number it is told to listen on.
Of course in inetd mode it works fine since inetd is responsible for
listening. 0.7.dfsg-9
if a port was not specified, use the one looked up from
services, otherwise use the one specified (it does the same thing already
below in the case no IP was specified).
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
Package: powerpc-ibm-utils
Version: 1.1.0-1
Severity: important
Tags: patch
ofpathname isn't working on my IBM p520. I managed to fix it with a
few lines of small changes.
Before:
rceng03:~# ofpathname /dev/sda
ofpathname: Could not find sysfs information for logical device /dev/sda.
After:
satisfied with those rules. I wanted periods allowed in
the name but certainly have no need for a leading period and it does
make it simpler to avoid relative paths when you avoid the leading period.
Looks great to me. Thanks.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist
can't.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
chroot if there
is any chroot in any config with an illegal name. So you can't even
use the valid ones when any invalid ones are defined.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Package: schroot
Version: 1.4.12-1
Severity: grave
I just upgraded schroot to the current version in testing, and now I
can't use it anymore because someone got the bright (not) idea that only
alphanumeric, dashes and underscores should be allowed in chroot names.
It was annoying enough when a
Package: login
Version: 1:4.1.4.2+svn3283-1
Severity: important
Please add the IBM pSeries console ports to /etc/securetty. Right now
only virtual consoles are supported, but not the real ones when running
on bare metal.
The real ones are named /dev/hvsi0 and /dev/hvsi1.
-- System Information:
Package: clisp
Version: 1:2.48-3
Severity: grave
Justification: renders package unusable
In trying to dist-upgrade today, I got a segfault in clisp.
Setting up clisp (1:2.48-3) ...
appear to have fixed the
problem. My iwlwifi (intel 5100) now seems to keep passing traffic again.
At least it hasn't died yet.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: linux-image-2.6.32-3-amd64
Version: 2.6.32-9
Severity: important
Tags: squeeze
The intel 5100 wireless on my thinkpad SL500 no longer works properly.
It works perfectly with 2.6.31, and it worked with at least 2.6.32-rc3
as well. Now however, it will connect, work for a few seconds (it
of the change logs appear to mention anything I recognize
as matching my problem. Well the changelog can't list everything.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
if they have been fixed yet.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: libxml-perl
Version: 0.08-1
Severity: important
Tags: patch
Justification: fails to build from source
If you try to build when your directory name is anything other than
libxml-perl-0.08 the packages builds without error but does not contain
the actualy perl module file.
The problem is
Package: libobject-realize-later-perl
Version: 0.18-1
Severity: important
Justification: fails to build from source
If you extract the source as libobject-realize-later-perl-0.18-1 rather
than the default libobject-realize-later-perl-0.18, then the package
builds without error but leaves out the
Package: libxml-regexp-perl
Version: 0.03-7
Severity: important
Tags: patch
Justification: fails to build from source
If you try to build when your directory name is anything other than
libxml-regexp-perl-0.03 the packages builds without error but does
not contain the actualy perl module file.
Package: libpod-escapes-perl
Version: 1.04-1
Severity: important
Tags: patch
Justification: fails to build from source
If building from a non default directory name (such as when using
sbuild), the package builds but silently fails to include the actual
perl module files.
The fix is to use the
Package: libtext-diff-perl
Version: 0.35-3
Severity: important
Tags: patch
Justification: fails to build from source
When building under sbuild the directory name isn't the default that
dpkg-source -x would pick. In cases like that (but really any where
the directory name is changed) the package
comma should be added. I have no idea how this
package EVER got into lenny in the first place like this. How did
it get built?
--
Len Sorensen
-- System Information:
Debian Release: 5.0.3
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: i386
Package: binutils-multiarch
Version: 2.18.1~cvs20080103-7
Severity: normal
binutils-multiarch breaks libbfd.a users since it diverts libbfd.a to
libbfd-single.a but does not in fact provide a libbfd.a itself. So if
you install binutils-dev to get libbfd.a, but binutils-multiarch is
installed you
Package: linux-headers-2.6.29-1-common
Version: 2.6.29-1
Severity: grave
Justification: renders package unusable
Trying to build anything against 2.6.29 headers on i386 fails due to a missing
file.
/usr/src/linux-headers-2.6.29-1-common/arch/x86/Makefile:41:
Package: quik
Version: 2.1-9
Severity: important
Justification: fails to build from source
Trying to build quik from source fails due to depending on asm/page.h which is
no longer
exported by the kernel sources.
If the #include is commented out, it builds, but then doesn't work. Seem the
/msg00662.html
[1] http://ctu.iuculano.it/procinfo-lenny/
I downloaded it, built it for i386, and ran it, and it didn't segfault,
and seems to work. I like that you seem to have adjusted the printout
to have room for 4 digit irqs now. Looks nicer that way.
--
Len Sorensen
--
To UNSUBSCRIBE
PROTECTED].
I do not consider this closed. You are wrong. Please reopen until it
is fixed. I was actually considering marking it RC for Lenny.
--
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
bug.
--
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: procinfo
Version: 18-1
Severity: important
When running on a modern server with many interrupts, procinfo
segfaults.
I have one MSI interrupt which is assigned number 1269. This causes
/proc/stat to have a very long 'intr' line since it has to show that
many interrupts. procinfo
Package: openssh-blacklist
Version: 0.1.1
Followup-For: Bug #481283
Please move these files to /usr/share/ssh in the Etch version as well.
It is very unexpected to have /etc go from 2MB to 6MB as part of a
security upgrade.
--
Len Sorensen
-- System Information:
Debian Release: 4.0
APT
Package: libcm-dev
Version: 0.1.1-3
Severity: normal
A number of packages provide opengl header files, not just MESA, so the
correct target to depend on is libgl-dev not xlibmesa-gl-dev. By
depending on xlibmesa-gl-dev any user with the nvidia-glx package
installed is unable to use libcm-dev
Package: texlive-base-bin
Version: 2007.dfsg.1-2
Followup-For: Bug #433481
I looked at these bug reports about mktexlsr going nuts and forking, and
I tried removing jadetex, but that didn't help. Removing latex-ucs
however did help. I encountered this trying to upgrade from Etch to
Lenny.
and does not apply.
The package build process is doing something weird to the patches rather
than just including them as is, and whatever it is doing is breaking
them.
Since the patch still doesn't work for 2.6.24, this bug isn't done yet.
--
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL
Package: jigit
Version: 1.15-2
Severity: normal
The jigit package mentions in the description that it has the utility
iso-image.pl for serving iso images directly from a jigdo file, but it
is not actually included in the package. It is present in the source
package of course but nothing takes
Package: snmptrapfmt
Version: 1.11
Severity: important
Tags: patch
I have a lot of switches sending traps on linkup/down and other events
which I receive using snmptrapd and log using snmptrapfmt (or at least
try to). Everytime I receive a trap however snmptrapfmt segfaults.
I tracked the
Package: grub
Version: 0.97-23
Severity: important
Tags: patch
If a file happens to use the last sectors on a device which is using LBA
mode access, grub will ask the bios to read past the end of the disk
which on some bioses causing a long delay (which looks like the system
is hung). I have
Package: grub
Version: 0.97-20
Severity: normal
Tags: patch
I am running with the current grub package compiled on a sarge system.
When I try to use the grub-reboot command to change the boot entry to
use on next boot as a one time choice, the /boot/grub/default is updated
to show 0:2 as
Package: snmpd
Version: 5.2.2-5
Severity: normal
Packagine 5.2.3 is pretty easy (compared to 5.3.x). It already includes
in the upstream patches 15_rh9-522 16_man_pages_section
17_man_pages_typo 22_net-snmp-5.2.x-sysObjectID which should be removed.
Everything else appears to just build as is.
Package: docbook-utils
Version: 0.6.14-1
Severity: important
Justification: fails to build from source
docbook-utils fails to build due to a missing dependancy on docbook,
which is only a suggested dependancy of some of the other packages
docbook-utils build-depends on.
Len Sorensen
-- System
installed only using 1.0.16-13.1
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: keepalived
Version: 1.1.11-3
Severity: important
Tags: patch
When keepalived starts up, it tries to enter master mode, but if it
detects the link is down on the interface it goes directly to the fault
state, without calling the notify script about the change to fault
state.
Similarly
to
solve the lack of help.
Great work. I will go check out your new packages.
Are your vim packages supposed to be 'native' rather than have an
upstream .orig.tar.gz and diff? Or is this a build mistake?
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
with nvu's build setup. If it did use the
externally available mozilla then this bug would have been solved long
ago since it was fixed in the mozilla upstream a few months ago.
Len Sorensen
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable
them about this.
vim should dereference the symlink to get the real file and use that
name for the locking so that all instances no matter which symlink they
go through would end up with the same lock file.
Len Sorensen
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT
the real one.
Len Sorensen
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.11-9-amd64-k8
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)
Versions of packages cowsay depends on:
ii
I don't see 2.2.0-7 in sarge yet (at least proposed updates on
ftp.debian.org when I connect still says 2.2.0-6) so I don't think this
bug should be closed until it actually makes it into the archive.
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
Until the fixed version is in _sarge_ gcc-3.4 is FTBFS which would count
as a RC bug.
Should I go file a FTBFS bug against gcc-3.4 instead pointing at this
one?
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: gcc-3.4
Version: 3.4.3-12
Severity: important
Justification: fails to build from source
Fixed in doxygen version in sid, but broken in sarge.
See bug #304659.
I believe this counts as RC for sarge.
Len Sorensen
-- System Information:
Debian Release: 3.1
APT prefers testing
APT
On Sun, May 01, 2005 at 04:43:36PM -0600, Marcelo E. Magallon wrote:
Hi Len,
On Tue, Apr 26, 2005 at 01:22:46PM -0400, Len Sorensen wrote:
This package still has no header files.
Nor will it have any. Here are the contents of
libosmesa6-dev_6.2.1-5_i386.deb:
drwxr-xr-x root/root
on Arm target ***/
+
+#define WORDSIZE 32
+#define HAVE_LONG_LONG
+#define ASHR2(x) ((x)2)
+#define BYTE_GENDER little_endian
+#define HAVE_GETRUSAGE
+
+#include unistd.h/* for the chdir() and isatty() functions */
+
#else
/*** no machine specified ***/
#error must edit config.h
Len
being in build.patch which cdbs does not permit. Removing
the patch for config.sub and config.guess from build.patch makes it
build fine.
Len Sorensen
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel
being in build.patch which cdbs does not permit. Removing
the patch for config.sub and config.guess from build.patch makes it
build fine.
Len Sorensen
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel
in sarge is rather unfortunate, especially when the machines failing are
the fastest machines you can get for building on.
Len Sorensen
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.10-9
) arch=$(arch) SUBDIRS=${SUBDIRS}
Which will pass the i386 arch as the CPU type and it will build
properly. This won't affect arm either (which already converts
arm3/arm4/arm5 etc to arm in the scripts) or any other arch since no
other arch is checked for explicitly.
Len Sorensen
-- System
On Wed, Apr 20, 2005 at 06:34:49PM +1000, Rob Weir wrote:
On Tue, Apr 19, 2005 at 09:30:00AM -0400, Len Sorensen said
This bug has now been fixed in CVS upstream. However until it is fixed
in Debian (sarge specifically) gcc-3.4 is technically FTBFS in sarge.
So this is a gcc problem
This bug has now been fixed in CVS upstream. However until it is fixed
in Debian (sarge specifically) gcc-3.4 is technically FTBFS in sarge.
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
search for attribute= and replace it
with attrs= in the file as part of the upgrade (perhaps tell the suer
and ask them if they want to make this required change).
Len Sorensen
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable
/ or something like that).
Len Sorensen
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-686-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages slapd depends
converting would just be a nice bonus, but many
things don't do that so that would be OK.
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
/README.Debian.gz or perhaps just build
conflict with autoconf2.13?
I decided not to flag this FTBFS since it can build from source just
fine when autoconf2.13 is not installed, but the problem does stem from
the syslog-ng sources to some extent.
Len Sorensen
-- System Information:
Debian Release: 3.1
Package: openswan
Version: 2.2.0-4
Severity: important
Justification: fails to build from source
libcurl2-dev does not exist on sarge anymore. Changing build-dep to
libcurl2-dev | libcurl3-dev fixes building. This is what many other
packages are doing already.
Len Sorensen
-- System
On Sat, Feb 12, 2005 at 06:01:44PM -0500, David Coe wrote:
Thanks for the report.
I don't have an ARM system to test on, so I wonder
if you can try a few things and let me know:
1) now that (I hope) you've recovered your system,
does gpart still report a seek failure when run against
on the disk using dd and running file to locate the start of
each partition so I could recreate it with fdisk. gpart would have been
easier I suspect.
Thanks
Len Sorensen
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing')
Architecture: arm (armv5tel)
Kernel
signed.
Len Sorensen
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: arm (armv5tel)
Kernel: Linux 2.4.27-5-rr
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages perl depends on:
ii libc6
95 matches
Mail list logo
