Sean Finney wrote:
Having a warning in lintian for arbitrarily long (perhaps = 256)
filenames is totally reasonable i'd say, but there's no reason to
otherwise throw out limits for the sake of having them.
Oh, I don't know.
Now that I check, the path provoking this was 269 characters
Sean Finney wrote:
Back when I was doing the conffile stuff I recall seeing hardcoded 256
character limits within dpkg in the archive handling stuff.
path_quote_filename(buf, fname, 256) and %.255s get used to display
filenames to the user, but I think anything lower level having that
limit
forcemerge 595927 606966
quit
Hi Sam,
Sam Morris wrote:
Package: dpkg
Version: 1.15.8.5
Severity: normal
dpkg hung while unpacking a package:
[...]
[5416783.438276] INFO: task dpkg:28315 blocked for more than 120 seconds.
[5416783.438330] echo 0
found 606975 git-core/1:1.6.3~rc1-1
tags 606975 + upstream fixed-upstream patch
# documentation bug
retitle 606975 blame: manpage advertises non-working --date format
(unsticked) syntax
severity 606975 minor
quit
Eugen Dedu wrote:
--date format
The value is one of the
Thorsten Glaser wrote:
Jonathan Nieder dixit[1]:
( ... )- runs ... in a subshell in the background, with its
output connected to a pipe.
[...]
On Linux and similar OSes this is typically implemented using
/proc/fd. A more portable implementation would use FIFOs
Dmitrijs Ledkovs wrote:
There are currently two free implementations of msvcrt: mingw.org and
mingw-w64.
Programs built with mingw32 *unable* to safely use DLLs built with
mingw64 there are subtle differences in implementations.
That answers my main question. Then I suppose:
We have one
found 607044 1:1.7.2.3-1
tags 607044 + upstream patch fixed-upstream
quit
Hi Philipp,
Ph. Marek wrote:
With my default setting in ~/.gitconfig
[diff]
noprefix = true
git rebase says
Applying: ...
fatal: git diff header lacks filename information when
Adam D. Barratt wrote:
Thanks for this, Jonathan; I have to admit that it didn't occur to me
while tidying up the preinst in -7.3.
Yes, I missed it, too. :/
fwiw, it looks like the postinst
will have the same issue.
Good catch.
Let me know if you need a sponsor for an upload fixing this.
tags 123252 + upstream
tags 123252 - fixed-upstream moreinfo
# difficult, apparently.
severity 123252 wishlist
quit
Ron wrote:
The following code demonstrates what I believe is the same issue as
was originally reported, but does so reading from stdin. Once the
aio_read has begun and blocked,
tags 476595 + upstream wontfix
quit
Hi Guido,
Guido Günther wrote:
for #476347 it'd be nice to have a:
git-add --allow-empty filepattern
git add is for humans and its behavior and output are potential to
change as our understanding of humans improves; git update-index is
for machines,
Adam D. Barratt wrote:
On Tue, 2010-12-14 at 03:12 -0600, Jonathan Nieder wrote:
Thanks. I've put something up at
- git://repo.or.cz/dash/debian/jrn.git for-sid
- http://mentors.debian.net/debian/pool/main/d/dash/dash_0.5.5.1-7.4.dsc
[...]
I haven't managed to spot any obvious issues
found 528270 git/1:1.7.2.3-2.1
tags 528270 - fixed-upstream
forwarded 528270
http://thread.gmane.org/gmane.comp.version-control.git/150141/focus=150346
quit
sean finney wrote:
it would be really nice to have in my ~/.gitconfig something that could
override the location of the hooks dir
Hi Cristian,
Cristian Ionescu-Idbohrn wrote:
On Sun, 28 Nov 2010, Herbert Xu wrote:
On Sat, Sep 04, 2010 at 07:35:04PM +, Jilles Tjoelker wrote:
This discarding is still bad as it throws away valid data if the open
file description is shared. This happens if stdin is redirected inside a
p3; do
echo p1=${p1}, p2=${p2}, p3=${p3}
done
Signed-off-by: Herbert Xu herb...@gondor.apana.org.au
(cherry picked from commit 55c46b7286f5d9f2d8291158203e2b61d2494420)
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
ChangeLog |4 ++
src/expand.c|9 ++---
src
Package: runit
Version: 2.1.1-6
Severity: important
1. Install git-daemon-run (version 1:1.7.2.3-2.1).
2. dpkg --purge git-daemon-run.
Then a second or two later, ps ax | grep runsvdir tells me
(linewrapping added):
runsvdir -P /etc/service log: \
rning: unable to open
severity 603827 serious
retitle 603827 fails to install noninteractively if procps is not installed
forcemerge 603827 606792
quit
Jonathan Nieder wrote:
runit.config contains the following:
if `ps -p 1 /dev/null`; then
db_input low runit/signalinit || :
else
be exploited only by person with
write access to gitweb config, or at least access to the repository).
This fixes CVE-2010-3906
Reported-by: Emanuele Gentili e.gent...@tigersecurity.it
Helped-by: John 'Warthog9' Hawley warth...@kernel.org
Helped-by: Jonathan Nieder jrnie...@gmail.com
Signed-off-by: Jakub
Hi Sedat,
Sedat Dilek wrote:
Maybe a CVE is now worth to package a new version?
See [1] and [2]. Probably 1.7.4-rc0 will be uploaded to experimental
as soon as it comes out (or maybe sooner, if it takes a long time ;-)).
Thanks for your interest,
Jonathan
[1]
Source: git
Version: 1:1.7.2.3-1
Severity: important
Jonathan Nieder wrote [1]:
You might have noticed that git's test suite is somewhat unreliable on
hppa.
A different problem occurs on the hurd (but aside from hurd and hppa,
all is well). Hmm.
1:1.7.2.3-1 2010-09-08 12.28 mozart
NightStrike wrote:
What's wrong with using the existing GNU triplet?
FWIW sorry for setting off this discussion (but thank you --- the
answers have been very helpful to me!). Luckily you provided a
good example that might help explain the purpose of Debian triplets
later in the thread:
Package: libssl-doc
Version: 1.0.0c-2
Severity: grave
Justification: cannot install
$ cupt full-upgrade
[...]
Unpacking libssl-doc (from .../libssl-doc_1.0.0c-2_all.deb) ...
dpkg: error processing /var/cache/apt/archives/libssl-doc_1.0.0c-2_all.deb
(--unpack):
trying to overwrite
Package: p910nd
Version: 0.93-2
Severity: minor
Justification: documentation
Hi,
Just installed p910nd. Unfortunately, it is not clear to me how to
get started.
From the postinst I learned that I should edit /etc/default/p910nd;
not sure how I would have learned the otherwise. From man p910nd
retitle 608051 git: pointless mailto links in manpages
severity 608051 minor
tags 608051 + upstream
quit
Oohara Yuuma wrote:
The manpage of git-commit(1) mentions aut...@example.com in the NOTES
section. Since it is a fictional address for explaining the --author
option, listing it among the
Julien Cristau wrote:
the release notes for squeeze will need to mention that any local
diversions of /bin/sh need to be removed prior to the upgrade. Any more
tweaking of this code path to support other shells as /bin/sh, if at all
necessary, will wait for post-squeeze.
Thanks, makes
Daniel Leidert wrote:
Am Sonntag, den 26.12.2010, 14:12 -0600 schrieb Jonathan Nieder:
Oohara Yuuma wrote:
The manpage of git-commit(1) mentions aut...@example.com in the NOTES
section. Since it is a fictional address for explaining the --author
option, listing it among the authors of git
forwarded 607982 http://bugzilla.redhat.com/583691
tags 607982 + fixed-upstream
quit
Lucas Nussbaum wrote:
It was fixed upstream, and the Ubuntu package contains the fix.
Thanks, tagging accordingly. [1] has the fix.
[1]
Hi,
Witold Baryluk wrote:
On 12-26 13:53, Julien Cristau wrote:
Upgrades skipping one release are not, and have never been, supported.
[...]
But on
http://www.debian.org/releases/testing/i386/release-notes/ch-upgrading.en.html
there is no explicit reference to etch, few times there is
Package: release-notes
Severity: minor
Section 1.1 1.1. Reporting bugs on this document of the squeeze
release notes says:
You will find more information describing how to obtain the
sources of this document in in Section 4.1.1, “Back up any data
or configuration
is not
+installed. (Thanks, Jonathan Nieder jrnie...@gmail.com)
+ * debian/control: Depends: procps (closes: #603827).
+
+ -- Daniel Kahn Gillmor d...@fifthhorseman.net Sun, 26 Dec 2010 14:19:53 -0500
+
runit (2.1.1-6) unstable; urgency=high
* debian/rules: don't set -D_FILE_OFFSET_BITS=64 on sparc (fixes
.
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
Javier Fernandez-Sanguino wrote:
Yes, the cross-reference is not correct. The actual sources are
available in the DDP's SVN and browsable at
http://svn.debian.org/wsvn/ddp/manuals/trunk/release-notes/#_manuals_trunk_release-notes_
Thanks
Hi Yves-Alexis,
Yves-Alexis Perez wrote:
I tried:
DEB_BUILD_OPTIONS='noopt,nostrip' debuild -us -uc
This should be
DEB_BUILD_OPTIONS='noopt nostrip' debuild -us -c
An example gcc command line is:
gcc -DHAVE_MKSTEMP -DHAVE_HYPOT -DHAVE_FILE64 -DHAVE_MKSTEMP64
-DHAVE_FONTCONFIG
reassign 616168 libsvn-perl 1.6.12dfsg-4
quit
Hi Daniel,
Daniel Kahn Gillmor wrote:
$ git svn init -Thttp://trac-hacks.org/svn/tagsplugin/trunk \
-thttp://trac-hacks.org/svn/tagsplugin/tags \
-bhttp://trac-hacks.org/svn/tagsplugin/branches
I believe you are looking for
git svn
tags 615922 + upstream patch
forwarded 615922 http://thread.gmane.org/gmane.comp.shells.dash/496
quit
Tim Allen wrote:
src/main.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
Thanks! Gerrit, I'd like to propose the combination of Tim's patch
and my tweak of it as a patch for
Aaron M. Ucko wrote:
As I recall, I was running reiser3 at the time.
Thanks. To summarize:
A lintian-clean Debian package failed to unpack with ENAMETOOLONG.
Setting maximum lengths for paths and filenames in data.tar.gz
in policy could prevent future mistakes of this kind, without making
Matthias Klose wrote:
fyi, here is a partial rebuild with gcc-4.6 without the work around applied:
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110111-gcc-natty.html
A quick grep -F '[-Wunused' finds nothing, while grep -F
'[-Werror=unused-but' finds 34 packages:
'
| make: *** [build] Error 2
How about this patch?
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
debian/changelog | 11 +++
debian/control |2 +-
debian/rules |8 ++--
3 files changed, 18 insertions(+), 3 deletions(-)
diff --git a/debian/changelog b/debian
Source: axis2c
Version: 1.6.0-2
Severity: important
User: peter.fritzs...@gmx.de
Usertags: unresolved-symbols-so
Tags: upstream
Hi,
axis2c doesn't build from source for me, due to errors triggered with
-Werror. I'll file a separate bug for that in a moment.
This bug is about what happens when
+DEB_BUILD_OPTIONS=noopt or DEB_CFLAGS_APPEND=-Werror in the
+build-time environment.
+ * Build-Depends: dpkg-dev (= 1.15.7) for dpkg-buildflags.
+
+ -- Jonathan Nieder jrnie...@gmail.com Thu, 03 Mar 2011 01:48:21 -0600
+
axis2c (1.6.0-2) unstable; urgency=low
* Fix patches/03_enable-security to enable
happy to know it will be
there when I need it. :)
Regards,
Jonathan
[1] http://lists.debian.org/debian-devel-announce/2011/02/msg00012.html
From: Jonathan Nieder jrnie...@gmail.com
Date: Thu, 3 Mar 2011 03:01:31 -0600
Subject: Remove unused variable
This variable was never used, even when first
Hi,
Jonathan Nieder wrote:
--- a/debian/control
+++ b/debian/control
@@ -5,7 +5,7 @@ DM-Upload-Allowed: yes
Uploaders: Daniel Nurmi nu...@eucalyptus.com, Graziano Obertelli
grazi...@eucalyptus.com, Chris Grzegorczyk g...@eucalyptus.com, Thierry
Carrez thierry.car...@ubuntu.com
XSBC
Jonathan Nieder wrote:
+ debhelper (= 8), dpkg (= 1.14.7),
This should say dpkg-dev (= 1.14.7). Sorry for the thinko.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Jonathan Nieder wrote:
--- a/debian/control
+++ b/debian/control
@@ -5,7 +5,7 @@ Maintainer: Debian Acpi Team
pkg-acpi-de...@lists.alioth.debian.org
Uploaders: Michael Meskes mes...@debian.org,
Loic Minier l...@dooz.org
Standards-Version: 3.9.1
-Build-Depends: debhelper
Hi,
Michael Meskes wrote:
I prefer fixing the bug over working around it. Even makes the patch smaller:
I should mention that gcc-4.6 gives another warning[1]. In general I
think -Werror is a good tool for development but not so good when
autobuilding, since warnings can subtly vary from
user debian-...@lists.debian.org
clone 616194 -1
severity -1 important
retitle -1 acpid: will FTBFS with gcc-4.6 (error: variable ‘type’ set but not
used [-Werror=unused-but-set-variable])
usertags -1 - ftbfs-gcc-4.5 ftbfs-gcc-4.4
block 615157 by -1
quit
Michael Meskes wrote:
* Make both
Michael Meskes wrote:
Could you please give us the whole warning gcc-4.6 spits out?
Sure, sorry about that.
cc -g -O2 -Wall -Wextra -Wundef -Wshadow -Werror -c -o libnetlink.o
libnetlink.c
libnetlink.c: In function ‘rtnl_from_file’:
libnetlink.c:444:17: warning: variable ‘type’ set but not
Michael Meskes wrote:
Sorry, I didn't see that as I dn't use gcc-4.6.
No problem; I should have mentioned it before.
Which is why I think it should stay in there. We build on way more systems
than
upstream probably can, so keeping -Werror in will help the package.
Fair enough.
Now that
Bill Allombert wrote:
On Wed, Mar 02, 2011 at 10:17:32PM -0600, Jonathan Nieder wrote:
Another question: is Debian policy the right place to make a decisions
like this? Ideally these maxima would be set using some cross-distro
standard like POSIX or the FHS. Sadly:
I do not think
Bill Allombert wrote:
Not really; the packager might not be able to change the filename without
breaking either
FHS compliance, the interface or compatibility with upstream.
Ah, now I think I understand a bit better.
FHS compliance sounds like a red herring to me. Does the FHS mandate
tags 587377 + wontfix
quit
Sean Finney wrote:
On Thu, 2011-03-03 at 15:58 -0600, Jonathan Nieder wrote:
* how many characters of grace area can tools like dpkg-divert feel
free to use?
I don't think tools should be like whoa, i think this filename is going
to be too long for some
Bill Allombert wrote:
To give an example: Debian policy mandates that the file
/usr/share/doc/package/changelog.Debian.gz
exists.
Now perl subpolicy mandate that the perl module
Foo::Bar::Baz::Qux::Quux::Quuux::Qx
whic live in /usr/share/perl5/Foo/Bar/Baz/Qux/Quux/Quuux/Qx
be
Hi Pertti,
Pertti Kellomäki wrote:
I ran into this issue today. The sequence of events was:
Excellent! I wonder:
. What filesystem are you using?
. What kernel (uname -a)?
. Did you catch what 'git diff-files' and 'git ls-files -u' said
at the time?
. Can you reproduce it?
3) At this
Hi Sergey!
sergey wrote:
What do you think about placing README in each system directory?
I think the idea is interesting but agree with Steve that policy is
not the best way to move it forward. Packages already can put README
files in particularly mysterious directories, and I don't see a
Hi again,
sergey wrote:
It is like bad tradition now: many documentation do not contain information
about
Debian version. It is very strange for me. How can be authors 100% sure
that their documentation is absolutely correct for all Debian versions,
from 1.1 or older to the current?
In
didn't know about that page. I agree that it's not worth
spending time on other aspects. So please feel free to ignore the
rest of this message. ;-)
On Tue, Mar 01, 2011 at 10:24:05PM -0600, Jonathan Nieder wrote:
retitle -1 debiandoc2html: link titles should not have embedded tags
What
Russ Allbery wrote:
Does that look okay?
Yes, the version in branch 504880-rra looks good to me (with one
tweak:
--- a/policy.sgml
+++ b/policy.sgml
@@ -4027,5 +4027,5 @@ fi
in prgnpostrm/prgn purges the prgndebconf/prgn
configuration for the package
forcemerge 587279 616462
quit
Hi Marvin,
Marvin Renich wrote:
to
...the packages in main
• must not require a package outside of main for compilation or
execution (thus, all declared Depends, Recommends, and
Build-Depends relationships must be satisfiable with only
Hi,
Colin Watson wrote:
On Tue, Nov 02, 2010 at 04:17:02PM -0400, Joey Hess wrote:
The only glaring problem is that Pre-Depends: ${misc:Pre-Depends} needs to be
added -- but I suppose lintian can be made to check for that.
Yes (and I think I forgot to document that, but that's a simple
a similar fix.
Reviewed-by: Jonathan Nieder jrnie...@gmail.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi,
Ansgar Burchardt noticed:
perl/5.8.0-7 added /etc/perl to @INC:
* Prepend /etc/perl to @INC to provide a standard location for
configuration modules:
But this addition has never been documented in the Debian Perl Policy.
Russ Allbery wrote:
Good point. Here's updated proposed
Raphael Hertzog wrote:
On Sat, 21 Aug 2010, Russ Allbery wrote:
Hm. All the words that I had intended to be there are there. I clearly
need to rephrase it somehow, though, if it's not clear. How about:
When two packages both declare the same ttconffile/tt, they may
see left-over
forcemerge 504880 403649
quit
Hi Frank,
Frank Küster wrote:
Current Policy says:
, 7.2 Binary Dependencies
| The Depends field should also be used if the postinst, prerm or
| postrm scripts require the package to be present in order to
| run. Note, however, that the postrm cannot rely
tags 556015 - patch
quit
Hi,
Russ Allbery wrote:
Here's a patch that is explicit about the required dependencies and
discourages the last case. Does this look good to everyone?
I'm missing some background but hopefully that's all right. Quick
comments.
+++ b/policy.sgml
@@ -573,10
Hi Russ,
Russ Allbery wrote:
Right, this was the reason why I hadn't committed anything yet. We have
to decide whether we're going to prohibit arch:any - arch:all links
completely to ensure that the binNMU changelog entries are visible. My
inclination is to do so, and hence drop this whole
Hi,
Steve Langasek wrote:
Sorry this has taken so long; I spun my wheels on it
for some time because I couldn't quite accept that there were so few
additional requirements that needed to be specified here!
Thanks for your work. :)
[...]
+ tasks at boot time. However, any package
Raphael Hertzog wrote:
Pushed a fix to master. It's not important enough to warrant a fix in
lenny. Maybe squeeze...
FWIW I think sid will be enough. I was only flailing around for words
for this is why the patch does not apply directly to master.
Thanks, Raphaël. :)
Jonathan
--
To
Bill Allombert wrote:
On Sat, Mar 05, 2011 at 02:19:12AM -0600, Jonathan Nieder wrote:
Maybe policy could allow (but discourage) packages that only support
some non-Sys-V init system as long as they include a dependency
indicating so?
This would be a terrible idea. We would end up
Hi Sergey,
sergey wrote:
Does Debian policy can recommend something (including READMEs)? Or policy can
only
force something, no recommendations is possible?
Policy sets rules that make sure the system works well. These can be
hard requirements (generally using the word must), which
Hi,
Steve Langasek wrote:
So in this case the pre-dependency
should *not* be set, as it only serves to complicate the upgrade path.
I think this example might deserve a closer look. Documentating the
required dpkg version seems useful for backporters and others who
would use the package in
(-cc: Steve since he is already subscribed to -policy)
Hi Sergey,
sergey wrote:
I agree that it is a good place for proposals like mine.
But making long well-developed draft and driving it - this is
mostly operating system developer's task, not users one.
I think that Debian should have some
Package: chromium
Version: 10.0.648.114~r75702-1
Hi,
Two quick observations:
1.
$ chromium-browser
bash: chromium-browser: command not found
This breaks scripts, so I think it should be mentioned in NEWS.Debian.gz
and perhaps a compatibility symlink provided for a short time.
2. If
Osamu Aoki wrote:
This may be a bug which can be quickly fixed.
I guess dropping all ... should be enough. I can even agree this to
be minor bug which is annoynig enough.
Thanks! Confirmed, version 1.2.21 fixes this for me.
--
To UNSUBSCRIBE, email to
Package: libc6-dev
Version: 2.13-0exp3
Severity: minor
Justification: noisy, results in ugly code
Tags: upstream
Forwarded: http://sourceware.org/bugzilla/show_bug.cgi?id=11959
Hi,
Testcase follows[1].
The C standard I/O facilities include an error flag on file streams,
so instead of a noisy
Hi again,
Jonathan Nieder wrote:
Unfortunately glibc marks fwrite --- but oddly not the other stdio
output functions --- with __wur (which expands to
__attribute__((__warn_unused_result__)) when optimization is enabled
and the _FORTIFY_SOURCE feature is in use).
An alternative fix would
Package: gcc-4.6
Version: 4.6-20110227-1
Severity: minor
Justification: cosmetic
Tags: upstream
Using -Werror with -pedantic to catch constructs the standard does not
permit:
$ ./test.c; # case (1)
./test.c:6:7: warning: ISO C90 does not support flexible array members
[-pedantic]
$ ./test.c
(switching topics; sorry for the cognitive dissonance)
Steve Langasek wrote:
Taken in sum, there is a cost to that documentation.
Thanks for a nice summary.
On Sat, Mar 05, 2011 at 06:26:27PM -0600, Jonathan Nieder wrote:
Bug#593177 brings the possibility of change. In the extreme case
forwarded 583433 http://thread.gmane.org/gmane.comp.lib.glibc.alpha/15973
found 583433 eglibc/2.13-0exp3
quit
Hi,
Ian Zimmerman wrote:
The line just below the comment should be #ifdef and not #ifndef. See also
/usr/include/bits/local_lim.h where the same mechanism is used (correctly).
I've
Hi Yann,
Yann Dirson wrote:
dpkg-deb -b apparently uses some temporary files which can take some
place. When it fills /tmp, it stops with a no space left on device
error, but since it cleans up before exiting, the user is left with
few clues as to where to add space. An explicit message
reassign 617441 hardening-wrapper
forcemerge 615262 617441
affects 615262 + binutils
quit
Hi Mats,
Mats Erik Andersson wrote:
The new binutils package installs a hard link
hrwxr-xr-x root/root0 2011-03-03 09:10 /usr/bin/ld link to
./usr/bin/ld.bfd
This causes an unresolvable
of
git-el because debbugs doesn't know about the latter yet.)
Thoughts?
Jonathan Nieder (2):
debian/git-el: avoid spurious doc/git/contrib/emacs.old directory
debian/git-el: remove spurious doc/git/contrib/emacs.old directory
debian/changelog | 11 +++
debian/git-el.postinst
@@
+git (1:1.7.4.1-3.1) experimental; urgency=low
+
+ * git-el.postinst: check if /usr/share/doc/git/contrib/emacs is
+already a symlink before making room for one.
+
+ -- Jonathan Nieder jrnie...@gmail.com Wed, 09 Mar 2011 16:52:14 -0600
+
git (1:1.7.4.1-3) unstable; urgency=low
[ Anders
to install git-el
once), remove it.
- if contrib/emacs/emacs is a symlink (from trying to install git-el
twice), remove it.
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
debian/changelog |4
debian/git-el.postinst |6 ++
2 files changed, 10 insertions(+), 0 deletions
Package: icedove
Version: 3.1.9-1
Severity: grave
Hi,
Typical experimental system. Trying to run icedove, I get
$ icedove; echo $?
/usr/lib/icedove/icedove-bin: symbol lookup error:
/usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc
127
I have no plugins installed.
reassign 617760 chromium
severity 617760 important
severity 616623 important
forcemerge 616623 617760
affects 616623 + chromium-browser
quit
Fathi Boudra wrote:
Since latest upgrade, I cannot run chromium.
Looking into the package, it seems the main binary is missing.
The new package calls it
Christoph Goehre wrote:
On Fri, Mar 11, 2011 at 01:28:33AM -0600, Jonathan Nieder wrote:
$ icedove; echo $?
/usr/lib/icedove/icedove-bin: symbol lookup error:
/usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc
127
I have no plugins installed. Any hints
severity 617784 wishlist
quit
Hi Bertrand,
Bertrand Yvain wrote:
package git should not depend on emacsen-common.
The postinst in git 1.7.4.1-3 uses emacsen-common to clean up after
git 1.7.4.1-1. So it really is intended.
Is the dependency causing a problem?
--
To UNSUBSCRIBE, email to
tags 426938 + moreinfo
quit
Hi again,
4 years ago, Bart Massey wrote[1]:
As of now, the conflict markers generated by merges
sometimes include only a relative symbolic name such as
HEAD. A SHA1 should also always be included, so that
months later the marker is still meaningful.
My
forcemerge 617784 618015
quit
Hi Klaus,
Klaus Ethgen wrote:
I was near to write idiotic dependencies but that would be not
objective.
However, my system was emacs free until the update today that brings
emacsen-common in by git.
This strikes me as an odd thing to say. Did you know that
tags 618015 - sid
quit
Klaus Ethgen wrote:
Ups, sorry, overlooked this bug.
No problem --- the bug list is pretty daunting to wade through.
Looks good. Ill give em a test. (I see no problems from the log.)
Good to hear. :)
Thanks for reporting it, by the way.
Jonathan
--
To
reassign 609627 gwibber
quit
Hi Kartik et al,
Ben Bromley wrote:
I've installed Firefox in /opt so that I can run the beta. I linked
/opt/firefox/firefox to /usr/bin/firefox, and I have been using that location.
I have Firefox listed as the preferred application for web browser, and used
Package: yelp
Version: 2.30.1+webkit-1
Severity: minor
Justification: cosmetic
$ yelp 21 |grep .
(yelp:9290): Gtk-CRITICAL **: IA__gtk_tool_button_new: assertion `icon_widget
== NULL || GTK_IS_MISC (icon_widget)' failed
(yelp:9290): GLib-GObject-WARNING **: invalid (NULL) pointer instance
tags 596527 + moreinfo
quit
Hi Eliad and Christina,
Emilio Pozuelo Monfort wrote:
On 02/12/10 15:42, ctineo wrote:
when execute gnome-help
ghelp:///usr/share/gnome/help/network-admin/es/network-
admin.xml Or any app with help button many windows open and freeze computer.
Can you still
retitle 531575 yelp: OMF category 'Applications|Other' not recognised, ignoring
quit
Dominique Brazziel wrote:
Since the move from 'scrollkeeper' to 'librarian0/rarian-compat'
there are hundreds of these messages in '.xsession-errors':
OMF category 'Applications|Other' not recognised,
Package: yelp
Version: 2.30.1+webkit-1
Severity: normal
Aron Xu wrote[1]:
2. Registering to doc-base won't benefit users of Yelp or something in
same category.
Yep. Even with rarian-compat installed, none of the documentation
from doc-base is visible in yelp for me. This makes the effort of
clone 607498 -1
retitle -1 doc-base: not clear what to do with multiple-file text documents
severity -1 wishlist
quit
Robert Luberda wrote:
And this is the main problem here - how doc-base or other tools should
handle documentation consisting of multiple text documents? I've just
checked how
Josselin Mouette wrote:
The performance issue is still here, we need to wait for yelp 3.0 for it
to be solved. The classification issue is still here: completely random
and mostly useless documents appear more prominently than the core GUI
documentation, and this is not acceptable.
Thanks.
tags 403409 - moreinfo
quit
Eric Cooper wrote:
Unfortunately I haven't been able to reproduce this so far. Any
insights would be appreciated (or if you are able to somewhat
reliably reproduce it though can't explain how, that would be
interesting, too).
I can't reproduce it either. I
reassign 546208 yelp 2.26.0-2
forcemerge 609644 546208
quit
Robert Luberda wrote:
Yes, I was checking yesterday why doc-base docs are not visible in yelp,
but failed to find the reason. I found out that I had already reported
bug #546208 against rarian-compat about this issue.
FYI:
# as before
unmerge 546208
reassign 546208 rarian-compat 0.8.1-4
severity 546208 important
quit
Robert Luberda wrote:
There's a similar issue in khelpcenter, and both yelp and khelpcenter
worked fine when scrollkeper was used. That's why my bug was about the
rarian-compat package.
Also your
tags 609176 + upstream moreinfo
quit
Dmitry Azhichakov wrote:
Ctrl-Shift-I shows the 'Developer tools' frame but nothing is working in it.
It's just dead. I've checked it with clean user-data-dir also.
Works for me (also with chromium-browser 9.0.597.19~r68937-1 but on
i386). Any hints for
tags 609176 - moreinfo
quit
Dmitry Azhichakov wrote:
After I hit ctrl-shit-I, the panes show, but empty. I can switch Elements to
Resources to Scripts etc. But they are empty: no html tree displayed, no
scripts etc. On Resources I can see a selection: Only enable for this
session or Always
301 - 400 of 6971 matches
Mail list logo
