Hi!
Package: pychecker
Version: 0.8.16-1
some cruft is left:
I'm not sure I understand what the problem is. Are these tests failing
for you, or something? They seem to all pass for me in a pbuilder
environment.
Sorry to be so dense, but I want to make sure I'm trying to fix the
right
On Thu, Dec 01, 2005 at 05:58:43PM +0100, Matthias Klose wrote:
Kenneth Pronovici writes:
Hi!
Package: pychecker
Version: 0.8.16-1
some cruft is left:
I'm not sure I understand what the problem is. Are these tests failing
for you, or something? They seem to all pass
It seems like the best solution is to just remove the .results files in
the clean rule. That way, even if there are leftover .results files
from failures that eventually get fixed, there's no chance that they
accidentally get placed into the source package. Does this sound like
it solves
Package: xmltv-util
Version: 0.5.39-2
As telepoche.fr has changed its data format, tv_grab_fr doesn't work
anymore and causes serious problems on my installation of freevo, for
example.
Hi,
I generally don't backport changes (even ones like this) from CVS into
Debian releases until it's
Package: python2.3-epydoc
Version: 2.1-8
Severity: normal
epydoc --html ignores the encoding of the Python source file (PEP 263)
and always put a:
?xml version=1.0 encoding=iso-8859-1?
which probably comes from my locale (it should come from the encoding
specified as '# -*- coding:
On Sat, Nov 05, 2005 at 04:22:29PM -0500, Roberto C. Sanchez wrote:
Package: pychecker
Version: 0.8.14-6
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The README.Debian file included with pychecker has lines that are longer
than 80 characters. This causes a rather
Package: cedar-backup2
Version: 2.7.1-1
Severity: serious
Justification: no longer builds from source
The following errors show when trying to build the package (on Sarge):
Well, that's pretty fscking odd. The package builds in a pbuilder
environment. Besides that, tests like these (which
Package: cedar-backup2
Version: 2.7.1-1
Severity: wishlist
I noticed the documentation is available both as PDF (compressed as .gz)
and html. Please do not package both in the same packages.
The various manual formats serve different purposes. While the HTML
manual is good for online
On Thu, Dec 22, 2005 at 07:25:11PM -0600, Kenneth Pronovici wrote:
Now that I think about it, I may have accidentally placed those tests
into the reduced feature set suite when I added them for 2.7.0. I'll
take a peek at it tonite and see if I can figure out what's going on.
Yeah
On Fri, Dec 23, 2005 at 12:00:12PM +0100, Jérôme Warnier wrote:
Le jeudi 22 décembre 2005 à 19:34 -0600, Kenneth Pronovici a écrit :
Package: cedar-backup2
Version: 2.7.1-1
Severity: wishlist
I noticed the documentation is available both as PDF (compressed as .gz)
and html
On Fri, Dec 23, 2005 at 11:43:04AM +0100, Jerome Warnier wrote:
Package: cedar-backup2
Version: 2.7.2-1
Severity: wishlist
Could you please already adapt the sample configuration file to Debian.
I think particularly to pathes to utilities like cdrecord, mkisofs, ...
Many Debian packages
Hi,
Were you planning on taking over the XMLTV packages, or not? I haven't
heard anything from you since your (possibly premature?) announcement to
the xmltv-devel mailing list on December 1 -- not even a reply to my
note asking for clarification of a few things like backports:
This is an upstream bug, but upstream seems to have disappeared for the
time being (I've heard from a collegue of his that he's both getting
married this year and working on a dissertation). I will do some
debugging on my own and see if I can fix the problem in a
Debian-specific release.
KEN
--
This bug might be related to the following python-list post:
From: Michele Petrazzo michele.petrazzo at TOGLIunipex.it
Subject: epydoc, variables and encoding
Newsgroups: gmane.comp.python.general
Date: 2005-09-21 10:48:06 GMT
I found a problem on epydoc. If I specify an encoding,
This bug might be related to the following python-list post:
I found a problem on epydoc. If I specify an encoding, epydoc not find
my global variables, and if I remove it, it work well.
Hmm, nope. I found a fix for the MY_VAR being skipped (and submitted a
patch to SourceForge), but
I've decided to orphan this package rather than listing it as RFA, and
I'll upload a new package with a Debian QA Group maintainer later today.
This package has no reverse dependencies any more, so unless someone
steps up to take this package, there's no particular need for it to stay
in Debian.
I've decided to orphan this package rather than listing it as RFA, and
I'll upload a new package with a Debian QA Group maintainer later today.
This package has no reverse dependencies any more, and AFAIK the only
package which build-depends on it is libhtml-tokeparser-simple-perl,
which I am
I've decided to orphan this package rather than listing it as RFA, and
I'll upload a new package with a Debian QA Group maintainer later today.
This package has no reverse dependencies any more, so unless someone
steps up to take this package, there's no particular need for it to stay
in Debian.
Package: uw-imapd
Version: 7:2002edebian1-11sarge1
Severity: minor
Tags: patch
Hi,
I recently configured UW IMAPD to use a real SSL certificate signed by
my own CA. However, I found the process a little confusing, mostly
because I wasn't sure how to create the new PEM file in
On 11/12/06, Florent Bayle [EMAIL PROTECTED] wrote:
package babygimp
tags 395917 + patch
thanks
Hi,
here is a patch to fix this bug.
Hi, Florent,
Thanks for the patch!
You definitely solved the problem with starting the script. I made a
few other changes, and was then able to successfully
On 10/28/06, Kenneth Pronovici [EMAIL PROTECTED] wrote:
On 10/28/06, Wolfgang Karall [EMAIL PROTECTED] wrote:
On Sat, 2006-10-28 at 13:21 -0500, Kenneth Pronovici wrote:
Odd, I filed the same bug just minutes before you did. I'll mark this
one as a duplicate.
Yeah, consecutive bug
Ok, so Chris Butler does not look like he's going to take the package
over. So, I'll upload the latest XMLTV release this afternoon or
tomorrow and that will fix this. Sorry it took so long -- I wasn't
expecting to have to be maintaining this package after Chris told me he
was taking it over.
Looks like this got fixed in the new 0.8.18 release:
/home/pronovic/tmp cat bug.py
try:
pass
except (KeyboardInterrupt, SystemExit):
pass
/home/pronovic/tmp pychecker bug.py
Processing module bug (bug.py)...
Warnings...
None
I'll upload later today.
KEN
Probably because those two are derived from BaseException, while
everything else is derived from Exception in Python 2.5. There
is a patch around, which I did not test:
https://thomas.apestaart.org/thomas/trac/changeset/938?format=diffnew=938
This patch does fix the bug for Python 2.5.
I think this is the same as upstream bug #2008061.
KEN
--
Kenneth J. Pronovici [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I have submitted this as SF bug #2018349.
KEN
--
Kenneth J. Pronovici [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I have submitted this as SF bug #2018350.
KEN
--
Kenneth J. Pronovici [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Interesting. It worked at my last upload.
The unit tests are still valid, and the only problem is the location
of the file the warning is coming from. I'll change the test
expectations and upload later this weekend.
KEN
On Jan 12, 2008 4:21 AM, Lucas Nussbaum [EMAIL PROTECTED] wrote:
Hi,
I'll take a look at this, but it's unlikely I'll find a solution very
soon. Upstream doesn't have a lot of time right now, and I'm not an
expert in the codebase (though sometimes I do get lucky).
I think that it's probably best for you to fix your FTBFS by removing
pychecker from
On Jan 14, 2008 10:36 AM, Guido Guenther [EMAIL PROTECTED] wrote:
Hi,
On Sat, Jan 12, 2008 at 10:34:44AM -0600, Kenneth Pronovici wrote:
I'll take a look at this, but it's unlikely I'll find a solution very
soon. Upstream doesn't have a lot of time right now, and I'm not an
expert
On Feb 2, 2008 2:01 PM, Christoph Burgmer [EMAIL PROTECTED] wrote:
Package: python-epydoc
Version: 3.0~beta1-5
Severity: normal
If a package is available globally to the system in addition to the version
in the local directory epydoc seems to prefer the global file over the local
in some
Christoph - I'll hopefully get 3.0 uploaded later today or tomorrow.
After it hits the archive, please re-test the stacktrace.txt scenario.
If the new version doesn't fix that problem, please file a separate
bug.
Edward - I'll leave this bug open while you're looking into
wrong-versions issue.
On Feb 3, 2008 5:46 PM, Marco Rodrigues [EMAIL PROTECTED] wrote:
Hi!
You should check this one.. Debian have done this request for this package,
and
so many others in Debian. You're right not to recommend a package that isn't
at
Debian, but with ... | firefox | ... it doesn't hurt.
On Feb 8, 2008 9:10 AM, Guido Guenther [EMAIL PROTECTED] wrote:
On Mon, Jan 14, 2008 at 10:39:27AM -0600, Kenneth Pronovici wrote:
Maybe we should clone 406357? You can fix your FTBFS by removing
pychecker from debian/rules, and I'll keep this bug against pychecker
open until we
On Nov 27, 2007 4:20 AM, Emilio Pozuelo Monfort [EMAIL PROTECTED] wrote:
We at the PythonApplicationsPackagingTeam are updating [1] the spe package,
but
it needs pychecker2, which is included in pychecker's tarball. Actually Spe
provides the module in its source tree, but we would like to get
On Nov 27, 2007 5:15 PM, Emilio Pozuelo Monfort [EMAIL PROTECTED] wrote:
[ CCing bug 453092, request for pychecker2 packaging ]
Kenneth Pronovici:
You've probably already checked before filing this bug report... but
has the Spe version of this code diverged at all from the Pychecker
On Dec 13, 2007 7:15 AM, Dan O'Huiginn [EMAIL PROTECTED] wrote:
The man page for pychecker omits many of the command-line switches
which are listed in 'pychecker --help'. It would be nice to:
a) update the man page to point users at --help for more complete
documentation
b) include more of
On Dec 20, 2007 7:51 PM, Dan O'Huiginn [EMAIL PROTECTED] wrote:
I am attaching a patch to update the man page.
Thanks! I am preparing an upload now. I always appreciate it when
users are willing to provide patches.
KEN
--
Kenneth J. Pronovici [EMAIL PROTECTED]
On Nov 6, 2007 4:12 AM, Michael Hanke [EMAIL PROTECTED] wrote:
Package: python-epydoc
Version: 3.0~beta1-4
Severity: normal
please add a package dependency recommendation to the 'python-docutils'
package. epydoc can understand restructured text as Python docstring
format, but the API docs
I heard back from Neal, and he doesn't mind me including pychecker2 in
the Debian package. So, I have made the changes and I will upload
0.8.17-5 later this evening.
I changed my mind and decided to add the new code to the existing
Debian package, rather than making a special library package to
Package: libhtml-linkextractor-perl
Version: 0.121-1
Severity: important
How to repeat:
# apt-get remove liburi-perl
# apt-get install libhtml-linkextractor-perl
% perl -e 'use HTML::LinkExtractor;'
Can't locate URI.pm in @INC (@INC contains: /etc/perl
/usr/local/lib/perl/5.8.4
$ cat foo.py
def nop(x):
No-operation decorator. Use like this:
[snip]
But epy/index.html corrupts the @-sign.
nop(x)
No-operation decorator. Use like this:
#64;nop
Ok, I see it. It looks like the problem is that epydoc generates:
span class=py-comment#64;nop/span
Edward,
Can you take a look at this Debian bug and let me know what you think?
You can find it here: http://bugs.debian.org/293571
This is what I've found so far. The _doctest_sub() function in
colorizer.py has responsibility for colorizing doctest blocks. It uses
a regular expression
Sorry for the delay in the reply, for some reason the e-mails got lost
(faulty spam filtering?) and I only found out you'd answered upon
checking up on the bug report.
It's OK. Spam processing is becoming a real pain. :(
OK, you are right, the JavaScript seems to be incorrect so I suppose
Please let me know if I can be of further assistance.
Thanks for the very complete report. I will let you know what more I
need from you.
KEN
pgp1lwDZPFfKy.pgp
Description: PGP signature
On Wed, Mar 23, 2005 at 07:37:33PM +0900, Takeru KOMORIYA wrote:
The site for Japanese grabber tv_grab_jp has changed its
format recently. So, I've wrote the patch against current cvs.
It works well for me, but I think we need to test it for a
while before commit.
Now in CVS.
The new
I received the following error:
Setting up pychecker (0.8.14-5) ...
/var/lib/dpkg/info/pychecker.postinst: line 45:
/usr/bin//etc/alternatives/python: No such file or directory
Line 29 of pychecker.postinst has a comment that is not true:
PYTHON=`readlink
On Wed, Mar 23, 2005 at 04:36:42PM -0600, Kenneth Pronovici wrote:
In this case, we would probably derive just PYTHON=python and then the
postinst would try to find compileall.py in /usr/lib/python, which
doesn't exist.
Sorry, I left off that I think I have a solution. I can just call
Package: polygen
Version: 1.0.6-4
Severity: wishlist
Hi,
_
/ Please document in manpage or \
| /usr/share/doc/polygen what polygen |
\ sources are available and what they do. /
-
Package: jspwiki
Severity: important
Tags: patch
Upgrading JSPWiki unexpectedly changes my configuration. In particular,
an upgrade seems to change jspwiki.pageProvider to FileSystemProvider
when I had previously set VersioningFileProvider. When this happens, it
usually takes a few weeks for my
hello, I used to have an old version of PythonCard installed, and now I
installed the Debian packages python-pythoncard, pythoncard-doc,
pythoncard-tools, and pythoncard, all versions 0.8.1-1.
Ok.
Now when I run resourceEditor, I get Unable to find PythonCard
installation.
A look at the
Well, I haven't heard back from you, but I have time to work on this bug
today, so I am going to make an upload. I am going to assume that my
theory is correct, and that your problem was caused by loose
dependencies between the various Pythoncard binary packages. I've
tightened up those
I've written upstream about this a few times, but he doesn't seem to be
there right now (or my messages are being spam filtered or something).
I think my change to the comment regular expression is sensible, even if
it's not a perfect solution, so I am going to make that change and
upload later
Shaun Andy -
A user of FreeGuide, which uses xmltv, says he needs
libarchive-zip-perl and libio-stringy-perl installed for freeguide to
work. I haven't needed these packages. The freeguide upstream author,
Andy, thinks it might be because the grabber for his region needs it.
What do you
Package: nbio
Version: 2.0-10
Severity: wishlist
Tags: patch
Please use the new 'libgcj-dev' package from gcc-defaults instead
of 'libgcj4-dev' in the Build-Depends.
I can do this. Just for my reference, what is the reason for the
change?
KEN
pgpEUhpAvySAS.pgp
Description: PGP
On Thu, Mar 31, 2005 at 07:32:34PM +0200, Andreas Jochens wrote:
On 05-Mar-31 10:14, Kenneth Pronovici wrote:
Package: nbio
Version: 2.0-10
Severity: wishlist
Tags: patch
Please use the new 'libgcj-dev' package from gcc-defaults instead
of 'libgcj4-dev' in the Build-Depends
Package: libxml-writer-perl
Version: 0.531-1
Severity: normal
File: /usr/share/perl5/XML/Writer.pm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
$ perl -MXML::Writer -e 'new XML::Writer(OUTPUT = \$a, ENCODING = utf-8);'
Not a GLOB reference at /usr/share/perl5/XML/Writer.pm line 442.
Package: libxml-writer-perl
Version: 0.531-1
Severity: normal
File: /usr/share/perl5/XML/Writer.pm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
$ perl -MXML::Writer -e 'new XML::Writer(OUTPUT = \$a, ENCODING =
utf-8);'
Not a GLOB reference at
On Thu, Apr 14, 2005 at 08:25:51AM -0400, Anthony DeRobertis wrote:
Kenneth Pronovici wrote:
Since $a hasn't been defined yet in your script, wouldn't you expect an
error?
No. The documentation says that passing a reference to a scalar will
have the XML written to the scalar (you can do
Hi,
I'm the maintainer for the Debian XML::Writer packages. I've just
received Debian bug #304477:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=304477
This bug documents a problem with the OUTPUT constructor parameter. The
constructor bombs out when this parameter is passed a scalar
On Fri, Apr 15, 2005 at 07:25:31PM +0100, Joseph Walton wrote:
[snip]
Sorry for a the lengthy response - none of those solutions is more
than about five lines, and it's really a question of policy rather than
mechanism.
The submitter suggests something like this:
Change the documentation
I assume we're talking about the tv_grab_na_dd grabber here? If so, I
believe the GUI piece of it is still experimental. However, I will
forward this bug report upstream and see what they think.
KEN
--
Kenneth J. Pronovici [EMAIL PROTECTED]
pgpC0OU308yYv.pgp
Description: PGP signature
Note that the actual dialog that accepts input does indicate:
Timezone offset (+/-) (+)
Based on this, I guess you can't be too surprised when it doesn't accept
input that doesn't match the format (+/-), such as -400 or values
containing Eastern or whatever.
Turning this question
Independent of which channels are selected - once the channels section
of the xml is generated the package returns:
Yeah, this is already known. It's SourceForge bug #1098886. Hopefully,
the problem will be fixed in the next XMLTV release. I don't know when
that will be, however.
KEN
--
When getting program-guides from multiple resion written in
one configration file, tv_grab_jp ignore some regions, only last
written region.
Thank you for the report. I have filed this with upstream as
SourceForge bug #1101373. Feel free to track the bug there if you would
like; otherwise,
tv_imdb (and possibly other xmltv scripts) garbles non-ascii characters,
probably since the last update of xmltv (the scripts worked fine before
2004-12-26, but weren't tested since then).
For reference, I have filed this with upstream as SourceForge bug
#1101376.
KEN
--
Kenneth J.
Kingsley -
I'm coming back to this ancient wishlist bug again, #176282:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=176282
You can't be seeing this actual problem any more with tv_grab_na (since
it doesn't exist any more), but I'm wondering whether you have the same
or a similar problem
Just for reference, I've filed this with upstream as SourceForge bug
#1101385. I have a feeling that Ed lost this bug when he was out of
the country earlier this year, and I forgot to remind him about it. Now
that I've filed the upstream bug, at least it won't get lost again.
KEN
--
Kenneth
I've filed this bug with CPAN as #9676:
http://rt.cpan.org/NoAuth/Bug.html?id=9676
KEN
--
Kenneth J. Pronovici [EMAIL PROTECTED]
pgpGiSdXB0OjX.pgp
Description: PGP signature
When trying to install the python-epydoc package I get the
following error:
Setting up python-epydoc (2.1-5) ...
dpkg: error processing python-epydoc (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
python-epydoc
E:
Package: jspwiki
Severity: important
I'm using Blackdown's Java 1.4 package with JSPWiki, which has always
worked before (at least, for the last year or so). The latest build of
the package (2.0.52-8) doesn't work any more with this install of Java.
It blows up with this exception:
Package: jspwiki
Severity: normal
Version 2.0.52-8 needs dpatch to build, but that package isn't listed on
the Build-Depends-Indep line and is not part of build-essential.
KEN
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386
It'd be nice if the help directory in the Options dialog defaulted to
the package installed /usr/share/doc/babygimp/doc instead of
/usr/local/doc/Babygimp.
And it'd be nice if the browser there defaulted to something neutral
like sensible-browser instead of kdehelp, so that at least
On 8/10/07, Jonas Meurer [EMAIL PROTECTED] wrote:
Package: ncompress
Version: 4.2.4.0-2
Severity: wishlist
Hello,
ncompress reffers to /usr/doc/ncompress/README.Debian in its package
description. This should be changed to
/usr/share/doc/ncompress/README.Debian, as documentation has been
On Thu, Jul 19, 2007 at 09:23:41PM -0500, Kenneth Pronovici wrote:
On 7/19/07, Cyril Brulebois [EMAIL PROTECTED] wrote:
Package: epydoc
Version: 3.0~beta1-1
Severity: normal
Tags: patch
please ask upstream to drop the '-u' option from the manpage, since it
is no longer supported. I
Just a note to indicate that I tested this with 3.0 beta 1 and it's
still true. I filed SF bug #1760007 to track the problem upstream.
KEN
--
Kenneth J. Pronovici [EMAIL PROTECTED]
signature.asc
Description: Digital signature
On Tue, Jul 17, 2007 at 12:38:20AM -0700, Cameron Dale wrote:
Package: python-epydoc
Version: 3.0~beta1-1
Severity: minor
A python file can import a module whose name contains a - (dash), using
the __import__ builtin function (just doing a normal import fails, as
identifiers cannot
Stephane -
I think that this old Epydoc bug should be addressed in the new 3.0 beta
1 release. Do you still have a test case around that you could check
against?
Upstream says:
The intended behavior is that epydoc should *not* ignore the encoding
of the source code, but it *should*
Ok, I'll push this upstream.
KEN
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
This has been filed as SF bug #1791281.
KEN
--
Kenneth J. Pronovici [EMAIL PROTECTED]
signature.asc
Description: Digital signature
This is fixed upstream in svn 1606. I'm not sure when beta 2 will be
coming out.
KEN
--
Kenneth J. Pronovici [EMAIL PROTECTED]
signature.asc
Description: Digital signature
Upstream says this is fixed in svn 1603. I'm not sure when beta2 is
coming out.
KEN
--
Kenneth J. Pronovici [EMAIL PROTECTED]
signature.asc
Description: Digital signature
Attached is a patch from upstream's Subversion for this fix.
KEN
--
Kenneth J. Pronovici [EMAIL PROTECTED]
Index: epydoc/docwriter/html.py
===
--- epydoc/docwriter/html.py (revision 1602)
+++ epydoc/docwriter/html.py (revision
Attached is a patch from upstream's Subversion for this fix.
KEN
--
Kenneth J. Pronovici [EMAIL PROTECTED]
Index: epydoc/apidoc.py
===
--- epydoc/apidoc.py (revision 1605)
+++ epydoc/apidoc.py (revision 1606)
@@ -111,11 +111,12 @@
Darn, I missed that. I was just looking at the diff from the previous
svn revision. I'll get this applied ASAP.
I'm looking forward to the 3.0 release. Have a good weekend!
KEN
On 9/30/07, Edward Loper [EMAIL PROTECTED] wrote:
Kenneth Pronovici wrote:
Attached is a patch from upstream's
Hi,
Thanks for the bug report and the patch. Interestingly, I just fixed
the platfomr typo myself yesterday in the upstream source. I'll fix
the other typo upstream too.
Note: I won't upload a new Debian package just to fix these typos.
Instead, the fixes will arrive in Debian with the next
On 12/17/06, Dmitry Rutsky [EMAIL PROTECTED] wrote:
Package: cedar-backup2
Version: 2.8.1-1
Severity: wishlist
Tags: patch
ide-scsi is obsolete on 2.6 kernels, cdrecord
(presently known as wodim in Debian by the way) can use recorders just like
wodim dev=/dev/hdc ...
and cannot (as
On 12/18/06, Dmitry Rutsky [EMAIL PROTECTED] wrote:
Package: cedar-backup2-doc
Version: 2.8.1-1
Severity: wishlist
In the descriptions of typical configuration process in chapter 4, sections
Setting up ..., there is step 5 in which suggests adding/enabling cron jobs.
I think
this step is too
On 12/18/06, Dmitry Rutsky [EMAIL PROTECTED] wrote:
It turns out that I'd overlooked relevant sections in the documentation
(Linux Notes in Chapter 4) and there is (or at least was) a way to use ATAPI
interface. Still it doesn't work for me, and
What happens when you execute this?
Hi Jörg,
I do appreciate the bug feedback -- but since this is a Debian bug
report, we have to deal with it in context of the packages available
in Debian, meaning wodim. I realize this is probably not a situation
you are happy with, and I do sympathize -- but the additional
advertisements for
On 12/18/06, Kenneth Pronovici [EMAIL PROTECTED] wrote:
On 12/18/06, Dmitry Rutsky [EMAIL PROTECTED] wrote:
It turns out that I'd overlooked relevant sections in the documentation
(Linux Notes in Chapter 4) and there is (or at least was) a way to use ATAPI
interface. Still it doesn't work
I'm going to dig a little further into your patch now and see what I
can do about supporting dev=/dev/cdrom and the like.
Upstream Subversion revision 1016 contains functionality equivalent to
your patch. I made the target_scsi_id parameter optional, and added
a hardwareId attribute on CdWriter
On 12/27/06, Gunnar Wolf [EMAIL PROTECTED] wrote:
Hi,
Any update on babygimp's status? If it no longer works and cannot be
fixed, maybe the best course of action is to remove it from Etch?
AFAIK, babygimp should already be removed from Etch per an email I
sent earlier to the release team. I
Package: cron
Version: 3.0pl1-86
Severity: wishlist
Hi,
It's sometimes difficult to distinguish between output from the
different jobs run as part of cron.daily. For instance, a recent email
I received contained these lines:
run-parts: /etc/cron.daily/bugzilla exited with return code 1
Package: ftp.debian.org
Severity: normal
Hi,
Please remove the babygimp package from the archive. It doesn't work,
upstream is dead and unresponsive, no one has stepped forward to fix any
of the bugs with it, and I am really not interested in debugging nasty
Perl-Tk incompatibilities. :)
In
Package: wnpp
Severity: normal
I am orphaning babygimp.
It doesn't work, upstream is dead and unresponsive, no one has stepped
forward to fix any of the bugs with it, and I am really not interested
in debugging nasty Perl-Tk incompatibilities. :)
I have also requested that babygimp be removed
On Wed, Jan 24, 2007 at 10:25:07PM +0800, LI Daobing wrote:
Package: pychecker
Version: 0.8.17-3
Severity: normal
warning on a well-defined python program
$ cat bug.py
def main():
' '.join(str(x) for x in range(10))
' '.join(str(x) for x in range(11))
$ pychecker bug.py
On 5/19/07, Cameron Dale [EMAIL PROTECTED] wrote:
Package: epydoc
Severity: normal
Tags: patch
There is a new upstream release available since February 2007 that has some
interesting enhancements for epydoc. I know it's a beta release, but as there
haven't been any releases in quite some time,
Eypdoc depends on the following utilities for its LaTeX functionality:
/usr/bin/latex
/usr/bin/makeindex
/usr/bin/dvips
/usr/bin/ps2pdf
The following packages provide these dependencies:
texlive-latex-base: /usr/bin/latex
texlive-base-bin: /usr/bin/makeindex, /usr/bin/dvips
I also had to use a weird version number (2.1+3.0beta1) so that later
upgrades to 3.0 will be automatic.
Incidentally, there's no need for weird version numbers like this.
Version numbers now support ~ to cover exactly this circumstance.
See:
http://lwn.net/Articles/194664/
A version
1 - 100 of 291 matches
Mail list logo
