I just built some fp-ide .debs with debugger support. Just send me a
mail if you're interested.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek
Package: joe
Version: 3.1-0.2
Severity: wishlist
Initially, I was happy to see that people picked up the project. Now I'm
deeply disappointed. They destroyed the portability, implemented very
useless syntax hilighting, and showed that they have no clue about coding
at all by totally f**king up
Maybe it'd also be a good idea to put -nobackups in by default. ;-)
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net |
+--- -- - `
), where good Pascal support is pretty important. :-) So I
think I wouldn't be a very good maintainer.
Greetings,
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux
Package: clearsilver
Severity: wishlist
I'm trying to install trac from source with bzr support. The bzr package
(including the libs used by trac) seems to require Python 2.4, while
clearsilver seems to work with 2.3 only.
If I knew more about Python and packaging I could make a patch, but I
is disable the
linestack module, it's the main problem. But without that module,
ctrlproxy isn't really useful... :-(
Wilmer van der Gaast.
on the channels you're in.
AFAIK it's because the linestack module doesn't flush any data.
Unfortunately there is no other suitable version I can upload. If one
appears, I'll upload it right away.
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| lintux
Package: libglide3
Version: 2002.04.10-11
Severity: normal
I don't know where to file this bug exactly, but this seems like a nice
starting point. I got a Voodoo3 card here and felt like experimenting with
it a bit. Anyway, things didn't work very well. X did enable direct
rendering, but glxgears
yet, but I
was pretty sure all the limits are gone.
Good to know. Let's see if this major new release will be suitable for
Etch or not, since it'd solve many of the BitlBee bugs in the Debian BTS.
Wilmer van der Gaast
lately with a valid MSN handle in
it. It seems the MSN servers don't feel a need to send proper TCP FIN
packets anymore when they close a TCP connection, which mainly causes
problems for BitlBee because it likes to keep empty switchboard
connections to use them for later conversations.
Wilmer van
at only one place, but I guess it
should then be included too...
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net
pool/main: 183 files 15.9MB 1s
pool/restricted: 2 files 1259kB 0s
Done Packages, Starting contents.
Done. 17.2MB in 185 archives. Took 1s
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer
Package: bitlbee
Version: 1.2.1-1
Severity: grave
Tags: security
Justification: user security hole
Since the fix to Mickey Mouse bug report 474589, BitlBee is runing as root
for most people, since the User = line is commented out by default.
-- System Information:
Debian Release: lenny/sid
APT
, hoping that the
problem will go away.
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net
Package: bitlbee
Version: 1.2.2-1
Severity: grave
Justification: causes non-serious data loss
There's another bug where a new user can overwrite existing accounts. This
does not give one access to anything that shouldn't be accessible, but it
does allow people to delete other people's accounts.
tag 293615 + pending
thanks
I put this in my development tree. Hope to do an upload soon (if
necessary I'll just do a 0.91-2 upload).
Thanks,
Wilmer v/d Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| lintux : :' : lintux.cx | | OSS Programmer
be the default port
(and 6668 if there's already something running on 6667). Also, 6668 is
quite a common port to run IRC daemons on, AFAIK...
What port is BitlBee running on on your machine right now?
Greetings,
Wilmer van der Gaast
I'm uploading 2.6.2-1 right now. Sorry for the late response, hope it'll
be in time for Sarge. ;-)
Wilmer v/d Gaast.
--
+ .''`. - -- ---+ + - -- --- - --+
| lintux : :' : lintux.cx | | Currently playing |
| at `. `~' debian.org | |
people, because it surely will give
stability problems.
So for now I'll put this back to severity wishlist.
Greetings,
Wilmer van der Gaast.
--
+ .''`. - -- ---+ + - -- --- - --+
| lintux : :' : lintux.cx | | Currently playing
my own software I'd be running Gentoy, not Debian...
Wilmer van der Gaast (misses iso8859-1).
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek
We use apt-ftparchive.
Yes, that's what I'm doing now too, see my other post to the bug. Works
like a charm now. :-)
Wilmer van der Gaast.
on buildds or wherever, but it'd
still be nice to have this fixed.
Wilmer van der Gaast. (trying to figure out the right way to enable
PASSFILE again...)
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux
Jelmer Vernooij wrote:
I've taken over maintainance (I'm the upstream maintainer), but I'm
still looking for a sponsor to sponsor the uploads of the latest
releases.
I was afraid you were still looking for a sponsor.
I think I should have more time for it now, so maybe I'll be able to do
it
-jabberserver.patch
Thanks for pointing me at a patch that I wrote myself. ;-) Seems that
Google Talk is quite popular, I'll think of uploading 0.92-2 then.
Greetings,
Wilmer van der Gaast. (both upstream and deb maintainer for BitlBee
Hello,
On 3 Jun 2008, at 05:53, Trent W. Buck wrote:
I believe the normal procedure is to a WONTFIX tag and leave the bug
open, so that people don't re-report the bug.
Hmm yes, I was already looking for close-with-reason commands but
couldn't find anything, I guess I'm spoiled by other bug
Hello,
I uploaded an Etch backport of the BitlBee 1.2-4 package to
backports.org this week.
http://packages.debian.org/search?keywords=bitlbee shows that it went
through most buildd's already by now. I hope this solves the problem
somewhat. I don't know if there's much else I can do. The change
severity 474589 minor
tags 474589 +pending
thanks
Marc Dequ?nes (Duck) ([EMAIL PROTECTED]) wrote:
Software is unusuable in ForkDaemon mode because you force running as
'bitlbee' user in the init script. Raised severity, as this is the
recommanded way of running bitlbee.
So, how does
free to NMU. I'll do my best to make sure you won't have to,
though.
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net
.
If this isn't really a policy violation, I'd rather reduce the bug
severity a bit and fix this in 1.1 packages.
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux
out. :-)
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net
The current BitlBee development version has a new daemon-mode, one that
fork()s off a process for every client. This gets rid of the inetd
dependency and has some of the daemon advantages (even though it still
fills up the process list a bit more, but that's just something we can't
avoid for now,
the .rej and .orig files from the .diff.gz... ;-)
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net
:nibbler.hengelo.gaast.net 002 wilmer :Host nibbler.hengelo.gaast.net is
running
As you see, it ignores empty lines. And since I'm using telnet, I know
that it sends CR-LF line-endings. So what's the problem exactly? I don't
get it, maybe you can send a traffic dump?
Wilmer van der Gaast
the patch to my bzr tree now, so I can't miss it later.
Great. :) If you tag it pending too, it will drop from my radar. :)
Doing that at this very moment, thanks for the hint!
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer
moritz wrote:
Please remove default passwords as provided by the configuration file.
This can become a security issue just too easily.
No passwords are required at all, and I don't even remember which
passwords those hashes resolve to exactly. :-)
The entries are commented out already. You're
Kapil Hari Paranjape wrote:
Infor is required for dependency based boot (init) systems in
/etc/init.d/bitlbee. (See [EMAIL PROTECTED] on
debian-devel-announce).
=20
Yeah, see the duped bug, Petter already submitted this bug a little
while ago, I'll upload it ~soonish.
Wilmer v/d Gaast.
--=20
forcemerge 472567 474943
thanks
(WTF.. I really clearly remember I put these commands in my previous
mail already...)
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | |
.
Wilmer van der Gaast.
--=20
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net
Also, I forgot to add, update-inetd isn't really consistent here. If I
run that remove command on my testing box with two BitlBee entries, I do
get a dialog asking if I really want to remove them both. Even if I
select Yes, it still doesn't remove anything.
--
+ .''`. - -- ---+ +
Package: bitlbee
Version: 1.2-1
Severity: normal
Filing a but to my own package, this justifies the high priority. :-) I don't
want this package to move to testing until I fix at least two issues:
*) Make /etc/init.d/bitlbee a conffile
*) Don't assume update-inetd is always there because it's
severity 472373 serious
thanks
reportbug ignored my severity because I chose for explanation Unknown,
and now I see severity serious is enough.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `.
, there will be a new snapshot
in get.bitlbee.org/devel/ in less than 24 hours.
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek
, of course).
This happened in the 1.0.x branch too and I forgot to copy it to bzr.
Stupid enough, I just uploaded 1.2-2, so I'll have to make it a 1.2-3 now...
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer
Petter Reinholdtsen wrote:
Well, there are less than 130 packages left to fix, and I NMU as
quickly as I can to fix the remaining packages, so I would urge you to
fix it very quickly. :)
Hmm. I'm just waiting for 1.2-3 to finally make it into testing. Will
you be able to wait for five days?
the case, I recommend removing 0
and 6 from the Default-Stop list.
Yes, sounds good to me.
Thanks,
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org
apt-get install rep
See also: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556403
This was broken for me too, took me a while to find out what it was.
Eventually using GNOME instead became too painful and counter-productive
so I straced the thing and found the fix. :-)
Wilmer.
--
Andrei Popescu wrote:
invoke-rc.d: unknown initscript, /etc/init.d/bitblee not found.
WTF :-/ Embarassing typo...
I know I tested the package and didn't have troubles with uninstalls
myself...
userdel: user bitlbee is currently logged in
Tss. Has processes running != logged in.
Wilmer.
--
Can you remember how tihs happened exactly? Maybe during a failed
upgrade or something like that?
I have no idea how this could happen so not sur ehow I should fix it...
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer
forcemerge 530345 531219
thanks
Hello,
Philipp Kern wrote:
ASAP. (And by the way there are currently two other RC bugs open, both
uncommented since three months.)
Best of all, the one you're reporting is a dupe. :-)
But yeah, I should pay more attention to this; working on that now.
Looking at this now.
Depends: bitlbee (= ${binary:Version})
The dependency seems right already, it's a binary dep, not a source dep.
I see other programs just make the dependency less tight by doing
something like
Depends: foo (= ${source:Version})
Is that the best I can get? :-/
Wilmer.
Hmm. Yeah, that code *should* be temporary and was only aimed at
upgrades in sid.
Just to be on the safe side I'll see about adding a warning to
init/maintainer scripts. It can still go wrong when upgrading from 1.0.x
to 1.2.3 if the user doesn't pay attention to the diffs.
Wilmer.
--
are on Jabber, but that doesn't seem like the right way to explain it
(not everyone knows what transports are).
Cheers,
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux
}.)
or something similar.
@Frank: Sorry, I clicked on that link, but failed to notice the comment
on the page, only saw the list of broken packages. :-/ But yes, that
page explains the same thing and says that something similar is .1~. :-)
Thanks for your help,
Wilmer van der Gaast
Package: bitlbee
Version: 1.2.5-1
Severity: serious
I should do an NMU of a new bitlbee-skype release before this package makes
it into testing. Opening this bug as a reminder and to hopefully keep it
out of testing.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT
switch to that then.
If you could verify that rcirc does the right thing with 320 that'd be
great. Otherwise, let's see what happens with 1.2.6.
Thanks,
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer
Sigh. I could've known. :-(
I spent a little while trying to pick a suitable number that isn't in
use already, but 333 is definitely in use already for /topic, yeah.
Bd choice, even though irssi let me get away with it.
This is definitely BitlBee's fault. I should find another int to use.
That's already fixed in 1.2.4 packages. I'm not sure if this bug is bad
enough that I can get it fixed in stable..
Wilmer.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | |
I'm getting some reports, I think they're all getting stuck around the
time the PRP MFN (friendly name) command is sent. Can you run tcpdump
and confirm that, and maybe send me a copy of the full dump?
I don't know if PRP MFN is the real problem or if any command would
trigger that response.
One step in the right direction:
http://bugs.bitlbee.org/bitlbee/ticket/115#comment:84
I can now add a bitlbee-plugin-otr package or something.
Wilmer.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
|
Although I understand the complaint, it's all a matter of tone. But this
is text, so the tone is interpolated by the reader. Try to expect more
kindness from BitlBee and it'll look a lot nicer. ;-)
But more seriously: This line has been there since the first release,
and is a somewhat
I have a full fix for this issue now:
http://bugs.bitlbee.org/bitlbee/changeset/devel%2C717
I hope to release 3.0.1 soonish.
Wilmer.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~'
Ah yes, IIRC this is fixed in bzr already. I'll hopefully have a 3.0.1
ready soon. Since 3.x won't make it into testing anyway for now I won't
hurry.
Wilmer.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org
Jelmer Vernooij wrote:
Debian, and have confirmed this request with Wilmer who is the current
maintainer of smbget in Debian)
Ack.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~'
Hello,
yellow wrote:
I notice that there is a wrong place for /usr/sbin/bitlbee which shall be
into /usr/bin
It's a daemon. Not entirely restricted to root, but it's not normally
meant to be started on the command line, only by init scripts.
If you just installed the package, you should
peter green wrote:
Does anyone know if there is any particular reason that bitlbee uses
libresolv.a rather than libresolv.so ?
Yes; the fact that Ulrich Drepper thought it'd be a good idea to declare
this API private and unsupported, claiming it's for internal use only,
even though it's
peter green wrote:
It looks like you forgot to really Cc them BTW?
I did but I resent the mail seperately to them afterwards.
Ah, found it. Looks like I'm not CC'ed on that anymore though. I think
it used to not work otherwise seems like a very good reason for me to
use the static lib. :-)
Alok G Singh wrote:
The libc6 version available in sid is 2.10.1-1, but bitlbee demands a version
strictly less than 2.10.
Note that I did not add that dependency myself. I have absolutely no
idea where it comes from and why it's not affecting any other package.
If you or anyone else who reads
Alok G. Singh wrote:
Rebuilding the package on a buildhost with the latest libc6 (2.10.1-1)
installed creates a package that does not conflict libc6. No changes are
required except the rebuild.
So that's what confuses me. Are you seeing this problem on amd64 or some
different arch? Because
Andreas Putzo wrote:
I consider this bug fixed. I added a clear comment to bitlbee.conf
saying that the Debian init script overrides this value with what's in
/etc/default/bitlbee.
Notice the version of the package i was referring to which does not have
your comments. It's usually better
Hello,
Eric Hermes wrote:
bitlbee will not start on kFreeBSD, and the following error shows up in
/var/log/daemon.log:
Mar 28 21:17:43 nene bitlbee[2269]: Unable to create UNIX socket: Protocol
not supported
That one isn't really a big deal, it's just the IPC socket (which isn't
On 17-02-11 08:09, Francesco Paolo Lovergine wrote:
It would be nice supporting identi.ca even. I love the twitter gateway,
adding identi.ca would satisfy most of the microbloggers out there.
I have good news for you: This is already possible. :-)
Docs are a bit lacking on this, but just
Can I just do an NMU to get this patch in Debian?
spamass-milter seems to be dead upstream for five years already..
Wilmer v/d Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~'
main mailserver again. I hope
we can have it upstream now. :-)
Just went through the whole diff once more, found no issues. I'm
attaching the newest version that should apply cleanly on 0.3.1-10.
Cheers,
Wilmer van der Gaast
Package: mimedefang
Version: 2.69-1
This is all I get:
Jul 16 16:43:54 jess mimedefang[22562]: No queue ID available in envfrom()
Which seems to be a known issue for a while already, and an extremely
common problem with Postfix and Milters annoyingly. 2.63 has a
workaround but apparently it
Package: src:linux
Version: 3.2.23-1
Severity: important
Dear Maintainer,
I don't know what exactly triggered this, but the result was that my /home
was no longer accessible after this event. My root filesystem was still
okay.
Marking as important because filesystem bugs could potentially
Hello,
On 02-11-12 15:33, Ben Hutchings wrote:
I don't know what exactly triggered this, but the result was that my /home
was no longer accessible after this event. My root filesystem was still
okay.
I assume this means it was no longer accessible until the next boot.
Oh yes, definitely.
Hello all,
This crash has happened to me three times now, but the last time is is
five days ago. Seems to have disappeared as mysteriously as it appeared.
On 08-11-12 15:30, Theodore Ts'o wrote:
On Fri, Nov 02, 2012 at 10:52:35PM +0100, Wilmer van der Gaast wrote:
whether my filesystem
Nice catch, thank you! NMU sounds good, I'll merge this into my tree too
then.
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek
Strangely, this has happened again a few days ago. Very similar
backtrace, and again triggered by Firefox. Annoyingly it was no longer
running within strace.
Wilmer v/d Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS
This just bit me too.
I understand the motivation for having this as a recommendation instead
of a dependency though.
Would it be reasonable to add a warning Please install packages
fgfs-aircraft-base and fgfs-models-base if you see this error message
or so?
Wilmer.
--
+ .''`. -
Since your prerm does not stop bitlbee on upgrade, by the time the
postinst tries to restart it, the executable has been replaced, and
start-stop-daemon cannot stop it.
To fix, you should instead of using --exec ,
use --pidfile /var/run/bitlbee.pid
I was going to fix this, but:
#
#
Package: ftp.debian.org
Severity: normal
The bitlbee source package now includes the Skype module, it is no longer
distributed separately.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
with an insatisfiable
dependency. My buildbot sets a version number at runtime and annoyingly
that only sets binary:Version, not source:Version.
I'll unmerge this stuff. Please in the future don't just assume the
other guy must be an idiot, crazy hacks may have a purpose.
Wilmer van der Gaast
Can you reproduce this with 3.2?
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net |
+--- -- - ` ---+ +-- - --- --
Hello,
On 22-03-12 15:38, Jonathan Wiltshire wrote:
This is CVE-2012-1187 [1]
Please investigate and if necessary backport the upstream fix [2] for this
problem to bitlbee in Squeeze for the next point release. If you need
assistance at any stage, do not hesitate to ask me.
Ah, hm. I've
priority can be left at its default, even though this is
security-related?
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek
On 06-07-13 16:35, Adam D. Barratt wrote:
On Tue, 2013-06-04 at 14:47 +0200, julien.cris...@logilab.fr wrote:
your package build-depends on libotr2-dev, which is no longer built
in sid as it has been replaced by libotr5-dev. Please port your
package to the new library.
Any news?
The guy
Just had a response from him on Twitter now, might get a fix over the
next weeks.
Wilmer v/d Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek
intrigeri (intrig...@debian.org) wrote:
If nothing has happened on this front, I'm afraid the OTR support in
BitlBee should now be considered as not maintained.
There's a fix actually, I've just not managed to take a closer look at
it, plus ther was some comment that it might not be complete
This should fix itself when libotr5 4.1 enters testing. I'm told that
irssi-otr and pidgin have exactly the same issue.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | |
/ch7/bind9-features.html suggests +subnet=
So maybe for compatibility you want to use that. I should maybe update
the patches.
Wilmer van der Gaast.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org
Source: poco
Severity: minor
Very minor but: Just noticed this header:
Homepage: http://poco.sourceforge.net/
Still having a project on SourceForge is not a good sign these days, and
definitely poco is not on it anymore. The URL above forwards to just
http://pocoproject.org/ now.
-- System
Package: gnome-terminal
Version: 3.16.2-1
Severity: normal
In the right click menu, for the last half a year or so already, there are
two items with the shortcut "O": Open link, and read-Only. This completely
defeats the purpose of the shortcut and for example just resulted in me
wondering for a
Hrm.
So in general I'm not much in favour of trying to handle edge cases not
normally produced by using the package normally to avoid doing the wrong
thing and ruining state further.
But in this case you've proactively created the bitlbee user (possibly
by just migrating your old passwd file)
I just had the same problem. I've straced gpg-agent and its child
processes which resulted in a 5.1MByte strace dump though I'd rather not
share it blindly.
I do see the following things in it:
7105 connect(9, {sa_family=AF_LOCAL, sun_path=@"/tmp/dbus-xNLgc87fg9"},
23) = -1 ECONNREFUSED
Yeah already preparing a fix. Turns out the fix from 3.4-1.1 was a
different fix from the one posted by the NMU'er on the bug. :-(
Instead of turning off networking temporarily, I managed to fix this by
just (re)moving
~/.config/chromium/Default/Extensions/pkedcjkdefgpdelpbcmbmeomcjbeemfm
(I hoped just turning off my Chromecast would've done it but that did
not work.)
Took me a few days before I finally ran into this bug
severity 883872 minor
Machine-readable is optional, and although not all attributed by exact
file or directory, everything in the existing file *is* accounted for
(Lintux == me at, hmm, 16 years old, and various files also in lib/
still come from Gaim which is mentioned.)
Patches for a fully
Severity: 883872 minor
stop
Please quote the part of
https://www.debian.org/doc/debian-policy/#copyright-information that
says "every single file must be mentioned in the copyright file". I
don't see it there nor would I see the point as per-file info is best
off stored in those very files.
Let
Yeah, this has always been a little bit iffy. Thankfully the
Skype-related packages can go away altogether. I'm not tracking BitlBee
development anymore but would expect that they go away in 3.6 (I'll have
to do the upload for it within the next few days so I'll verify).
signature.asc
1 - 100 of 111 matches
Mail list logo
