Package: xul-ext-zotero
Version: 4.0.22-1
Severity: normal
right-click on a just-downloaded pdf, select retrieve metadata (last
item), and it gives a popup about installing pdf tools, which then opens
the zotero preferences window in the search tab, which says
PDF Indexing
Package: python-serial
Version: 2.6-1.1
Severity: normal
pyserial 2.7 has been up on pypi and sf.net since late 2013, but the
debian package is only 2.6 and is older than that... is there some
reason I'm missing that it was held back at the time? I don't see
anything in the changelog.Debian
Package: photofloat
Version: 0~20120917+dfsg-3
Severity: normal
Tried a run based on the instructions in /usr/share/doc/photofloat/README.Debian
$ mkdir photo
$ cd photo
$ mkdir albums cache
$ ln -s /usr/share/photofloat/web/* .
$ mkdir albums/flickr
$ ln $(kpa-grep --tag flickr) albums/flickr/
Package: ftp.debian.org
Severity: normal
barnowl is a fork that people actually use, and there was some plan to
do something clever about this that didn't go anywhere - it's time to
just make it go away. Thanks!
Package: postgresql-common
Version: 189
While diagnosing an unrelated problem with pg_upgradecluster, got the
"Configuring already existing cluster" message and chased down the code
to this, starting at line 351:
if ($existingver = $version) {
print "Configuring already existing
Freshly installed to test this:
i-meant-that$ dpkg --status sqlcipher|grep Version
Version: 3.2.0-2
i-meant-that$ sqlcipher mydata.db
SQLCipher version 3.8.6 2014-08-15 11:46:33
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> pragma key = 'passphrase';
sqlite>
Oh, this is already known upstream:
https://github.com/sqlcipher/sqlcipher/issues/196
so it should be "merely" a matter of getting the sid version into
stretch-backports.
Subject: debhelper: dh_installsystemd --name documentation doesn't match actual
behavior
Package: debhelper
Version: 13.11.6
Severity: normal
Dear Debhelper Maintainers,
The dh_installsystemd documentation says that
As an example, B will look for
F<<< IB<< I >>I<.service> >>> instead
Package: python-sphinx
Version: 0.4.2-1
Severity: wishlist
Both sphinx-build and sphinx-quicksetup attempt (and fail) to use ansi
color sequences, even when TERM=dumb (for example, when run from an
emacs shell buffer, or m-x compile. This produces garbage, like this:
^[[01mSphinx v0.4.2,
Package: bfr
Version: 1.6-2
Severity: normal
bfr(1) ends with POD ERRORS.
POD ERRORS
Hey! The above document had some coding errors, which are explained
below:
Around line 179:
You forgot a '=back' before '=head2'
Around line 181:
'=item'
Package: xscreensaver
Version: 5.05-3
Severity: wishlist
I couldn't find anything in the man page (and haven't dug in to the
code yet) but I use xscreensaver to lock my laptop screen, and a new
login button is something I don't want to have. (This is distinct
from debbugs#304406 which suggests
This is checked in compilation-time. I could build a
`xscreensaver-nonewlogin' package but I think could be annoying... And
if you're using no [x|g|k]dm I guess you should know that there's no
option to new login :).
There are two issues here:
(1) according to apt-file search,
To create the re identifier on the Python side, you need to write
M-x pymacs-exec RET import re RET
It's nice that there's another workaround, but the real problem is
that the example as-written in the documentation didn't work :-)
Additionally the documentation will be clarified in the
Package: aptitude
Version: 0.4.4-4
Severity: normal
Specifying -o Aptitude::ProblemResolver::StepLimit=0 (I'm looking
for a way to turn off the resolver entirely, in a controlled-upgrade
scenario where it shouldn't require resolution to complete the upgrade
and I want it to fail instead, without
Package: owl
Version: 2.1.8-2.1
Severity: wishlist
not actually known to fix anything, but should be upgraded for
completeness, I hadn't heard about it.
-- System Information:
Debian Release: lenny/sid
APT prefers gutsy-updates
APT policy: (500, 'gutsy-updates'), (500, 'gutsy-security'),
Package: subversion
Version: 1.1.3-1
Severity: serious
subversion's debian/rules line 13:
include /usr/share/cdbs/1/rules/patchsys-quilt.mk
subversion's debian/control build-depends: cdbs (=0.4.26)
cdbs 0.4.27-3 changelog.Debian, ChangeLog, and changelog make no
mention of quilt. There is a
Package: pymacs
Version: 0.22-3
Severity: normal
Under @subsection Python handles:
(setq matcher (pymacs-eval re.compile('pattern').match))
Debugger entered--Lisp error: (error Python: Traceback (most recent call last):
File \/usr/lib/python2.3/site-packages/Pymacs/pymacs.py\, line 95, in
Package: dnsdoctor
Version: 1.0.0-2
Severity: normal
File: /usr/bin/dnsdoctor
dnsdoctor --help says:
-o, --outputOutput (see output)
output: [byseverity|byhost] [text|html]
byseverity*[bs] Output is sorted/merged by severity
byhost [bh] Output is
Package: python-django
Version: 0.96-1
Severity: normal
$ pydoc django.db
problem in django.db - EnvironmentError: Environment variable
DJANGO_SETTINGS_MODULE is undefined.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
by django-admin. I'm sorry that this behaviour is unfriendly towards pydoc
but I doubt there's any way to avoid this (without defining the variable
DJANGO_SETTINGS_MODULE to point to a valid Django settings module).
As long as it stays open as a bug, that's fine; I suspect there *is* a
way to
On closer inspection - django.db only *has* two functions and they
don't have any docstrings :-) though presumably the __import__ changes
that by pulling them in from django.db.backends.*.base.
It could be argued, then, that a sufficient fix to the original
problem would be to include a pointer
Package: svn-load
Version: 0.6-1
Severity: normal
(Note that this is the unstable version, built on and running on etch...)
svn-load does a
if not svn_path_exists(url, ''):
sys.stderr.write(Error connecting or no such repository: %s\n % url)
sys.exit(1)
svn_path_exists
perhaps svn-load should be merged with vcs-load-dirs which has the
same functionality, only targeted at different VCSes. The common
infrastructure could probably be reused for subversion, too.
I'd prefer (as a user) to have svn-load, because it supports a
specific usage that none of the
Package: jam
Version: 2.5rel-1
Severity: normal
Because jam is not compiled with -D_FILE_OFFSET_BITS=64 it treats any
file over 2G as missing; this is particularly inconvenient when
using jam to build iso images of large software releases.
Since jam doesn't deliver any libraries, this seems like
Note that this also points out a failure to meet policy manual 10.1,
Binaries:
By default, when a package is being built, any binaries created
should include debugging information, as well as being compiled with
optimization.
What's going wrong is that the build rule only passes CFLAGS in
Package: fakechroot
Version: 2.5-1.1.20070223-2
Severity: normal
(again, ignore the version as it's a local build with a bunch of
previously submitted changes applied)
I don't see a reason not to let subsequent chroot() calls within an
already running fakechroot succeed - it's not like the
Package: fakechroot
Version: 2.5-1.1.20070227-1
Severity: normal
(again, that's a local build version, but it is based on 2.5-1.1 with
patches from other current bugs.)
The execve wrapper, correctly, expands the actual-filename argument
because the kernel needs an unfake name. It then looks for
Package: fakechroot
Version: 2.5-1.1.20070227-1
Severity: normal
mktemp() just expands the template and passes it on to the real
mktemp. If the template is an absolute path, that causes us to return
an unfake path. Instead, it needs to
* narrow the result
* copy (memmove) it back into the
Package: fakeroot
Version: 1.2.10
Severity: normal
I'm not sure that subject is clear, but the demonstration that follows
should be:
wildcat$ fakeroot
wildcat# id -u
0
wildcat# id -g
0
wildcat# python
Python 2.4.1 (#2, Oct 18 2006, 20:58:01)
[GCC 3.3.5 (Debian 1:3.3.5-13)] on linux2
Type help,
Clint Adams [EMAIL PROTECTED] writes:
I'm not sure that subject is clear, but the demonstration that follows
should be:
Currently fakeroot doesn't support nested operation. There is this
little block in faked.c:
if(getenv(FAKEROOTKEY_ENV)) {
/* I'm not sure -- maybe this can work?) */
Package: fakechroot
Version: 2.5-1.1
Severity: important
Inside fakechroot, make displays
make[1]: Entering directory `/home/eichin/'
ie. it display the *outside* path. Yet a Makefile target running pwd
gives the correct value. (I was hunting this down in search of
another problem...)
(I went digging for this in search of an explanation for a
/bin/sh: line 1: cd: .: No such file or directory
message from deep in a
fakeroot/fakechroot/pdebuild/pbuilder/dpkg-buildpackage
stack, and will see if this helps shortly... but since it's clearly
wrong even if it doesn't, I
I saw that mailsync doesn't work from cron problem under Ubuntu
6.06, using mailsync 5.2.1-2build1; given that unstable has 5.2.2 and
it (and libc-client) has the exact same lines of code, the analysis
below applies there too...
Given a .mailsyncrc including
channel slurp imapmail localfile {
Package: fakechroot
Version: 2.5-1.1.20070207-1
Severity: normal
readlink -f . inside fakechroot displays the external path, instead
of the local one. Looking at coreutils, readlink -f calls
canonicalize_file_name, which is supported, but it only calls it on
the input side... it looks like it
Package: fakechroot
Version: 2.5-1.1
Severity: wishlist
I particularly care because I am using pbuilder with fakechroot on a
machine that uses nscd; pbuilder stuffs an entry into the chroot'ed
/etc/passwd, /etc/shadow, and /etc/group, but then can't reference it.
(There's no exposed mechanism to
Package: fakechroot
Version: 2.5-1.1.20070212-6
Severity: important
(Ignore the version, it's my local build with other fixes, the bug is
clear from reading the source...)
libfakechroot.c, readlink() implementation, in particular the
end-of-buffer handling, can truncate links; coreutils readlink
Package: krb5-clients
Version: 1.4.4-7etch1
Severity: normal
According to http://web.mit.edu/kerberos/mail-lists.html krb5 bugs
should be submitted with krb5-send-pr. I suggest either actually
including it in some package, *or* if you prefer for these bugs to go
through debian, to have a
The proximate cause of that obscure error message appears to be that
/usr/src/modules/alsa-driver/usb/usx2y/usbusx2y.h
says
typedef struct {
snd_usb_audio_tchip;
...
but snd_usb_audio_t isn't defined anywhere.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
and the proximate cause of *that* was that there was an older
alsa-source unpacked previously in /usr/src/modules/alsa-driver;
apparently modass silently failed to erase the previous version before
unpacking the new one.
So I'd suggest transferring this bug to module-assistant, or just
closing
Package: erc
Version: 5.3-1
Severity: normal
(C-c C-j runs the command erc-join-channel)
connected to freenode, joined #python.web. c-c c-j #python did
nothing, no errors, but no new buffer and no change either. c-c c-j
#pylons however did create a new buffer with the #pylons channel in
it.
Package: dfo
Version: 0.7+svn45-4
Severity: normal
dfo mostly works, but I get these mono tracebacks intermittently while
or perhaps after syncing (photos, tags, and sets seem ok, pools aren't
up to date though...)
near t: syntax error
at Mono.Data.SqliteClient.SqliteCommand.GetNextStatement
Barry deFreese [EMAIL PROTECTED] writes:
Package: owl
Version: 2.1.8-2.1
Severity: normal
User: [EMAIL PROTECTED]
Usertags: proposed-orphan
Dear Maintainer,
While reviewing some packages, your package came up as a package that
should maybe be orphaned by its maintainer, because:
* Out
http://groups.google.com/group/dfo-users/browse_thread/thread/50e04abad374aca5
suggests that it's a similar sql-injection-ish quoting error; the fix
given in that thread is mostly a demonstration, it's not anywhere near
complete, but at least it's another instance of the same thing...
--
To
Package: fakechroot
Version: 2.5-1
Severity: normal
A package using libtool to build shared libraries, and then run them
in-tree, ends up having two executables and a helper script... one of
the executables is .libs/lt-foo and it has a run-time-link-path encoded into
it (objdump -p, look for
Package: nbd-client
Version: 1:2.8.4-1
Severity: normal
Fetched 64.1kB in 0s (79.2kB/s)
Preconfiguring packages ...
Configuring nbd-client
--
nbd-client can handle multiple concurrent connections. Please
state the number
of connections you'd
Package: kpilot
Version: 4:3.5.2-0ubuntu6
Severity: normal
(apologies if this should go somewhere ubuntu-specific, but m-x
debian-bug sends it here... the version in unstable is only a little
bit ahead of this one, though, but I haven't tested for the bug there.)
Invalid entry (missing ']') at
Was this in mondo-archive.log?
Yes -- surprisingly, I even still have that /var/log/mondo-archive.log around
:-)
When you run the latest version of mondo, do you still get this?
For unrelated reasons, I haven't run it since then, and so I don't
really have any idea where to start...
If the lyx in stable actually works with examples/docbook_article.lyx
now (the original bug report was pre-sarge), go ahead and close it - I
don't have any other examples (we switched from lyx back to straight
latex back in 2004 or so.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Package: bzip2
Version: 1.0.2-8
Severity: normal
File: /usr/bin/bunzip2
$ tail -2 /etc/motd | zcat --force
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
$ tail -2 /etc/motd | bunzip2 --force
$
There are two reasons this bothers me:
1.
Do you keep config.log from these? (Although in this case it's
libfaim/config.log I guess.) The report doesn't actually give
enough information to figure out what the bug is...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dann frazier [EMAIL PROTECTED] writes:
I've tried to reproduce this issue in various scenarios, but haven't
been able to yet. Can you provide me the command you used?
--
dann frazier
I just tried the svn_path_exists I mentioned in the original bug
report under Ubuntu Hardy pre-alpha
Package: libneon27-dev
Severity: normal
Attempting to build debs of the 1.5.x branch of subversion fails when
libneon27-dev is installed:
libtool: link: cannot find the
Package: python-svn
Version: 1.5.1-2
Severity: normal
The script below sets up a test repository, and then generates this output:
file:///tmp/pysvn-bug/test_repos/trunk/testing/file with spaces
[('file with spaces', PysvnInfo '')]
Package: vncsnapshot
Version: 1.2a-1+b1
Severity: normal
Took some playing around with ltrace to catch this, but
vncsnapshot -tunnel ${host}:3 /tmp/${host}.03.jpg
gives a Usage message which includes
Usage: vncsnapshot [OPTIONS] [HOST]:DISPLAY# filename
vncsnapshot [OPTIONS] -listen
Package: libpam-runtime
Version: 1.0.1-5+lenny1
Severity: normal
libpam-runtime.postinst does a clever update if the md5sums match our
records bit, but only
if [ -z $2 ] || dpkg --compare-versions $2 lt 0.76-17
which appears to mean it only triggers on upgrades from sarge to etch
(since lenny
Package: postgresql-common
Version: 94lenny1
Severity: normal
The ssl-cert package creates the ssl-cert group in its postinst.
postgresql-common does:
if getent group ssl-cert /dev/null; then
adduser --quiet postgres ssl-cert
fi
to add the postgres user to this
Package: ntp
Version: 1:4.2.4p4+dfsg-8lenny2
Severity: normal
ntp (1:4.2.4p4+dfsg-4) unstable; urgency=low
* Also use lockfile-progs to ensure that ntpd does not start while
ntpdate.ifup is running (closes: #436029)
-- Peter Eisentraut pet...@debian.org Tue, 29 Apr 2008 11:19:54 +0200
Looks like it's enough to
$ git clone git://gitorious.org/python-markdown/mainline.git
$ cd mainline
$ svn co
svn://svn.debian.org/python-modules/packages/python-markdown/trunk/debian
Bump the version (debian/changelog diff) and tweak the rules file:
Index: debian/changelog
Sven Joachim svenj...@gmx.de writes:
tags 120160 + moreinfo
thanks
Hello Mark,
I'm going through the list of old Emacs bugs in Debian. This one is a
bit mysterious to me.
On 2001-11-19 04:50 +0100, Mark W. Eichin wrote:
Package: emacs21
Version: 21.1-5
Priority: wishlist
Could
Appreciate the effort... except the resulting ratmenu doesn't actually
display those characters, against a Karmic X server (where the uxterm
example works fine.) XmbTextEscapement returns zero for the non-ASCII
string, even though def_string is empty and missing_charset_count is
zero...
I haven't
Explicitly setting LANG=en_US.UTF-8 helped, and installing more
fonts (xfonts-terminus in particular) improved things further (didn't
work by itself, $LANG really is critical to Xmb* working, it appears.)
Now that I can actually demonstrate it, I'm happy to push the change
out, should show up
Package: python-werkzeug
Version: 0.3.1-1
Severity: normal
/usr/share/doc/python-werkzeug/html/index.html points to a missing
unicode.html.
The source package contains
python-werkzeug-0.3.1/docs/src/unicode.txt
but python-werkzeug-0.3.1/build doesn't have a corresponding
unicode.html...
--
I'll take a look at those patches and also see if upstream is at all
interested. (Last resort would be a self-immolating
use-barnowl-instead package.)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
FYI I've just heard back from kretch and he's testing a new release,
so we should be able to kick out a new package within the week.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
found a second reset_heartbeat instance that did the same thing;
switched to checking against not HB_DISABLED for consistency.
--- tzc-2.6.15.orig/tzc.c
+++ tzc-2.6.15/tzc.c
@@ -1369,7 +1377,9 @@
globals-ebuf = (char *) malloc(globals-ebufsiz);
globals-ebufptr = globals-ebuf;
-
Package: sysvinit
Version: 2.86.ds1-61
Severity: normal
When looking at some etch-lenny upgrade diffs, noticed that while the
sysvinit postinst creates a symlink from /etc/nologin to
/var/run/initscripts/nologin, the first shutdown after the upgrade
(or install) simply deletes the symlink.
While you're updating things for nikola 6 - Debian only has python-doit
0.22.1, and nikola (6.2 at least, but probably went in earlier) needs at
least doit 0.23 (and the failure mode is an obscure error, under earlier
versions.)
--
_Mark_ eic...@thok.org eic...@gmail.com
I needed post-0.5 to play with the spark.io spark core, which needed
:leave support at least; dropping the debian dir into a git clone of
upstream, running ./autogen.sh (and doing a dpkg --commit of that, which
was probably wrong but I got about 15 seconds into untangling the cdbs
autotools
Package: dgit
Version: 0.21
Severity: minor
Used dgit to pull ratmenu 2.3.20 down, work on it, pushed 2.3.21 which
made it to unstable, dgit fetch again for consistency, made more changes
for 2.3.22, tried to push ... but *forgot* to dgit build first (I'd
been testing with dpkg-buildpackage
Package: googlecl
Version: 0.9.13-2
Severity: wishlist
A possible new upstream for googlecl appeared on the forum, I just
noticed it:
https://groups.google.com/forum/#!topic/googlecl-discuss/WqlM3fpBOVE
https://github.com/vinitkumar/googlecl
I have no particular opinion on the validity of this
Package: python-pbs
Version: 0.95-1
Severity: normal
per the top of https://pypi.python.org/pypi/pbs, as of pbs 0.110, pbs is
now sh, see http://pypi.python.org/pypi/sh which is at 1.09 (see also
http://amoffat.github.io/sh/)
-- System Information:
Debian Release: jessie/sid
APT prefers
Package: kphotoalbum
Version: 4.5-1
Severity: normal
Just got the popup about trying the Android app, which acts as a remote
for the client, and I tried it and it worked... with *no access control*
or even a popup...
lsof confirms that kphotoalbum is just listening on a port:
kphotoalb 29586
Got email from the upstream author who pointed out (and I just
confirmed) that once you've started, hit *Settings, *Configure
KPhotoAlbum, under the General Tab, Miscellaneous section, you can
uncheck *Listen for Android devices on startup.
I believe that for Debian this should certainly default
Since this gets written out to ~/.kde/share/config/kphotoalbumrc under
[General] as listenForAndroidDevicesOnStartup=false, it might be
possible for the Debian-specific patch to install something in the
existing global config in /usr/share/kde4/config/kphotoalbumrc though
that uses different
Package: docker.io
Version: 1.2.0~dfsg1-1
Severity: normal
man docker-inspect includes:
Getting the IP address of a container instance
To get the IP address of a container use:
# docker inspect --format='.NetworkSettings.IPAddress'
1eb5fabf5a03
172.17.0.2
75 matches
Mail list logo
