respects than just hardware driver count, and we have to be realistic
that this means a period of heavy changes followed by a period to stabilize
everything again.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
, not audit
someone's code, it also looks immature to take potshots at someone who,
unlike the changelog author, was able to find such a security bug without
first having his attention drawn to the section of code in question. shrug
--
Steve Langasek
postmodern programmer
signature.asc
Description
to handwave
this away by saying that free firmware could exist. We either have free
firmware for use with the device, or we don't. If we don't, then the driver
won't work for our users without additional effort, and we should be honest
about that.
--
Steve Langasek
postmodern programmer
linking against libc6 is more likely to
introduce ABI problems via nss than just dynamically linking against an old
libc6 ABI (i.e., GLIBC_2.0 or GLIBC_2.1).
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
Hi Goto,
On Wed, Feb 02, 2005 at 01:54:54PM +0900, GOTO Masanori wrote:
At Thu, 27 Jan 2005 07:30:57 -0800,
Steve Langasek wrote:
On Thu, Jan 27, 2005 at 01:19:36PM +0100, Christoph Berg wrote:
I upgraded a Woody box last week to Sarge's glibc/apt/dpkg/
openoffice.org/perl last week
, which requires no
imprimatur from the DPL, before you start throwing packages that have never
even been tested by their maintainer at us faster than we already get them.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
packages are uploaded, or to cut down on the number of utterly broken
packages that are getting uploaded in the first place. I'm not suggesting
that ftpmasters are deliberately ignoring the NEW queue for sarge's sake,
but from here I'm not shedding any tears.
--
Steve Langasek
postmodern
maintainers to tag packages
as being testing-worthy would just make it harder to get needed package
fixes to get into testing.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
about it via
debian-devel-announce, y'know?
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
the importance of not turning
libmysqlclient into libC here.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
in Debian.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
On Sat, Feb 12, 2005 at 09:14:26AM +0100, Francesco Paolo Lovergine wrote:
On Fri, Feb 11, 2005 at 03:30:59PM -0800, Steve Langasek wrote:
On Fri, Feb 11, 2005 at 03:31:44PM +0100, Christian Hammers wrote:
On 2005-02-11 sean finney wrote:
On Fri, Feb 11, 2005 at 10:15:55AM +0100
404 Not Found
Failed to fetch http://xx.linux.org.xx/debian/pool/main/x
Fetched 26.6MB in 2m39s (167kB/s)
E: Some files failed to download
Error 100
Yeah, real helpful of you to blot out the only potentially useful bit of
information in your post...
--
Steve Langasek
postmodern
this problem.
Thanks,
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
the version of automake you're using.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
On Wed, Feb 16, 2005 at 01:02:58PM -0800, Thomas Bushnell BSG wrote:
Steve Langasek [EMAIL PROTECTED] writes:
Clearly not, or it wouldn't have failed to build on mips and mipsel. There
is nothing perfectly working about that version of libtool, and moreover,
its effects are not limited
are not as nice as they ought to be -- frequently
complicated by upstreams' use of questionable practices where autoconf
macros (aclocal.m4) are concerned. I still haven't gotten gnucash playing
nicely with libtool 1.5, FWIW, after several iterations...
--
Steve Langasek
postmodern programmer
then, but I would rather
avoid such a procedure if possible.
I think the path to getting 1.8.10 into sarge is fairly straightforward from
here.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
only of benefit to a single, little-used architecture
is negligible.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
:
debian-release on the message -- now, rather than waiting for the buildds to
be fixed. Hopefully, this would save the buildd maintainers the trouble of
having to look through all the build logs to find the ones related to this
breakage, and they can requeue them as a batch.
--
Steve Langasek
wrong here. (If I'm not absolutely
wrong this is not the first case for this package.)
Perhaps there was some spam filter in your pipeline that tried to do natural
language parsing of the text, and exploded the same way my brain did upon
reading that message?
--
Steve Langasek
postmodern
) that using -D_FILE_OFFSET_BITS=64 on natively 64-bit
systems such as alpha causes surprising breakage of some glibc APIs.
* Would the release managers approve this change for sarge?
If this is the only change, yes.
Cheers,
--
Steve Langasek
postmodern programmer
signature.asc
Description
; the package currently in
unstable cannot be built using sources in the archive (it depends on a
library that currently awaits ftp-master NEW processing), so should not have
been uploaded to main.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
On Sat, Feb 26, 2005 at 04:28:36PM +0100, Marc Haber wrote:
On Fri, 25 Feb 2005 17:16:57 -0800, Steve Langasek [EMAIL PROTECTED]
wrote:
That said, any package that is uninstallable in testing for such a long
period of time almost certainly has an RC bug that should be filed. In the
case
On Sat, Feb 26, 2005 at 12:59:49PM +0100, Santiago Vila wrote:
On Fri, 25 Feb 2005, Steve Langasek wrote:
The version in experimental has -D_FILE_OFFSET_BITS=64, and it works
on files larger than 2GB, but I have only tested it on the i386
architecture.
Please use the value
that this doesn't actually slow them at all.
Hmm, no; I've only said that dropping archs because of build problems
affecting individual, arbitrary packages is a stupid strategy for getting us
to release.
--
Steve Langasek
postmodern programmer
[1] With other minor factors that probably balance each other out
going to bring about the
desired outcome.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
On Thu, Feb 24, 2005 at 08:44:04PM -0800, Thomas Bushnell BSG wrote:
Steve Langasek [EMAIL PROTECTED] writes:
I don't think it would hurt if maintainers whose packages are in this state
would email the relevant arch@buildd.debian.org addresses and cc:
debian-release on the message -- now
(and there are a couple
of good reasons for this).
Good maintainers understand that QA is more than just getting the latest and
greatest version of the package into the archive...
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
having had its reiserfs resize support pulled
because it depended on the buggy progsreiserfs implementation, qtparted has
itself also been dropped from testing due to an unrelated RC bug.
Thanks,
--
Steve Langasek
postmodern programmer
Date: Mon, 28 Feb 2005 12:12:38 -0800
From: Clifford
at the
beginning of November). Not much of a reason to hurry, if you ask me...
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
list that have not been relinked against libmysqlclient12.
- On Saturday, Mar 12 I will begin NMUing any packages from that list which
have not been fixed.
Thanks,
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
much to ask that people who bitch about communication problems in Debian
make an effort first to pay attention to the communication that's going on?
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
i can send you a copy off-list.
Any reason not to post it on-list? I was hoping to improve the
security/usability of my own setup based on the best practices offered up in
reply to this thread.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
is in the
top five reasons I'm a Debian user.
Out of curiosity, how many of these architectures are you running stable on?
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
entries to these packages? Far better than removing a
bunch of modules from the kernel-image at this late stage, IMHO.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
On Thu, Mar 10, 2005 at 12:20:36AM +0100, Sven Luther wrote:
On Tue, Mar 08, 2005 at 03:11:02PM -0800, Steve Langasek wrote:
On Tue, Mar 08, 2005 at 04:54:34PM +0100, Sven Luther wrote:
Here is the relevant section of the .changes file for the package in
question:
Date: Wed, 12 Jan
On Thu, Mar 10, 2005 at 11:57:11AM +0100, Mike Hommey wrote:
On Wed, Mar 09, 2005 at 05:46:22PM -0800, Steve Langasek [EMAIL PROTECTED]
wrote:
Considering you're talking about solutions that require updates to
kernel-image packages *anyway*, why has no one suggested adding the
necessary
. Re-uploading doesn't change its position in the queue, but
it *does* force buildds for all the other archs to needlessly rebuild the
package. This is why the answer to your previous email was please be
patient.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
On Fri, Mar 11, 2005 at 05:03:55PM -0800, Thomas Bushnell BSG wrote:
Steve Langasek [EMAIL PROTECTED] writes:
Re-uploading a package to provoke a buildd response is counterproductive,
*particularly* when the package is already in Needs-Build on the missing
architectures. Re-uploading
On Sat, Mar 12, 2005 at 03:19:23PM +1100, Matthew Palmer wrote:
[Probably going a bit off track for -release; MFT to -devel]
On Fri, Mar 11, 2005 at 07:14:35PM -0800, Steve Langasek wrote:
The queue ordering is entirely automatic, and AIUI the queue(s) is (are)
sorted by:
- target suite
prevent it from time to time.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
On Sun, Mar 13, 2005 at 08:57:14PM -0800, Thomas Bushnell BSG wrote:
Steve Langasek [EMAIL PROTECTED] writes:
Some maintainers have already opted to move their GFDL documentation
to non-free for sarge, but the vast remainder will need to be dealt
with soon after sarge's release to keep us
On Sun, Mar 13, 2005 at 10:47:15PM -0800, Thomas Bushnell BSG wrote:
Steve Langasek [EMAIL PROTECTED] writes:
The sh and hurd-i386 ports don't currently meet the SCC requirements, as
neither has a running autobuilder or is keeping up with new packages.
It is impossible for any port under
Hi Andreas,
On Mon, Mar 14, 2005 at 07:37:51AM +0100, Andreas Tille wrote:
On Sun, 13 Mar 2005, Steve Langasek wrote:
IMHO all these facts with exception of those social facts I marked (?)
are fullfilled by Sparc.
For reference, the killer for most archs is the 98% built criterion;
from
on the side
of caution for long enough and will probably be more aggressive with
buildd-stalled RC fixes going forward.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
On Sun, Mar 13, 2005 at 11:36:39PM +0100, Wouter Verhelst wrote:
Op vr, 11-03-2005 te 19:14 -0800, schreef Steve Langasek:
The queue ordering is entirely automatic, and AIUI the queue(s) is (are)
sorted by:
- target suite
- previous compilation state (already built packages
On Sun, Mar 13, 2005 at 11:21:29PM -0800, Thomas Bushnell BSG wrote:
Steve Langasek [EMAIL PROTECTED] writes:
On Sun, Mar 13, 2005 at 10:47:15PM -0800, Thomas Bushnell BSG wrote:
Steve Langasek [EMAIL PROTECTED] writes:
The sh and hurd-i386 ports don't currently meet the SCC
On Mon, Mar 14, 2005 at 09:09:09AM +0100, Adrian von Bidder wrote:
On Monday 14 March 2005 05.45, Steve Langasek wrote:
Architectures that are no longer being considered for stable releases
are not going to be left out in the cold. The SCC infrastructure is
intended as a long-term option
On Mon, Mar 14, 2005 at 09:31:44AM +0100, Romain Francoise wrote:
Steve Langasek [EMAIL PROTECTED] writes:
The following people in Debian leadership roles have also expressed
their support:
Andreas Schuldei (DPL candidate)
Angus Lees (DPL candidate)
Branden Robinson (DPL
you?
I'm all about portability, but I also believe it's important in terms of
our release cycle length for the release team to be in a position to set
release standards for architectures, much stricter than the ones we have
in place now. This proposal represents our first stab at this.
--
Steve
for
multiarch in glibc/dpkg/toolchain seems sound, but actually using it in
Debian packages for etch seems to hinge on the other concerns above.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
the current upstream KDE
packages for a whole seven days, THAT is a noteworthy improvement all
its own.
--
Steve Langasek
postmodern programmer
pgpngD3xvmkzg.pgp
Description: PGP signature
On Wed, Aug 20, 2003 at 04:48:15PM +1000, Anand Kumria wrote:
Hi Steve,
On Wed, Jul 30, 2003 at 08:02:44AM -0500, Steve Langasek wrote:
On Wed, Jul 30, 2003 at 05:40:26PM +1000, Anand Kumria wrote:
If you, or anyone else, is interested shipping those overseas could be
arranged
serve the same purpose?
--
Steve Langasek
postmodern programmer
pgpO7yAYpLReB.pgp
Description: PGP signature
the
package upload queue and d-d-a. Whether you agree with this design or
not, it means that the Debian keyserver is not suitable for use as a
general-purpose means of *authenticating* people. For authenticating
PGP users to one another, you should use the usual Web of Trust to
achieve this.
--
Steve
,
--
Steve Langasek
postmodern programmer
pgpy7v2KoqL8F.pgp
Description: PGP signature
; there is simply some testing we can't do before packages
have been allowed to hit the archive, and the window between getting the
current KDE packages into testing (just in case), and getting KDE 3.2
pre packages into experimental/unstable, doesn't leave any margin for
error before the release.
--
Steve
On Wed, Aug 20, 2003 at 07:13:38PM +0200, Santiago Vila wrote:
On Wed, 20 Aug 2003, Steve Langasek wrote:
On Wed, Aug 20, 2003 at 03:52:42PM +0200, Santiago Vila wrote:
Will we some day consider seriously the idea of autobuilders compiling
against testing those packages which do not need
On Thu, Aug 21, 2003 at 10:42:28AM +0200, Sam Hocevar wrote:
On Wed, Aug 20, 2003, Steve Langasek wrote:
But descriptions can be deceiving. Does anyone use this package who
could comment on its reliability? Does the lack of other bugs indicate
that the software is mature and stable
On Thu, Aug 21, 2003 at 12:40:35PM -0400, Joey Hess wrote:
Steve Langasek wrote:
- It will now be possible to choose md5 vs. crypt passwords at install
time without violating policy. (Currently, a number of conffiles are
being modified by maintainer scripts in order to enable md5
Hi Marcelo,
On Thu, Aug 21, 2003 at 10:44:04AM +0200, Marcelo E. Magallon wrote:
On Wed, Aug 20, 2003 at 10:37:59PM -0500, Steve Langasek wrote:
- Per-package /etc/pam.d/ configuration files should not include
explicit 'password' blocks. Instead, services should use the builtin
On Thu, Aug 21, 2003 at 08:11:21PM -0400, Joey Hess wrote:
Steve Langasek wrote:
Given that all the files involved were conffiles prior to this
transition, I think no additional work is needed to correctly support
systems that are being upgraded. Can you confirm whether
/etc/pam.d/other
that such NMUs are a safer bet than many
NMUs for severity: important bugs that require code changes.
--
Steve Langasek
postmodern programmer
pgpaehTTZ2i9g.pgp
Description: PGP signature
.)
--
Steve Langasek
postmodern programmer
pgpFJmPZUWmFI.pgp
Description: PGP signature
to say an NMUer is responsible for all open bugs on the
package unless the maintainer uploads.
--
Steve Langasek
postmodern programmer
pgpUOJbPjciwI.pgp
Description: PGP signature
directory on my system; I
think this was an upstream default. Since all of the files under there
are merely data to the host system, /usr/share/ltsp/i386-linux is
probably fine.
--
Steve Langasek
postmodern programmer
pgpUUoRl3GPCd.pgp
Description: PGP signature
to include the preformatted dictionaries in
the source package so long as the true source form of the dictionaries
is also included.
--
Steve Langasek
postmodern programmer
pgpIWtoIYFBS2.pgp
Description: PGP signature
=$LOCALE_NAME.$LOCALE_CHARSET date
This should work just fine as any user.
Looks like this needs to be localedef -i $LOCALE_NAME -f $LOCALE_CHARSET
instead, but otherwise, I've confirmed that this works.
Cheers,
--
Steve Langasek
postmodern programmer
pgpKczzpbaxgJ.pgp
Description: PGP signature
is running UTF8. :)
--
Steve Langasek
postmodern programmer
pgpj8nQpkTi3D.pgp
Description: PGP signature
.$LOCALE_CHARSET
# Using the locale
LOCPATH=$LOCALE_PATH LC_ALL=$LOCALE_NAME.$LOCALE_CHARSET date
Steve Langasek [EMAIL PROTECTED] added:
Looks like this needs to be localedef -i $LOCALE_NAME -f $LOCALE_CHARSET
instead, but otherwise, I've confirmed that this works.
I need
if you really feel strongly
about it, I would just encourage you to reconsider in this particular
instance.
--
Steve Langasek
postmodern programmer
pgpYgNis4P2wR.pgp
Description: PGP signature
loss.
--
Steve Langasek
postmodern programmer
pgpJmDIezlgIQ.pgp
Description: PGP signature
of their uploads: yes.
Holding NMUers accountable for the quality of the maintainer's package: no.
--
Steve Langasek
postmodern programmer
pgpnDmZZA1Ro7.pgp
Description: PGP signature
On Wed, Aug 27, 2003 at 02:57:28PM -0400, Stephen Frost wrote:
* Steve Langasek ([EMAIL PROTECTED]) wrote:
Holding NMUers accountable for the quality of their uploads: yes.
Holding NMUers accountable for the quality of the maintainer's package: no.
I'm happy to clarify my position if you
On Wed, Aug 27, 2003 at 02:05:15PM -0500, Manoj Srivastava wrote:
On Wed, 27 Aug 2003 11:46:41 -0500, Steve Langasek [EMAIL PROTECTED] said:
This is the sticking point, I think. Are we talking about resolving
the possible problems *from* NMUing, or are we talking about
resolving any
options that are potentially useful to other
packages, including ntp timeserver information; it might be nice to
gather a list of them all at once for submission to the dhcp3
maintainers, so they're not constantly recompiling to special-case each
attribute.
--
Steve Langasek
postmodern programmer
On Sat, Aug 30, 2003 at 11:18:25PM +, Brian May wrote:
On Sat, Aug 30, 2003 at 09:56:38AM -0500, Steve Langasek wrote:
On the client side, however, at least dhcp3-client requires recompiling
for each option you want to export to the client hook scripts. This was
You do? I was kindof
adapted to
support hooks to external program checks, if it really doesn't support
them already. You can do just about any other kind of check you want to
at any point in the receiving process, external program checks shouldn't
be all that hard to add.
--
Steve Langasek
postmodern programmer
on 64-bit architectures.
;)
--
Steve Langasek
postmodern programmer
pgphhS2my5DS9.pgp
Description: PGP signature
is non-free.
--
Steve Langasek
postmodern programmer
pgpM2AKNJ3kOJ.pgp
Description: PGP signature
that will be created automatically from
programs that are part of a package, it should be reserved for files created
by the administrator.
/var/opt sounds reasonable.
The /var/opt directory corresponds to /opt, and is not available for
Debian package use.
--
Steve Langasek
postmodern programmer
On Wed, Sep 03, 2003 at 03:20:49PM +1000, Russell Coker wrote:
On Wed, 3 Sep 2003 12:00, Steve Langasek wrote:
On Wed, Sep 03, 2003 at 11:31:28AM +1000, Russell Coker wrote:
On Wed, 3 Sep 2003 11:25, Pierre THIERRY wrote:
If not where should it be?
What about /usr/local/package
,
automatic upgrade path for users. However, I would feel better about
recommending this in horde's case if imp3 didn't currently have an RC
bug against it.
--
Steve Langasek
postmodern programmer
pgphEpm0kuhKx.pgp
Description: PGP signature
.
In general, no. If the contents of $var are a test operator, you'll get
a syntax error.
--
Steve Langasek
postmodern programmer
pgpoZEuNlPTZe.pgp
Description: PGP signature
a formality. ISTR that Roman is not
actively involved in m68k development anymore, so it wouldn't surprise
me that he's not taking an interest in this package.
--
Steve Langasek
postmodern programmer
pgpfmNHydF7OV.pgp
Description: PGP signature
without official sanction, then neither can bugs such as this be
considered closed without a similar official statement.
--
Steve Langasek
postmodern programmer
pgpvEqSdUem1l.pgp
Description: PGP signature
to be inconsequent. Why not have
the line say:
2. It must be compiled and up to date on all architectures it has
previously been compiled for in testing; ?
Because the principle is if it built on the architecture at once, we
expect it to be buildable again unless given a good reason.
--
Steve Langasek
On Sat, Sep 27, 2003 at 08:56:54PM +0200, Matthias Urlichs wrote:
Hi, Steve Langasek wrote:
What you are overlooking is that the main bug causing build failures for
gnucash is NOT architecture specific; rather, the potential for a build
failure appears to exist on all architectures
is
uploaded.
FWIW, last time I tried I found that it was rather difficult to run
debootstrap from within a package postinst script... at least with
debconf using an interactive frontend. :)
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
be overcome by someone with a vested interest in the
MILO-dependent subarchs.
Cheers,
--
Steve Langasek
postmodern programmer
pgpLBbzW9AowG.pgp
Description: PGP signature
+aboot is the way to go.
--
Steve Langasek
postmodern programmer
pgpVclM7QU2uv.pgp
Description: PGP signature
?
Looking at the graphs, I know I'm not the only one who took advantage of
it.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
of this
information as possible available to developers, so they can dig into
some of the larger package knots according to their interests rather
than it being exclusively the domain of the RM assistants.
--
Steve Langasek
postmodern programmer
pgpdw6xHmRZJ1.pgp
Description: PGP signature
from testing (and not making
it back in) between now and release, but such decisions are made rather
dispassionately by the release team -- if someone cares enough to fix
it, it stays in; if no one cares enough to fix it, it doesn't.
--
Steve Langasek
postmodern programmer
pgpk77tOpzAHQ.pgp
On Thu, Oct 02, 2003 at 08:36:50AM -0400, Stephen Frost wrote:
* Steve Langasek ([EMAIL PROTECTED]) wrote:
It's been noted several times that the end of the 0-day NMU period was
accompanied by a marked reversal in the RC bug graph. I think it's time
for a group debriefing
On Thu, Oct 02, 2003 at 10:43:24PM +0200, Björn Stenberg wrote:
Steve Langasek wrote:
What's hard to see at a glance is how large collections of packages are
interrelated in their dependencies. Many packages that you *don't* use
may be having a direct effect on the packages you *do* use
of the recent aptitude bug, this makes all the
difference between pulling in non-free packages by default, and
informing the user by default that a non-free package is available which
complements the chosen package.
--
Steve Langasek
postmodern programmer
pgpVqMkPvv3uV.pgp
Description: PGP
On Fri, Oct 03, 2003 at 05:52:36PM +0200, Rene Engelhard wrote:
Steve Langasek wrote:
With the exception of the recent aptitude bug, this makes all the
difference between pulling in non-free packages by default, and
informing the user by default that a non-free package is available which
401 - 500 of 3869 matches
Mail list logo
