I have the same problem (though note that the configure script does in
fact exit without an error despite printing the error to the console.
I have to use dpkg-reconfigure to reproduce the error. I assume my
system isn't bootable but I'm not eager to test this):
root@tweedle:~# dpkg-reconfigure in
I don't think this is the right way to go about changing interfaces between
packages in Debian.
The correct way to go about this is to propose a new packaging policy that
packages use the sysfs interface. When that's approved then issue bug
reports against all packages using the old interface. Then
Has the debian zephyr package been krb5ed? Or will that package be
desupported as well?
--
Greg
On 17 Mar 2009, at 02:39, Sam Hartman wrote:
Source: krb5
Source-version: 1.6.dfsg.4~beta1-4
So, the Kerberos libraries in unstable do not support Kerberos 4.
This is known and documented in th
> From: "Eugene V. Lyubimkin"
> To: 24717-d...@bugs.debian.org
> Date: Mon, 22 Dec 2008 21:06:20 +0200
> Subject: closing #24717
> Very old bug, we have nothing to do with it. Closing. Reopen if you object.
I'm sorry, I can't make heads or tails of this message.
"We have nothing to do with it" n
Karl Ramm <[EMAIL PROTECTED]> writes:
> I realize it's been a while, but can you describe the behavior that this
> fixes?
Oh my it has!
I don't remember at all, but skimming the code again it looks like
info->alignment=' ' indicates a newline. So the code sometimes accumulates two
lines' worth
> I can't quite figure when you would have info->ignore and info->alignment=' '
> but it must have been happening. As a result zephyrs were often formatted far
> too wide.
Hm, I wonder if tty_filter.c:360 was there at the time though.
--
greg
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
Brice Goglin <[EMAIL PROTECTED]> writes:
> Hi,
>
> A long time agoo, you reported a bug to the Debian BTS regarding the
> pointer hotspot being desynced with viewport on a MGA G400 board. Did
> you reproduce this problem recently? With Xorg/Etch? If not, I will
> close this bug in the next weeks.
Brice Goglin <[EMAIL PROTECTED]> writes:
> Hi Gregory,
>
> About 3 years ago, you reported a bug to the Debian BTS regarding some
> fonts not showing up.
> Did you reproduce this problem recently? If not, I will close this bug
> in the next weeks.
I tracked the problem down to some invalid font
Nathanael Nerode <[EMAIL PROTECTED]> writes:
> The X server has changed radically in recent years.
>
> Is this bug still present in the X server in a current version of Debian
> (sarge, etch, or sid)? Please reply to the bug trail. (If you don't reply,
> we will eventually assume that the bug i
Ari Pollak <[EMAIL PROTECTED]> writes:
> "ICQ privacy in Gaim is currently presence only. Message blocking uses
> another list on the server. Gaim's privacy API currently can't handle
> that. Fixing this is on the TODO list. However, most if not all of the
> spam will disappear if your account isn
[EMAIL PROTECTED] (Debian Bug Tracking System) writes:
> - Steal patch from Ubuntu/upstream to disable the webaware feature to
>drastically reduce AIM & ICQ spam (Closes: #360063, 369234)
Does this actually make it refuse messages from non-buddies fixing the problem
that privacy set
> On Tue, May 16, 2006 at 09:05:40AM +0200, Frank K??ster wrote:
>
> Something like, on first installation, or debconf question "Should
> xdvi/... respect /etc/papersize" with an appropriate file in
> /etc/libpaper.d in such a case:
>
> paper=`paperconf`
> case "$paper" in
> a4)
I would say to
Frank Küster <[EMAIL PROTECTED]> writes:
> Greg Stark <[EMAIL PROTECTED]> wrote:
>
> > Sure you can, in fact you already do have such a thing. It's not an error
> > not
> > to specify margin sizes in your document, there is a default specified in
>
Florent Rougon <[EMAIL PROTECTED]> writes:
> No, because in this case:
> - you cannot study how the document was done;
> - you cannot (conveniently) modify the document.
>
> Writing LaTeX code is comparable to programming, and what is good for
> usual software is also good for LaTeX code, mos
Frank Küster <[EMAIL PROTECTED]> writes:
> Greg Stark <[EMAIL PROTECTED]> wrote:
>
> > Generally what would happen on any reasonably configured system is they
> > would
> > go to Europe, for example, and rerun LaTeX on their document and print it on
> >
Florent Rougon <[EMAIL PROTECTED]> writes:
> Bullshit. They shot themselves in the foot and are "flummoxed" (guessing
> the meaning, sorry) whenever they work on a system that is configured in
> a different way than their home computer.
Only if it's configured differently than the paper available
Norbert Preining <[EMAIL PROTECTED]> writes:
> There is NO NO NO reasonable default. Get it. I create on a daily basis
> documents which are not A4, although my papersize is A4. B4, Crown,
> whatever you want. There is no default. There is no default. There is no
> default. Maybe for such simple
Florent Rougon <[EMAIL PROTECTED]> writes:
> Greg Stark <[EMAIL PROTECTED]> wrote:
>
> > You have to default to something, it may as well be something reasonable.
> > You
> > would prefer eliminating /etc/papersize and having every package have its
> >
Frank Küster <[EMAIL PROTECTED]> writes:
> Greg Stark <[EMAIL PROTECTED]> wrote:
>
> > would describe this, Debian users expect packages to user /etc/papersize and
> > work automatically and won't have read any install document before
> > installing
>
Ralf Stubner <[EMAIL PROTECTED]> writes:
> IMHO this is a question of general LaTeX usage and in no way Debian
> specific. In addition, the UK TUG FAQ (aka TeX FAQ) that Norbert
> mentioned is actually in tetex-doc:
It's Debian specific in that while users of a freshly installed source compile
m
Ralf Stubner <[EMAIL PROTECTED]> writes:
> On Fri, May 12, 2006 at 16:38 -0400, Gregory Stark wrote:
> >
> > It's actually worse than that.
> >
> > I have a LaTeX document that specifies
> >
> > \documentclass[letterpaper]{article}
> >
> > This works fine in LaTeX, it generates a correctly siz
Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
> > Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
> >
> > > Try -D_GNU_SOURCE then? Or -D_POSIX_C_SOURCE=200112L -D_BSD_SOURCE, or
> > > several other combinations.
>
> Yes, did you read my suggestion?
oh i see, i misread it.
> The man pages c
Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
> > This seems to be a problem related to the "features.h" stuff. If I define
> > _POSIX_C_SOURCE to 200112L then it works but then random other system
> > functions
> > aren't defined. (specifically "random" and "srandom").
>
> Try -D_GNU_SOURCE th
23 matches
Mail list logo
