-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am pleased to announce two new Project Leader's Delegates as per section
8.2 of the Debian Constitution.
First, as some of you may be aware, in May of this year I began looking for
someone to help me handle the details of donations to Debian,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello. This is another in my ongoing series of messages as your DPL. I
certainly didn't intend to get from mid May to mid September without a
message! I'll try to be more regular about these in the future...
Rather than try to tackle every subject
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
Some of you noticed that the Linux Weekly News, aka lwn.net, changed to a
subscription model for full access, and wondered if Debian developers could
arrange some sort of group access.
I'm pleased to report that the answer is yes! LWN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Below is a message from Martin (Joey) Schulze, the current Vice President
of Software in the Public Interest (SPI). SPI is the non-profit corporation
that was formed to provide Debian with a legal and financial existence in the
United States, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Debian is a member project of Software in the Public Interest, Inc, which is
a non-profit corporation under US law that was created to provide legal and
financial existence for projects like Debian. More information about SPI is
available on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In early January, I pointed out that Debian is a member project of Software
in the Public Interest, Inc, and that all Debian developers have the right to
be contributing members of SPI.
SPI is now electing new members for the Board of Directors.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This message failed to be delivered to debian-devel-announce initially,
trying again since all Debian Developers should know about this...
Moshe Zadka [EMAIL PROTECTED] writes:
Dear Debian Project Leader,
As one of the candidates in the DPL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
Last October, I announced a group subscription to lwn.net for Debian
developers, sponsored by HP. I've recently received numerous queries
about whether this deal was still available, and/or whether HP intended
to continue sponsoring the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have agreed to moderate an online debate among the candidates for SPI's
board of directors. Information about the election is available at:
http://www.spi-inc.org/news/2003/20031023
The debate will take place on Monday, 17 November 2003,
In article [EMAIL PROTECTED] you wrote:
It's too bad upstream developers are so diverse in their attitudes about how
to number things... such that we have to deal with stuff like this. However,
that's a fact of life.
: 2) Use the Epoch system for the purpose it was intended, and move libc6
:
In article [EMAIL PROTECTED] you wrote:
: I was looking at the list of release-critical bugs and noticed some bugs
: were closed. A lot of those closed bugs are for packages that are still
: sitting in Incoming. I would like to remind people that you have to wait
: with closing a bug until the
In article [EMAIL PROTECTED] you wrote:
: I see versions numbered 2.0.7 and 2.0.8 as release versions, because that
: is the way the upstream authors see them. The tarballs that appear before
: those releases are given numbers like 2.0.7pre1 specifically to indicate
: that they are NOT releases,
In article [EMAIL PROTECTED] you wrote:
: The latest version of the Debian web pages are complete.
I like them. Good work! A few nits.
The link on the developer's corner page that I think should go to the list
of developers instead brings up the xearth image. The visit the sponsor
image on
In article [EMAIL PROTECTED] you wrote:
: 21884 libc6-dev: relative links between top-level dirs
: The upstream maintainer (Ulrich D.) insists that the relative links are
: correct and that making /usr a symlink to something else is evil.
I'm not sure I completely understand what the links
In article [EMAIL PROTECTED] you wrote:
Hmmm. swinstall (HP-UX native I think) seems to support dependencies.
It's pretty ugly though and I don't know if there's a command line version.
Yes, you can drive swinstall from the command line. It's not pretty, but it
works.
Unfortunately, there's
In article [EMAIL PROTECTED] you wrote:
I suppose that we could go to a
release candidate model during the freeze, but that's something for another
discussion.
Of course, until we discuss this, we're doomed to perpetuation of the current,
incredibly broken freeze process. [shudder]
Not that
In article [EMAIL PROTECTED] you wrote:
Since the sources include an explicit copyright assertion but no explicit
distribution license
The upstream maintainers indicate in email that the GPL is their choice, which
is wonderful news. Now that this is resolved, I'll upload a package to main
In article [EMAIL PROTECTED] you wrote:
I'll be at Usenix again this year
As will I. Flying in Tues evening, back Fri evening. Will, as usual, have
some of my PGP fingerprint slips of paper with me in case I run into anyone.
Bdale
In article [EMAIL PROTECTED] you wrote:
I wonder if s/o is already working on this or if it doesn't make sense
to package it.
Given the BIND package will move to non-free in version 8.2 due to the license
on the RSA code used for DNSSEC, it's good to see an alternative that will be
in main...
In article [EMAIL PROTECTED] you wrote:
Given the BIND package will move to non-free in version 8.2 due to
the license on the RSA code used for DNSSEC, it's good to see an
alternative that will be in main... even if it's less functional.
Is it possible to keep an older version of Bind in
In article [EMAIL PROTECTED] you wrote:
I'm not the only one to be annoyed at the nag messages that are sent out.
Can the script please be disabled.
Absolutely. I've asked before for the nag widget to be turned off, and I
strongly support turning it off now.
Yes, I have a couple of packages
I would like to offer the following two packages for adoption or removal:
upsd- I don't use it, but others apparently do, and there are
no open bugs that I am aware of
jaztool - I don't use it, I'm not sure anyone does. Rumor has it that
a
I'm going to package the software used with the Planet Connect satellite
Usenet feed service. We've been using it for a while, but there was no
explicit copyright/license terms in the upstream sources. A new version is
in the process of being released, and the author has agreed to resolve this,
Hi John.
I just read your LWN backpage letter, http://lwn.net/1999/0916/backpage.phtml.
I'm the Debian BIND package maintainer. I am aware of no intention on the
part of Debian to undermine the goal of a public key infrastructure centered
on DNS. We simply cannot ship the RSA code in our
In article [EMAIL PROTECTED] you wrote:
Package: dump (main)
Maintainer: Bdale Garbee [EMAIL PROTECTED]
44061 dump: Appears to be unable to dump rev 1 ext2fses with sparse super
I'm not an expert on ext2 filesystem internals. If someone who is wants to
have a look at this and give me some
In article [EMAIL PROTECTED] you wrote:
Bugs are no longer deleted!!! We don't have a way for you to access them
directly but there's an official location in the database where they're
being archived. We're trying to decide how to serve them up... by
requesting a bug number, obviously, but
In article [EMAIL PROTECTED] you wrote:
What do other think, and have you seen seeing the same runaway bug severity
inflation I have?
Yes. Submitters seem to think that if they crank up the severity, the bug
will get more/quicker attention. At least in my case, that just isn't true.
I'm not
In article [EMAIL PROTECTED] you wrote:
tar -zxf control.tar.gz control ./control
You can also use
tar -zxf control.tar.gz *control
which does not produce an error, and extracts either one. This is the fix I
supplied for lintian when the tar upstream changed the way pathname
In article [EMAIL PROTECTED] you wrote:
Bug stamp-out list for Mar 10 03:04 (CST)
Package: dump (debian/main)
Maintainer: Bdale Garbee [EMAIL PROTECTED]
59935 dump: dump segfaults
A number of bugs have been fixed since the 0.4b12 snapshot that's in potato
now. I agree with the submitter
In article [EMAIL PROTECTED] you wrote:
Package: sawmill (debian/main).
Maintainer: Mikolaj J. Habryn [EMAIL PROTECTED]
59760 sawmill: Sawmill fails to load -- missing file
/usr/lib/rep/0.11/i686-pc-linux-gnu/timers.so
This is filed against version 0.25-1. The version in potato is
In article [EMAIL PROTECTED] you wrote:
Package: pilot-manager (debian/main).
Maintainer: Darren Stalder [EMAIL PROTECTED]
59202 pilot-manager: Method GetRecord missing in SyncPlan
The pilot-manager package is quite useful even if SyncPlan doesn't work, which
I can neither confirm nor deny.
In article [EMAIL PROTECTED] you wrote:
does anybody know, wether there are ideas or plans to make
an Debian GNU/Linux especially for embedded and/or realtime
systems, i.e. Embedian GNU/Linux?
The problem is that embedded covers such a huge range these days. I've
built several embedded
In article [EMAIL PROTECTED] you wrote:
After reading this nice diskussion with all it's aspects, I want to
complete the mess and suggest a distribution called
e.g. progressive beetween stable(frozen) and unstable.
I gather you haven't read the discussion of package pools in the archive?
In article [EMAIL PROTECTED] you wrote:
You know, the whole concept of 'a release' is orthogonal to the way I think
about Debian. We've been through that before, too, and I understand the
various reasons that it's important for us to make a release from time to
time... but I doubt any of my
In article [EMAIL PROTECTED] you wrote:
It might be he wants to talk about -changes ? There he's right (and I do
totally agree with him).
I'm not excited about a list per architecture, but I've often wondered if
only posting to the lists messages for uploads that include source might not
be
In article [EMAIL PROTECTED] you wrote:
Package: bind (debian/main)
Maintainer: Bdale Garbee [EMAIL PROTECTED]
59649 bind: Gives core dump
Closed by 8.2.2p5-9, now in potato.
Package: inn2 (debian/main)
Maintainer: Bdale Garbee [EMAIL PROTECTED]
61030 inn2: fresh potato install
In article [EMAIL PROTECTED] you wrote:
I'm having some trouble, actually with a Cisco 6509 switch, but getting
it to talk to 20 VALinux machines. My story:
Some folks at work saw similar weirdness with the negotiation on some HP
switch products, their solution was to configure the switch to
I have packaged 'pcrd', which is a utility for controlling an Icom PCR-1000
radio receiver. It is probably mostly of interest to amateur radio folk,
and so will go in the hamradio section.
The upstream site for this package is
http://www.mv.net/ipusers/cdwalker/pcrd.html
The PCR-1000
I've built a package of bidwatcher, which is a tool for users of eBay, that
assists in placing and monitoring bids. I don't really want to maintain the
package, though, so I'm calling for a volunteer to package this for real and
upload it. I'm happy to provide what I've done so far, but it's
In article [EMAIL PROTECTED] you wrote:
Bug stamp-out list for Mar 31 03:06 (CST)
Package: bind (debian/main)
Maintainer: Bdale Garbee [EMAIL PROTECTED]
61129 base: bind upgrade leaves two named's running
I see how this can happen in some odd cases. Should have a fix uploaded in
a day
[EMAIL PROTECTED] (Nicholas Lee) writes:
Are there any thoughts to a chroot install option for bind?? Its not
that hard to setup, but I wonder how it would fit into the debian
policy.
I've been thinking about it after 9.1.0 releases, and after I add debconf
support. I don't run chroot'ed,
[EMAIL PROTECTED] (Adam Heath) writes:
Bdale hates dbs, doesn't know what it is
I don't hate dbs. I just get annoyed when packages with complicated build-time
patching schemes won't build. My sense is that each of these schemes increases
the probability of build-time failures by deferring
It was just pointed out to me that there is a new RFP for bind9 packages
filed to the wnpp part of the BTS.
As the BIND package maintainer, I indicated many months ago my intention to
package BIND 9.X for Debian.
Unfortunately, the BIND 9.0.0 and 9.0.1 releases contained sources for
required
[EMAIL PROTECTED] (Brian May) writes:
Does bind come with multiple libraries?
Yes. Four, I think.
Ok, I haven't looked at our policies for shared libs for a while, and I
obviously have some reading to do. Thanks for the warnings.
Bdale
[EMAIL PROTECTED] (Wichert Akkerman) writes:
gzip --rsyncable, aloready implemented, ask Rusty Russell.
I have a copy of Rusty's patch, but have not applied it since I don't like
diverging Debian packages from upstream this way. Wichert, have you or Rusty
or anyone taken this up with the gzip
[EMAIL PROTECTED] (Matt Zimmerman) writes:
As you know, it's been eons since the last upstream gzip release.
On advice of the current FSF upstream, we moved to 1.3 in November 2000.
I think it is entirely reasonable to talk to upstream about this before
contemplating forking.
Bdale
PROTECTED], [EMAIL PROTECTED]
Subject: Re: can we get rid of -I entirely, please?
From: Bdale Garbee [EMAIL PROTECTED]
Date: Mon, 08 Jan 2001 09:18:51 -0700
After lots of discussion on the Debian developer mailing lists, the
solution that I think makes the most sense is:
the -I
[EMAIL PROTECTED] (Roland Bauerschmidt) writes:
Speaking of IA-64: Do we have a machine yet? AFAIK not.
Several Debian folk have acces of one kind or another to IA-64 hardware. I
am not aware of any IA-64 systems fully dedicated to Debian development.
I am in possession of an IA-64 box from
[EMAIL PROTECTED] (Herbert Xu) writes:
kernel where all options were compiled into separate modules so simply
choosing the right modules constructs the optimal kernel.
Guess what, that's how the current 2.4 kernel images are constructed.
Well, not really. All of the drivers and other
[EMAIL PROTECTED] (Bas Zoetekouw) writes:
If a package requires any binary package in order to be build from
source, it must declare a dependency on that package.
It isn't *quite* that simple. Explicit build dependencies should only be
for packages that are neither essential nor
[EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
Bdale Garbee [EMAIL PROTECTED] writes:
It isn't *quite* that simple. Explicit build dependencies should only be
for packages that are neither essential nor build-essential.
But it's entirely harmless to mention them; this is an area
[EMAIL PROTECTED] (Rahul Jain) writes:
maybe there should be meta-packages for packages that have embedded version
numbers like that.
In the general case, yes. In this case, there is no need for one, since the
package in question is build-essential, and so need not be listed in a build
[EMAIL PROTECTED] (Martin Schulze) writes:
12. http://testdrive.hp.com/
Yes, this can be a good resource. I also invite anyone working on ia64
porting issues to the #debian-ia64 channel on irc.debian.org. There is very
little activity visible there, but people who can help are often
I am unable to spend as much time updating the 'ntp' packages as they deserve,
and so I would like to find someone suitable to either join me in working on
them, or take them over outright.
There are a number of open bugs that need to be addressed, and I'm completely
unhappy with the current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vince Mulhollon [EMAIL PROTECTED] writes:
I can't participate in the debate at that time and date. Will a log of
the debate be available via http and if so, where?
Yes, I'm sure a log of the debate will be made available online after the
event.
The new tar behavior with respect to wildcards is not a change I
introduced just for Debian, it's a new upstream change that appears to
be quite intentional and well documented, as per this text from the tar
info docs:
The following table summarizes pattern-matching default values:
Members
On Tue, 2006-06-27 at 13:09 +0200, Jeroen van Wolffelaar wrote:
But on the other hand, according to the 'be strict in what you send,
liberal in what you accept' mantra, it makes sense for tar to not create
tarfiles which in the past have caused issues for certain programs while
there's a
On Wed, 2006-06-28 at 10:36 +0200, Bill Allombert wrote:
Here, the only way seems to be putting an entry in NEWS.Debian (for
users script, ie things not under our control).
Good idea, Christian.
In addition, I would suggest we reinstate the previous behaviour, but
display a warning when
[EMAIL PROTECTED] (Barak A. Pearlmutter) writes:
As a compromise that addresses some of the issues I would suggest the
following: go with upstream, but add some convenience code, to whit:
(1) Hot-wire tar to check an environment variable TAR_WILDCARD_DEFAULT
and activate the --wildcard
In article [EMAIL PROTECTED] you wrote:
: ... and the expected destination of those files.
That raises an interesting question for me, my apologies if it's docuemented
somewhere that I haven't found yet.
What's the protocol for picking a directory to dump a new package in?
It was pretty easy
Package: tar
Version: 1.11.8
When attemping to do remote tar operations using the archive name systax
specified in the info file, which is [EMAIL PROTECTED]:file, if user is not
specified, tar core dumps, when it should use the current username as the
default.
This is probably part of the same
Package: trn
Version: 3.6-2
It's not clear to me why trn uses 'recommends' for a mail transport
and a news article injector, while tin uses 'depends'. I think that depends
makes more sense, so I'm filing this against trn.
Bdale
In article [EMAIL PROTECTED] you wrote:
: * delete mail spool file (what if it's nonempty?)
Tell the person running the script it's non-empty, and ask if they want it
deleted, anyway.
: * delete home directory. What do we do about saving
: files?
Package: mh
Version: 6.8.3-2
The 0.93R6 MH mail user interface package causes it to be impossible to
read any mail, since the default moreproc is '/usr/bin/more', and the current
Debian release appears to put more in '/bin/more' instead. You end up with
errors like:
[EMAIL PROTECTED]:~:
This is sort of long. Don't bother unless you care about what /usr's contents
look like, and/or you're desperate for reading material...
I've alluded in the past to my intention to package for Debian the cross
development tools we're using for AMD 29200 embedded systems development. I
care
In article [EMAIL PROTECTED] you wrote:
: We should document what we ship as we ship it.
: No argument, but that implies lots of work for maintainers
: when initially building packages and when upgrading to new
: upstream releases. I'm not sure that it's practical.
I think it's necessary. If
In article [EMAIL PROTECTED] you wrote:
: Kenny Wickstrom writes:
: My X server is
: on my Win 95 machine. So to get xtet42 to install I needed to add the
: --force-depends to the dpkg command line.
: xtet42 depends on X11R6 and recommends xserver. This is what Ian Murdoch
: said all X
I accidentally sent this to just Ian the first time, here it is again...
In article [EMAIL PROTECTED] you wrote:
: Martin Schulze writes (One question upon INN (and syslogd)):
: These logfiles are not turned with savelog by cron.sysklogd. Are they
: turned by cron.inn? If not I might have to
In article [EMAIL PROTECTED] you wrote:
: Something ought to be done though, since more(1) can't be made to go
: backwards through manpages. This is rather a serious deficiency.
: HP-UX's more(1) doesn't allow you to go back at all. Ever. :)
Until HP-UX 10.X, at which point it has very less-ish
In article [EMAIL PROTECTED] you wrote:
: I think we should arrive at a happy medium - uploads
: are verified against their .changes file and moved into an accessable
: area that is not their final resting place. Ian can then move them, with
: the confidence that their integrity has been checked,
In article [EMAIL PROTECTED] you wrote:
: Here are new versions of libgdbm, libdb and libreadline.
I can't find these anywhere, and it's been a couple of days since the
announcement? I really, really, want to install libreadline-2.0-9 ASAP.
Bdale
Package: metamail
Version: 2.7-1
The script /usr/bin/showpicture provided with the metamail package, which is
used by Netscape, et al, to launch xv or xloadimage to display graphical
objects, is a csh script. There is no dependency specified by the metamail
package, and csh is not part of the
Package: source
Version: 1.3.43
The file drivers/scsi/hosts.c defines the sequence in which different SCSI
controller cards are identified. The AHA152X driver appears early in the list,
which is unreasonable if there is another, smarter, SCSI controller in the
system... since it will result in
Package: source
Version: 1.3.43
The SCSI device driver for the AHA1740 only supports one card in a system at
one time. This is annoying.
Bdale
Package: base
Version: 0.93.6-13
It is utterly unreasonable for the system to try and do fsck's when the
system is booted with 'linux single'. The whole point of a single user boot
is that something is wrong that needs reasoned attention from a system
adminitrator. A single-user boot should do
This release fixes the problem with specifying a null username when a remote
tape is specified to the 'f' argument. Previously, unless the fully qualified
form of
[EMAIL PROTECTED]:/dev/tapename
was used, a segmentation violation and core dump would result before anything
else happened.
In article [EMAIL PROTECTED] you wrote:
: It doesn't really matter if a 152X gets detected before a high-power
: whiz-bang SCSI-matic 2010 PCI adapter, because you can still put root
: on any SCSI controller you like.
You are correct, of course, Jeff, but the problem with having a card like
a
Hmmm. This is somewhat more complex than it looks like. I cannot just
remove /usr/bin/zcat because it is intimately linked with compress.
I disagree. The job of a package maintainer includes the process of doing
things like this to a package. I have to do the same thing for the tar
package,
In article [EMAIL PROTECTED] you wrote:
: When mainstream is updated, hello-1.3 - hello-1.4
: Non-usual-maintainer updates, hello-1.3-8 - hello-1.4-0.1
: Usual-maintainer updates, hello-1.3-8 - hello-1.4-1
:
: Usual-maintainer should never use -0 for revisions.
:
: I think this seems
Package: ftp.debian.org
It appears to me that some files are incorrectly placed directly in the
buzz-fixed tree, instead of being in buzz-updates with appropriate
symlinks in buzz-fixed... all on master.debian.org.
The files in question:
buzz-fixed/source/manpages-de_0.1-4.tar.gz
In article [EMAIL PROTECTED] you wrote:
:
: The only incompatibility is that you might have to add a :bk: entry to
: the printcap in order to print to a BSD-lpd-based network printer.
I care a lot about compatibility with other BSD'ish lpd-based systems. I
could live with this easily.
Bdale
In article [EMAIL PROTECTED] you wrote:
: I don't know of a longterm solution short of
: duplicating the contrib and non-free trees into stable and unstable
: versions.
During the time when I was master of master, I was working on a proposal for
restructuring the hierarchy... and this is the same
Package: gzip
Version: 1.2.4-11
Execute these commands on the gzip file attached:
gzip -cd a.gz
gunzip a.gz; cat a
The output of the former is clearly incorrect.
I can't seem to duplicate your problem.
Note that
if the output is redirected or piped then the errors
What happens is that the first page is displayed over and over again.
The effect should be obvious if you are able to reproduce it.
Aha. Nothing like that here.
Some more info about my system:
kernel: 2.0.13
libc5: 5.2.18-10
I've tried this on a 1.2.8 machine with the same gzip and it
Package: lyx
Version: 0.10.3-1
This package installs /usr/X11R6/lib/X11/lyx/ and all child directories with
permissions 750, which prevents lyx from being able to read its own config
files at startup.
My quick hack fix was to run
find /usr/X11R6/lib/X11/lyx -type d -exec chmod 755 {} \;
In article [EMAIL PROTECTED] you wrote:
: BTW: Do you know anybody who really needs to put all the tools needed
: to build source packages onto floppies? :-)
Yes, I do. A friend has an older laptop that has a floppy drive, and that's
his only current path of getting bits in and out. He may
Fellow Debian folk.
Those of us who run autobuilders have started seeing more cases of a new
class of problem showing up in our buildd email that we'd like your help
resolving.
It is possible in the Build-Depends specification of a package to give
alternatives using syntax like:
[EMAIL PROTECTED] (Martin F Krafft) writes:
i don't think a global solution is a good choice here. if i install
bind9-chroot (hypothetically speaking), then bind9 should not possibly
ever run non-chrooted again. this should be done via diversions.
Eee. Diversions are so, well, messy. I
[EMAIL PROTECTED] (Wichert Akkerman) writes:
Previously Steve Greenland wrote:
Stdout and stderr from the maintainer scripts. (This may be obvious, but
you didn't explicitly list it.)
No, they should use debconf.
Regardless of whether packages are using debconf, I have wondered for *years*
[EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
But I think the point here is that the presence of a jillion normal
bugs, unaddressed for years, constitutes a release-critical bug
While that's an interesting assertion, the real question is what it means to
address a bug. There are packages
[EMAIL PROTECTED] (Adam Olsen) writes:
http://lists.debian.org/debian-devel/2000/debian-devel-23/msg01353.html,
which says there's a lintian error/warning called
ancient-standard-version, which I believe can detect when a debian
package is far behind the upstream version.
Nope, it tells
[EMAIL PROTECTED] (Brian Wolfe) writes:
Actualy, I believe that the mkisofs maintainer should have seen that a
new option was created and notified the maintainers of anything that
depended on mkisofs ...
That's pushing it, I think. I've had several experiences as a maintainer
where
[EMAIL PROTECTED] (Lenart Janos) writes:
On Sat, Dec 29, 2001 at 03:30:28PM +0100, Bas Zoetekouw wrote:
You wrote:
As you might already have noticed Debian begun to bloat - so many
unneeded, unused, unmaintained(!) packages.
My opinion is that one DD alone couldn't upload NEW package,
[EMAIL PROTECTED] (dman) writes:
It does, depending on the environment. If many users of a system have
used normal vi for a long time, and you want to convince them to
install vim instead, it better behave the way they expect.
Why do people insist on installing 'vim' as 'vi'? It isn't vi,
[EMAIL PROTECTED] (Mikael Hedin) writes:
ogle doesn't build on ia64, and I don't understand what's causing it.
...
The configure script stops when testing xml2-config, but the correct
version is on the system.
This often indicates that the configure script is trying to run a small
test
[EMAIL PROTECTED] (Tille, Andreas) writes:
Could any kind soul please do the job or just poin to an ia64 box with
installed build dependencies?
Done.
Bdale
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[EMAIL PROTECTED] (Colin Watson) writes:
Generally speaking, Debian packages aren't relocatable anyway. Many of
them (unavoidably) end up with paths compiled into binaries.
We may have to deal with this for things like allowing ia32 binaries to run
on ia64 systems... though so far, all of the
[EMAIL PROTECTED] (Don Armstrong) writes:
If not, I'll just file a bug w/ patch.
That's the right thing to do for now, regardless.
Bdale
aj@azure.humbug.org.au (Anthony Towns) writes:
On Tue, Aug 27, 2002 at 01:40:09PM +0200, Michael Meskes wrote:
I was just told the script updating testing doesn't run at the moment.
Is that true? If so, is there a reason? Are we already in freeze? :-)
It's running, but it's not doing any
on my list right now.
Bdale Garbee [EMAIL PROTECTED]
amanda
dump
Change made to both packages in my CVS for the next upload.
Bdale
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
1 - 100 of 814 matches
Mail list logo
