On Sat, Aug 8, 2015 at 2:39 PM Dirk Eddelbuettel wrote:
> Abort. I just wasted a few hours on this (luckily while doing other
> stuff). I am not going to split libjags, libjags-dev off but simply rebuild
> depending on g++ (>= 4:5.2).
>
> Chris can then depend on this version, and that is all th
On Tue, Oct 28, 2014 at 6:25 PM, Axel Beckert wrote:
> Rob Browning wrote:
>> One answer would be to patch css-mode, another would be to just remove
>> css-mode (and html-helper-mode (last updated upstream in 2004) if it
>> doesn't work with Emacs' built-in css-mode).
>
> Just for the record: Remo
The attached version of debian/patches/home.diff fixes the segfaults
on amd64. As Aurelien suggests, someone probably should tackle the
real underlying issues with $HOME, but this at least fixes the
immediate issue.
Chris
--
Chris Lawrence - http://blog.lordsutch.com/
Index: tvtime-1.0.2/src
Package: libcairo2:amd64
Followup-For: Bug #658252
FYI, this appears to be an upstream bug (or bugs):
"Current git: Xorg display corruption with radeon driver (bisected)"
... which appears to actually be a bug in somewhere in X:
"Graphics corruption and performance problems using recent Cairo"
h
On Mon, May 31, 2010 at 10:47 PM, wrote:
> Regardless, this bug (#584026: printconf) is hardly "done".
Yes, it is, because it doesn't apply to printconf. foomatic-filters
is the only Foomatic-related package that is affected by calling gs
directly, and I assume your mass-filed bug reports have
OdyX - My apologies for not getting back to you sooner on this. Yes,
if you're interested in co-maintaining the package or even taking it
(and the related foomatic-* packages) over as maintainer, I'd be happy
to have the help as my interests have moved elsewhere (and my time
demands in other areas
Turns out that the only solution that seems to work with all cases
(including directories w/spaces) is to move the --chdir "$PWD" part
into each of the start-stop-daemon calls rather than embedding it in
$args. 3.2-22, uploading now, includes this fix.
Thanks to all those who took time to try to
severity 518362 important
thanks
Note that this bug does not affect all usage of the package, and thus
is not "grave."
You can turn debugging on in CUPS with:
LogLevel debug
in /etc/cups/cupsd.conf.
Please also see if foomatic-rip segfaulted by checking /var/log/syslog
or /var/log/kern.log.
I
On Sun, Mar 1, 2009 at 10:42 AM, Bdale Garbee wrote:
> I raised the severity on cups bug #511009 yesterday to release-critical,
> since the move from postscript to pdf as the default cups output format
> broke all of my printers.
>
> As Keith Packard noted in a follow-up to the bug, it appears tha
On Sun, Oct 5, 2008 at 12:51 PM, Luk Claes <[EMAIL PROTECTED]> wrote:
> Can you please exclude all the CVS files, so we can unblock a fixed
> version, TIA.
The CVS files aren't a regression from the previous release; they were
in 0.7.8 too, as far as I can remember.
(I mean, I'll gladly build a 0
On Wed, Aug 13, 2008 at 8:39 PM, Rob Browning <[EMAIL PROTECTED]> wrote:
> "Chris Lawrence" <[EMAIL PROTECTED]> writes:
>
>>> I suppose this should probably be serious, since it prevents
>>> /etc/init.d/at from stopping the server. I think it may al
On Tue, Aug 12, 2008 at 10:56 PM, Rob Browning <[EMAIL PROTECTED]> wrote:
>
> severity 494268 serious
> thanks
>
> I suppose this should probably be serious, since it prevents
> /etc/init.d/at from stopping the server. I think it may also kill an
> attempt to run "/etc/init.d/atd restart".
>
> I'm
Per my vac message if you guys can put together a quick release in the
next day or so that would be great. It will otherwise be Tuesday at
the earliest. Chris.
On 6/4/08, Thijs Kinkhorst <[EMAIL PROTECTED]> wrote:
> On Wed, June 4, 2008 14:27, Thomas Arendsen Hein wrote:
>> I encountered this bug
On 7/26/07, Josip Rodin <[EMAIL PROTECTED]> wrote:
On Thu, Jul 26, 2007 at 10:54:22AM -0500, Chris Lawrence wrote:
> Has this been tested with lsb-base 3.1-24 (which was already in
> incoming when this cloning was done)? If not, please test with that
> version.
I can't
Has this been tested with lsb-base 3.1-24 (which was already in
incoming when this cloning was done)? If not, please test with that
version.
On 7/26/07, Debian Bug Tracking System <[EMAIL PROTECTED]> wrote:
Processing commands for [EMAIL PROTECTED]:
> unblock 412980 by 410622
Bug#410622: lsb-b
On 7/10/07, Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
But look what the source has:
[EMAIL PROTECTED]:~$ grep Depends src/debian/CRAN/mvtnorm-0.7.5/debian/control
Build-Depends: debhelper (>> 4.1.0), r-base-dev (>= 2.3.1), cdbs
Depends: ${shlibs:Depends}, r-base-core (>= 2.3.1)
[EMAIL PROTEC
On 7/9/07, Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
a) How do I fix the dh_shlibs call to get proper Depends? I do not
know how :-/
I think dh_shlibs is getting the depends... the trouble is they're not
making it into the control file. In r-cran-mvtnorm's case, in
debian/contro
On 3/28/07, Carl Fürstenberg <[EMAIL PROTECTED]> wrote:
Package: reportbug
Version: 3.34
Severity: serious
Have to report this manually as reportbug doesn't work for me at the
moment. When trying to execute reportbug, I get this error:
[0:[EMAIL PROTECTED] ~]$ reportbug
Traceback (most recent c
On 10/27/06, Neil Williams <[EMAIL PROTECTED]> wrote:
This is the NMUdiff that I propose to upload to fix the RC bug due to
the automake transition.
I'm traveling this weekend without access to my build machine, so an
NMU ASAP would be much appreciated. Thanks for taking care of this.
Chris
On 9/10/06, Erich Schubert <[EMAIL PROTECTED]> wrote:
Hi Chris,
> And people wonder why individuals leave the project...
When a key utility such as "reportbug" is uploaded to unstable
*untested*, this is not very motivating for others, either!
I wanted to file a bug, and it was "Duh! The maintai
: 4B3A135C (o_
A man doesn't know what he knows until he knows what he doesn't know. //\
Nichts läßt die Erde so geräumig erscheinen, als wenn man V_/_
Freunde in der Ferne hat. --- Henry David Thoreau
--
Chris Lawrence - http://blog.lordsutch.com/
Package: r-doc-html
Version: 2.3.1-2
Followup-For: Bug #382696
Hey Dirk - this bug definitely hits on the upgrade from 2.3.1-1 to
2.3.1-2 (I found this out when finally upgrading my work box after the
big move from NC).
I can't even get the package to install with --force-all... my strong
suspici
rt before
the options, please reassign the bug; I haven't checked the LSB and this
package doesn't seem to bother to document start_daemon's syntax internally.
The LSB does require that all options be specified before the
executable name; I am revising README.Debian in lsb-bas
Is downgrading foomatic-db the only thing you needed to do to fix the
problem, or did you also downgrade foomatic-filters (which is the only
package with a binary in it)?
Chris
Did you also install the updated python2.3-gnome2 and
python2.3-gnome2-extras packages?
On 2/27/06, Ramakrishnan Muthukrishnan <[EMAIL PROTECTED]> wrote:
> || On Mon, 27 Feb 2006 14:37:33 -0500
> || "Chris Lawrence" <[EMAIL PROTECTED]> wrote:
>
> lawre
interfaces to BibTeX and
> th
> ii python-glade2 2.8.2-3GTK+ bindings: Glade support
> ii python-gnome2 2.10.0-4 Python bindings for the GNOME
> desk
> ii python2.3-glade2 2.8.2-3GTK+ bindings: Glade support
> ii python2.3-gnome2 2.10.0-4 Python bindings for the GNOME
> desk
>
> Versions of packages pybliographer recommends:
> ii yelp 2.10.0-3 Help browser for GNOME 2
>
> -- no debconf information
>
>
--
Chris Lawrence - http://blog.lordsutch.com/
eful on the m68k architecture (equivalent to lspci, etc.). If
someone wants to adopt it from me (I don't have an m68k box any more),
that's fine, but I don't think it should be removed.
Chris
--
Chris Lawrence - http://blog.lordsutch.com/
This looks like a bug in gcj on SPARC. None of the other buildds seem
to have tripped this problem; it may relate to the version drift in
libgcj6-dev on SPARC.
Chris
--
Chris Lawrence - http://blog.lordsutch.com/
box in my office tomorrow (which I can't ssh to from
home).
Chris
--
Chris Lawrence - http://blog.lordsutch.com/
On 7/13/05, Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
> On Wed, Jul 13, 2005 at 01:47:43PM -0500, Chris Lawrence wrote:
> > Package: r-cran-rgl
> > Version: 0.64.13-3
> > Severity: serious
> >
> > Subject says it all, really... the upload of X.org to sid
Package: r-cran-rgl
Version: 0.64.13-3
Severity: serious
Subject says it all, really... the upload of X.org to sid makes this
package not installable with the upgraded xutils and x-window-system-core.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (50
ends is necessary, since base-files is
Essential and depends on awk. (Why lintian doesn't catch that too is
beyond me.) As long as AWK=/usr/bin/awk according to R, we're good to
go.
Chris
--
Chris Lawrence - http://blog.lordsutch.com/
n we
can get on with our lives.
Chris
--
Chris Lawrence - http://blog.lordsutch.com/
se for this issue (which affects exactly zero people) is rich.
Dirk: attached is a 3-line patch to r-base that should fix the issue globally.
Chris
--
Chris Lawrence - http://blog.lordsutch.com/
diff
Description: Binary data
I'm still not convinced this is really RC, by the way... any
non-seriously-broken system should have mawk installed.
Chris
--
Chris Lawrence - http://blog.lordsutch.com/
se feel free to lower the severity of this bug.
I'd rather see it fixed for sarge ;-)
Chris
--
Chris Lawrence - http://blog.lordsutch.com/
d not found
> make[1]: *** [world2.line] Error 127
>
> You should add a build dependency on gawk.
Chris
--
Chris Lawrence - http://blog.lordsutch.com/
, 'testing')
> Architecture: i386 (i686)
> Kernel: Linux 2.4.27-1-586tsc
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
>
> Versions of packages reportbug depends on:
> ii python2.3 2.3.4-19 An interactive high-level
> object-o
>
> -- no debconf information
>
>
--
Chris Lawrence - http://blog.lordsutch.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
y *description* rather than by name.
The "don't offer RC severities in novice mode" approach has already
been tried and was apparently too confusing for our users' brains.
See e.g. 254327 and 255479.
Chris
--
Chris Lawrence - http://blog.lordsutch.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
failure)
has corrupted your /etc/python2.3/site.py file in some way. Please
try reinstalling python2.3 and seeing if this fixes the problem.
Chris
--
Chris Lawrence - http://blog.lordsutch.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
40 matches
Mail list logo
