Package: shunit2
Version: 2.1.2-1
Severity: critical
The top level makefile assumes that $(PWD) will be in the environment
for the current directory, but sudo doesn't pass this along. This
causes builds with sudo to remove /build /test and /tmp along with
their contents. GNU make sets CURDIR for
On at least mips and mipsel, pselect (and the backing system call pselect6)
end up returning EINVAL with some combinations of kernel and the libc in
unstable. Apt should probably handle this case in the same way as ENOSYS --
decide that pselect is broken and make do as best it can with select.
Package: apt
Version: 0.7.8
Severity: serious
dpkgpm.cc:856 of aptbzr looks like:
select_ret = pselect(max(master, _dpkgin)+1, &rfds, NULL, NULL,
&tv, &original_sigmask);
if (select_ret == 0)
continue;
else if (select_ret < 0
ssh 4.6p1 defaults to having challenge_response_authentication and
kbd_interaction_authentication to off. The shipped config file does
not set either option by default. This means that PAM is disabled by
default. A KbdInteractiveAuthentication yes or
ChallengeResponseAuthentication yes is needed
Package: ocsigen
Version: 0.5.0-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of ocsigen_0.5.0-1 on goedel by sbuild/alpha 99.99
> Build started at 20061209-1805
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelpe
Package: codeine
Version: 1.0.1-3.dfsg-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of codeine_1.0.1-3.dfsg-1 on goedel by sbuild/alpha 99.99
> Build started at 20061021-0906
[...]
> ** Using build dependencies supplied by package:
> Build-Dep
Package: xterm
Version: 222-2
Severity: grave
Setting up xterm (222-2) ...
Installing new version of config file /etc/X11/app-defaults/KOI8RXTerm ...
error in control file: `Format' value not specified at /usr/sbin/install-docs
line 699, line 22.
dpkg: error processing xterm (--configure):
subp
Package: mplayer
Version: 1.0~rc1~svn20199-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of mplayer_1.0~rc1~svn20199-1 on voltaire by sbuild/powerpc
> 99.99
> Build started at 20061025-1338
[...]
> ** Using build dependencies supplied by packa
Package: ecj-bootstrap-gcj
Version: 3.2.1-1
Severity: grave
upon removal of ecj-bootstrap-gcj, find starts recursing down / (with
errors), I'm thinking due to the find call in rebuild_db() of
rebuild-gcj-db. This happened while attemping to dpkg -P all of the build
depends of openoffice.org that
Package: gaim-otr
Version: 3.0.0-2
Severity: grave
gaim-otr is not installable with the current gaim in unstable.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sat, Sep 02, 2006 at 06:46:45PM -0700, Russ Allbery wrote:
> > I just confirmed that when I install the 1.4.4~beta1-1 krb5kdc,
> > whatever existing kdc is stopped and the new kdc binary ends up
> > running.
>
> Hm.
>
> I should have tested that more thoroughly; I went from the documentation
>
Package: dpkg
Version: 1.13.22
Severity: serious
start-stop-daemon's --stop option doesn't work when upgrading when
combined with --exec. As most daemons these days have abandoned "stop
in preinst, upgrade, start again in postinst" in favour of "upgrade,
restart in postinst", this means that upgr
Package: krb5
Version: 1.4.4~beta1-1
Severity: serious
krb5-kdc and krb5-admin (possibly other daemons?) pass --exec to
start-stop-daemon when attempting to stop the daemon. This doesn't work in
the case of upgrades, as the binary on disk is no longer the one the process
started with. This means
Package: clearsilver
Version: 0.10.3-2
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of clearsilver_0.10.3-2 on ball by sbuild/mips 99.9
> Build started at 20060705-1020
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: py
Package: dietlibc-dev
Version: 0.29-12
Severity: serious
Removing dietlibc-dev ...
/var/lib/dpkg/info/dietlibc-dev.prerm: line 6: syntax error: unexpected end of
file
dpkg: error processing dietlibc-dev (--purge):
subprocess pre-removal script returned error exit status 2
--
To UNSUBSCRIBE, e
Package: apt
Version: 0.6.44.1
Severity: serious
I'm not certain where this was introduced; I've been running a version in
experimental with pdiff support until upgrading to 0.6.44.1
apt-cache, apt-get source and similar fail with the following error
E: Unable to parse package file
/home/buildd/
Package: xmlstarlet
Version: 1.0.1-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of xmlstarlet_1.0.1-1 on ninsei by sbuild/i386 98
> Build started at 20060531-0138
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhel
Package: nvidia-settings
Version: 1.0+20060404-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of nvidia-settings_1.0+20060404-1 on ninsei by sbuild/i386 98
> Build started at 20060517-1950
[...]
> ** Using build dependencies supplied by package:
Package: gnucash
Version: 1.9.6-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of gnucash_1.9.6-1 on ninsei by sbuild/i386 98
> Build started at 20060514-2323
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: libltdl3-dev
On Thu, Apr 20, 2006 at 01:14:11PM +0200, Filippo Giunchedi wrote:
> hi,
> consider that array-util:
>
> Build-Depends: debhelper (>= 4.0.0), linux-source-2.6.15 | linux-source-2.6,
> libgtk1.2-dev, libglib1.2-dev, gdk-imlib1-dev, imlib11-dev, automake1.9 |
> automaken, autoconf
>
> but the build
For some reason, the package has this in debian/rules:
# Add here commands to compile the package.
#/usr/bin/xmkmf
/usr/bin/make
The call to xmkmf is commented out. This call is needed to both fix the
installation paths, and to get the correct build options for each architecture.
--
To UNSUBSC
Package: postgresql-8.1
Version: 8.1.3-4
Severity: serious
Removing postgresql-8.1 ...
/etc/init.d/postgresql-8.1: line 3:
/usr/share/postgresql-common/init.d-functions: No such file or directory
invoke-rc.d: initscript postgresql-8.1, action "stop" failed.
dpkg: error processing postgresql-8.1 (
Package: libopensync-plugin-evolution2
Version: 0.18-1
Severity: critical
There was an error while trying to autobuild your package:
> Automatic build of libopensync-plugin-evolution2_0.18-1 on ball by
> sbuild/mips 85
> Build started at 20060413-1708
[...]
> ** Using build dependencies suppli
Package: xorg-x11
Version: 6.9.0.dfsg.1-5
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of xorg-x11_6.9.0.dfsg.1-5 on ball by sbuild/mips 85
> Build started at 20060403-0041
[...]
> ** Using build dependencies supplied by package:
> Build-Depends
Package: sysklogd
Version: 1.4.1-17.1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of sysklogd_1.4.1-17.1 on mayer by sbuild/mipsel 85
> Build started at 20060113-1423
[...]
> make[1]: Entering directory `/build/buildd/sysklogd-1.4.1'
> gcc -O2
Package: pstngw
Version: 1.3.1-5
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of pstngw_1.3.1-5 on goedel by sbuild/alpha 85
> Build started at 20060112-1617
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>=
Package: xorg-x11
Version: 6.9.0.dfsg.1-2
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of xorg-x11_6.9.0.dfsg.1-2 on mayer by sbuild/mipsel 79
> Build started at 20060106-0905
[...]
> ** Using build dependencies supplied by package:
> Build-Depe
reassign 343861 libesd-alsa0
severity 343861 important
tag 343861 moreinfo
thanks
On Sun, Dec 18, 2005 at 12:31:17PM +0200, Martin-??ric Racine wrote:
> esound 0.2.36-1 does NOT work anymore since ALSA 1.0.10 entered testing.
Can you please provide some specifics of not working? Does it fail to
Package: flex
Version: 2.5.31-36
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of flex_2.5.31-36 on voltaire by sbuild/powerpc 79
> Build started at 20051212-0432
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: bison, ge
On Wed, Nov 16, 2005 at 11:33:35PM +0100, Moritz Muehlenhoff wrote:
> Debian Bug Tracking System wrote:
> > Changes:
> > gdk-pixbuf (0.22.0-11) unstable; urgency=high
> > .
> >* Fix for integer overflows in io-xpm.c which could be exploited to
> > execute
> > arbitrary code (CVE-2005-2
Package: debian-installer
Version: 20051018
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of debian-installer_20051018 on rem by sbuild/mipsel 69
> Build started at 20051019-0638
[...]
> ** Using build dependencies supplied by package:
> Build-De
On Mon, Oct 17, 2005 at 12:28:52PM +0200, Loic Minier wrote:
> On Mon, Oct 17, 2005, Ryan Murray wrote:
> > Sorry, but depending on gconf2 does not fix this. The prerm script needs to
> > not fail if gconf2 is unavailable.
>
> Can you -vv your remark? You want the dh_gc
reopen 329759
thanks
Sorry, but depending on gconf2 does not fix this. The prerm script needs to
not fail if gconf2 is unavailable.
signature.asc
Description: Digital signature
Package: tetex-bin
Version: 2.0.2-31
Severity: serious
libkpathsea3 is now built by libkpathsea3 -- tetex-bin needs to be updated
to not build libkpathsea3 packages anymore.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture
This appears to be upstream bugzilla #758, which is fixed in cvs on November
11th, 2004:
2004-11-11 Richard Sandiford <[EMAIL PROTECTED]>
[BZ #758]
* sysdeps/unix/sysv/linux/mips/configure.in (asm-unistd.h): Only
preprocess if it defines ABI-prefixed syscall names
reassign 331293 libc6
thanks
General timeline:
libc is upgraded, at keeps running fine.
libselinux is rebuilt, requiring GLIBC_2.3.4
libpam is rebuilt against the new libselinux
At this point, at entirely fails because the libc it was started with isn't
2.3.4 or higher. Rather than continually u
Package: php4-lasso
Severity: grave
Depends: phpapi-20020918
phpapi-20020918 isn't provided by anything.
phpapi-20050606 is, however.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked t
Package: xmms-oggre
Version: 0.3-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of xmms-oggre_0.3-1 on rem by sbuild/mipsel 69
> Build started at 20051003-1240
[...]
The version of libtool used to build this source package is too old to
correctl
Package: php4-syck
Version: 0.55-2
Severity: grave
There was an error while trying to autobuild your package:
> Automatic build of syck_0.55-2 on ninsei by sbuild/i386 69
> Build started at 20051002-2242
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 4.1
On Sun, Oct 02, 2005 at 09:09:49PM -0700, Thomas Bushnell BSG wrote:
> imlib+png2 is just the png2 version of imlib; since png2 (aka png10)
> is now gone, imlib+png2 is on its way out too.
I'll be uploading once my build-depends are installable again. Your change of
package name means I have to w
Package: oaf
Version: 0.6.10-4
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of oaf_0.6.10-4 on ball by sbuild/mips 65
> Build started at 20051001-2034
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>> 2.0.0)
> at won't execute any job at all and report the following in the logs :
>
> Oct 2 22:59:00 dino atd[18647]: PAM unable to
> dlopen(/lib/security/pam_unix.so)
> Oct 2 22:59:00 dino atd[18647]: PAM [dlerror: /lib/libselinux.so.1: symbol
> regexec, version GLIBC_2.3.4 not defined in file libc.so
reopen 329759
thanks
gconftool-2 isn't in libgconf2-4, it's in gconf2, which isn't depended on
by libgstreamer-gconf0.8-0, or any of it's dependencies.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wed, Sep 28, 2005 at 12:48:13AM -0500, Manoj Srivastava wrote:
> Sounds to me that the package in question is getting ahead of
> policy and deciding that the debconf transition is over. Well, is it
> just powerpc debian installer that build depends on kernel-images?
> Why? I am not s
severity 330445 serious
thanks
> The fact that kernel-package does not have these image
> packages use debconf is a bug (a normal bug, so far), and I am thus
> merging this report with the other "use debconf" reports.
http://release.debian.org/etch_rc_policy.txt
Point 4, Autobuilding.
Package: initrd-tools
Version: 0.1.82
Severity: serious
sh-3.00# dpkg -P --pending
(Reading database ... 8535 files and directories currently installed.)
Removing initrd-tools ...
Purging configuration files for initrd-tools ...
/var/lib/dpkg/info/initrd-tools.postrm: line 7: update-modules: comma
Package: linux-image-2.6.12-1-powerpc,linux-kernel-di-powerpc-2.6,kernel-package
Severity: serious
The problem:
* linux-kernel-di-powerpc-2.6 build-depends on kernel images.
* build daemons install packages in noninteractive mode
* the kernel images do not install successfully in noninteractive mo
Package: gcc-4.0
Version: 4.0.1-9
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of gcc-4.0_4.0.1-9 on voltaire by sbuild/powerpc 65
> Build started at 20050922-1710
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: dpkg-de
Package: libc6-dev
Version: 2.3.5-6
Severity: serious
/usr/include/bits/syscall.h on mips and mipsel only contains definitions for
the ABI-specific syscalls. The rest of the syscalls (suchs as SYS_pivot_root)
are missing, which is causing other packages to build without support for
the syscall, a
Package: libyehia0.5-dev
Version: 0.5.4-6
Severity: grave
The following packages have unmet dependencies:
libyehia0.5-dev: Depends: libyehia0.5-0 (>= 0.5.4-6) but it is not going to
be installed
Depends: libgc1 but it is not installable
E: Broken packages
libgc1 has been rem
Package: gwydion-dylan-dev
Version: 1:2.4.0RC3-1
Severity: grave
The following packages have unmet dependencies:
gwydion-dylan-dev: Depends: libgc1 but it is not installable
E: Broken packages
The following packages have unmet dependencies:
oo2c: Depends: libgc1 but it is not installable
E:
Package: oo2c
Version: 1.5.9-4
Severity: grave
The following packages have unmet dependencies:
oo2c: Depends: libgc1 but it is not installable
E: Broken packages
libgc1 is no longer in the archive, having been replaced with libgc1c2
-- System Information:
Debian Release: testing/unstable
APT
Package: flite
Version: 1.2-release-2
Severity: serious
The following command as a regular user fails to build flite from source:
dpkg-buildpackage -uc -us -B -rsudo
The problem is that the bin directory is created in the debian/rules clean
target (run as root), and the build target (run as a reg
Package: libsqlite3-0
Version: 3.2.1-1
Severity: grave
libsqlite3-0 sources the debconf module in it's preinst script, but doesn't
depend on it:
Unpacking libsqlite3-0 (from .../libsqlite3-0_3.2.2-2_powerpc.deb) ...
/var/lib/dpkg/tmp.ci/preinst: line 6: /usr/share/debconf/confmodule: No such
file
Package: dupload
Version: 2.6.3.1
Severity: grave
Great, you've added yet another layer of checks for gpg signatures,
duplicating checks in several other places after the upload. However,
you've now broken all of the buildds with this change. If the key cannot be
found to do the verification, yo
Package: dpkg
Version: 1.13.10
Severity: serious
dpkg doesn't set close-on-exec on the dpkg.log file, and it ends up being
left open while maintainer scripts run, and therefore being inherited by
daemons restarting.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
Package: icewm
Version: 1.2.22-2
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of icewm_1.2.22-2 on goedel by sbuild/alpha 42
> Build started at 20050719-0045
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>>
Package: libc6-s390x
Severity: serious
Tags: sarge, etch, sid
libc6-s390x is missing a depends on lib64gcc1 that causes gcc to fail to link
when -m64 is used on an s390 system.
I'm filling the bug here rather than on the gcc-VERSION packages because the
sparc64 packages have the dependency in lib
Package: alsaplayer
Version: 0.99.76-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of alsaplayer_0.99.76-1 on goedel by sbuild/alpha 42
> Build started at 20050626-2204
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: l
Package: ximian-connector
Version: 2.2.2-6
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of ximian-connector_2.2.2-6 on rem by sbuild/mipsel 33
> Build started at 20050524-0618
[...]
> ** Using build dependencies supplied by package:
> Build-Depe
Package: fltk1.1
Version: 1.1.6-4
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of fltk1.1_1.1.6-4 on ninsei by sbuild/i386 33
> Build started at 20050520-1525
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: cdbs (>= 0.2
Package: zaptel
Version: 1:1.0.7-4
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of zaptel_1:1.0.7-4 on ninsei by sbuild/i386 33
> Build started at 20050521-2001
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper
On Tue, May 17, 2005 at 12:49:30PM -0500, Jay Kline wrote:
> Alexander Sack wrote:
> | I did not found any hints on this in the bug report, so maybe it's
> worth asking:
> |
> | You see any unexpected messages in dmesg or any system logs? Are there any
> | errors in /var/log/XFree86.0.log?
>
> No,
On Thu, May 12, 2005 at 11:30:31AM -0500, Jay Kline wrote:
> |>| And what is in the user's ~/.xsession-errors ? I have a feeling your
> |>| problem is in the session startup, and nothing to do with gdm.
> |>|
> |>
> |>The file is blank. Note that the sesision type did not change, and this
> |>beh
On Thu, May 12, 2005 at 11:02:19AM -0500, Jay Kline wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ryan Murray wrote:
> | On Wed, May 11, 2005 at 08:48:20AM -0500, Jay Kline wrote:
> |
> |>After a recent upgrade of gdm, logins "fail". A user in
On Wed, May 11, 2005 at 08:48:20AM -0500, Jay Kline wrote:
> After a recent upgrade of gdm, logins "fail". A user inputs
> username/password/securID login, it succeeds, goes to a black screen,
> then back to login. Here is the output to daemon.log:
>
> gdm[23126]: gdm_slave_xioerror_handler: Fat
Package: evolution-data-server1.2
Version: 1.2.2-3
Severity: grave
There was an error while trying to autobuild your package:
> Automatic build of evolution_2.2.2-3 on solitude by sbuild/mipsel 27
> Build started at 20050505-1734
[...]
> ** Using build dependencies supplied by package:
> Build-
Package: nufw
Version: 1.0-2
Severity: serious
Tags: sid
There was an error while trying to autobuild your package:
> Automatic build of nufw_1.0-2 on goedel by sbuild/alpha 27
> Build started at 20050404-2338
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (
Package: blackbox
Version: 0.70.0-2
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of blackbox_0.70.0-2 on goedel by sbuild/alpha 27
> Build started at 20050429-1528
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: autocon
Package: djvulibre
Version: 3.5.14-4
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of djvulibre_3.5.14-4 on voltaire by sbuild/powerpc 27
> Build started at 20050423-2026
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: d
Package: nstx
Version: 1.1-beta6-2
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of nstx_1.1-beta6-2 on voltaire by sbuild/powerpc 27
> Build started at 20050403-1239
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhe
Package: elinks
Version: 0.10.4-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of elinks_0.10.4-1 on solitude by sbuild/mipsel 27
> Build started at 20050414-0031
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelpe
Package: fyre
Version: 1.0.0-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of fyre_1.0.0-1 on solitude by sbuild/mipsel 17
> Build started at 20050404-2335
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: libglade2-dev
Package: webauth
Version: 3.2.6-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of webauth_3.2.6-1 on r5k by sbuild/mips 27
> Build started at 20050420-2342
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>> 4
Package: tspc
Version: 2.1.1-4
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of tspc_2.1.1-4 on resume.rfc822.org by sbuild/mips 1.170.5
> Build started at 20050312-0402
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: cd
Package: plucker
Version: 1.8-4
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of plucker_1.8-4 on resume.rfc822.org by sbuild/mips 1.170.5
> Build started at 20050312-0412
[...]
> ** Using build dependencies supplied by package:
> Build-Depends:
Package: stk
Version: 4.2.0-3
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of stk_4.2.0-3 on solitude by sbuild/mipsel 17
> Build started at 20050323-1428
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 4.
Package: libdata-dumper-perl
Version: 2.121-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of libdata-dumper-perl_2.121-1 on goedel by sbuild/alpha
> 1.170.5
> Build started at 20050310-1833
[...]
> ** Using build dependencies supplied by packa
Package: xball
Version: 3.0-15
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of xball_3.0-15 on solitude by sbuild/mipsel 17
> Build started at 20050323-1532
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>>
Package: gtk-engines-mac2
Version: 1.0.3-2
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of gtk-engines-mac2_1.0.3-2 on remake by sbuild/mipsel 1.170.5
> Build started at 20050320-0824
The version of libtool used to build this source package is to
Package: udev
Version: 0.054-3
Severity: grave
The fix to #294968 moves the original /dev directory from a safe spot
outside of the udev /dev tree to a .static dir inside the udev tree,
only accessable to root. Unfortunately, many programs (such as mdadm)
that use device nodes often directly scan
Package: gauche
Version: 0.8.3-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of gauche_0.8.3-1 on solitude by sbuild/mipsel 17
> Build started at 20050320-1947
[...]
The version of libtool used to build this source package is too old to
correct
Package: beecrypt
Version: 2.2.0-pre1-4
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of beecrypt_2.2.0-pre1-4 on remake by sbuild/mipsel 1.170.5
> Build started at 20050215-1526
The version of libtool used to build this source package is too old
Why are we disabling the entire GTK testsuite because of a static linking
failure? I would rather have the static libraries not included (they aren't
useful on mips with the stated problem anyhow), and run all of the testsuite
that doesn't require the static libs/binaries.
Testsuites are a good t
Package: papaya
Version: 0.97.20031122-4
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of papaya_0.97.20031122-4 on solitude by sbuild/mipsel 1.170.5
> Build started at 20050205-0542
The version of libtool used to build this source package is too
Package: gnofin
Version: 0.8.4-2.1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of gnofin_0.8.4-2.1 on remake by sbuild/mipsel 1.170.5
> Build started at 20050204-2006
The version of libtool used to build this source package is too old to
correct
On Tue, Jan 25, 2005 at 03:49:28PM -0500, Branden Robinson wrote:
> * Fix xserver-xfree86's configure script to not die if Discover 1.x's
> discover command segfaults. Thanks to Kyle McMartin for reporting this
> problem and testing the fix.[1]
Yes, that was indeed the problem.
> The s
Package: xserver-xfree86
Version: 4.3.0.dfsg.1-10
Severity: grave
Preconfiguring packages ...
xserver-xfree86 failed to preconfigure, with exit status 139
(Reading database ... 88681 files and directories currently installed.)
Unpacking xserver-xfree86 (from
/xserver-xfree86_4.3.0.dfsg.1-10_i3
88 matches
Mail list logo