Bug#962692: puppet: Crashes due to "missing" facts.d directories
>From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962320 I guess swapping libboost library versions may be a more proper fix. Though I haven't tried this myself yet.
Bug#962692: puppet: Crashes due to "missing" facts.d directories
Huh https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962320 may in fact be a duplicate.
Bug#962692: puppet: Crashes due to "missing" facts.d directories
On Fri, 12 Jun 2020, at 09:38, intrigeri wrote: > > Some stracing uncovered that it was trying to read the following > > directories: > > > > /opt/puppetlabs/facter/facts.d > > /etc/facter/facts.d > > /etc/puppetlabs/facter/facts.d > > > > through trial and Aborted errors I've created those and now it works again. > > I confirm this workaround fixes the problem for me as well. > Thanks for figuring it out and sharing this workaround :) > Ha, no worries, glad you discovered this so quickly then! For others who run into this, let's reduce the above into a oneliner: mkdir -p /opt/puppetlabs/facter/facts.d /etc/facter/facts.d /etc/puppetlabs/facter/facts.d I just realised that indeed my other testing box had this problem and again it was resolved by creating these directories. Logs show that puppet on this box disappeared on the 7th. (I separately have a cronjob that restarts puppet daily due to memory leaks (maybe long gone, the cronjob is years old), helping early discovery of this issue) dpkg.log doesn't show any ruby or puppet packages being touched then but I do see some libboost libraries, I believe at least some of these are (indirect) puppet dependencies? `//
Bug#962692: puppet: Crashes due to "missing" facts.d directories
Package: puppet Version: 5.5.19-1 Severity: grave Justification: renders package unusable Since the recent Ruby upgrade, Puppet invocations have been very noisy for a while already. But by now it's not even starting. Even after a dpkg -P including most dependencies (including apt-get remove ruby.*) then reinstalling, all I get is: wilmer@veer:~/adsb$ sudo puppet agent --waitforcert 60 -t /usr/lib/ruby/vendor_ruby/puppet/util.rb:461: warning: URI.escape is obsolete /usr/lib/ruby/vendor_ruby/puppet/file_system/file_impl.rb:80: warning: Using the last argument as keyword parameters is deprecated free(): invalid pointer Aborted Some gdb'ing and strace'ing suggests it gets stuck in facter, which indeed fails individually with the ~same error. Some stracing uncovered that it was trying to read the following directories: /opt/puppetlabs/facter/facts.d /etc/facter/facts.d /etc/puppetlabs/facter/facts.d through trial and Aborted errors I've created those and now it works again. Really wondering what's special about my system, or are more folks seeing this? -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages puppet depends on: ii adduser 3.118 ii facter 3.11.0-4.1 ii hiera 3.2.0-2 ii init-system-helpers 1.57 ii lsb-base 11.1.0 ii ruby 1:2.7+1 ii ruby-augeas 1:0.5.0-3+b8 ii ruby-deep-merge 1.1.1-1 ii ruby-shadow 2.5.0-1+b3 Versions of packages puppet recommends: ii debconf-utils 1.5.74 ii lsb-release 11.1.0 ii ruby-selinux 3.0-1+b3 Versions of packages puppet suggests: pn ruby-hocon pn ruby-rrd -- no debconf information
Bug#883872: Bumping Severity
OK, there's always http://code.bitlbee.org/debian/README.html Sorry for those who now end up without a BitlBee package. But really the nightly builds are pretty stable. :-) Patches are welcome while I don't have time for this. Cheers, Wilmer. signature.asc Description: OpenPGP digital signature
Bug#921895: bitlbee: does not build all binary packages by default
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 Description: OpenPGP digital signature
Bug#883872: (no subject)
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 me know if there's something actually serious like a *licence* not being accounted for, or a (significant) author or group of authors (that is not the currently mentioned me/dx/BitlBee team or Gaim team) not mentioned.
Bug#883872: bitlbee: Extremely incomplete d/copyright
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 comprehensive copyright file are welcome :-)
Bug#853017: bitlbee: FTBFS on every autobuilder: dh_testroot: You must run this as root (or use fakeroot).
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. :-(
Bug#767230: bitlbee-plugin-otr: bitlbee no longer starts: libotr API version 4.1.0 incompatible with actual version 4.0.0
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 | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: Digital signature
Bug#711071: bitlbee: please port to libotr5-dev
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 yet. I've asked for clarification since I might have misundestood this part: http://bugs.bitlbee.org/bitlbee/ticket/1004#comment:9 This has been keeping noteworthy security improvements for all other consumers of libotr out of Jessie for too long now, so I recommend that bitlbee is built without OTR support in Debian -- this certainly can be reverted when it gets updated and maintained again :) Argh! I had no idea this was blocking other packages, sorry. :-( Well it'd be easy to just omit the bitlbee-plugin-otr package from Debian for now while this is getting resolved. Although omitting a single binary package is probably easier said than done. I have very little time for this stuff at the moment, sadly. :-( Wilmer v/d Gaast. -- + .''`. - -- ---+ +- -- --- - --+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: Digital signature
Bug#711071: bitlbee: please port to libotr5-dev
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 who implemented OTR support is AWOL and I'm not interested in maintaining it. :-( Wilmer v/d Gaast. -- + .''`. - -- ---+ +- -- --- - --+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: OpenPGP digital signature
Bug#711071: bitlbee: please port to libotr5-dev
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 wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: OpenPGP digital signature
Bug#681146: bitlbee-common: fails to install, purge, and install again
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 wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651612: bitlbee: diff for NMU version 3.0.3-1.1
Hello,
On 15-12-11 20:47, Julien Cristau wrote:
+bitlbee (3.0.3-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Use the standard ${source:Version} and ${binary:Version} substvars instead
+of the custom and broken ${bee:Version} (closes: #651612).
+
Please in the future instead of boldly declaring how someone else's
stuff is broken and doing an NMU without even warning the original
maintainer (who already had a fix ready himself and uploaded a few days
earlier except it got stuck in NEW), think of WHY a seemingly broken
thing is in place.
Indeed the bee:Version hack is gross and it doesn't make me happy
either. When I saw your patch I tried to remember why I used it in the
first place (it's been a year), couldn't figure it out and decided to
just merge your stuff, assuming I missed something.
But indeed now my buildbot is generating packages 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.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net |
+--- -- - ` ---+ +-- - --- -- -+
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603681: bitlbee-common: fails to install
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 | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: OpenPGP digital signature
Bug#575572: bitlbee-skype won't work with 1.2.5
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 policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-xen-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages bitlbee depends on: ii adduser 3.112 add and remove users and groups ii debconf [debconf-2.0]1.5.28 Debian configuration management sy ii debianutils 3.2.2 Miscellaneous utilities specific t ii libc62.10.2-6Embedded GNU C Library: Shared lib ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification ii libglib2.0-0 2.22.4-1The GLib library of C routines ii libgnutls26 2.8.5-2 the GNU TLS library - runtime libr ii net-tools1.60-23 The NET-3 networking toolkit bitlbee recommends no packages. bitlbee suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#557946: apt-get install rep
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. -- + .''`. - -- ---+ +- -- --- - --+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: Digital signature
Bug#551775: bitlbee: Uninstallable package due to conflict with libc6
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. :-) Someone had bitlbee removed from testing now, stating eglibc migration as the reason. I wonder what that means? What system are you getting those errors with? in my sid chroot there doesn't seem to be any problem linking bitlbee with libresolv.so instead of libresolv.a, doing so produces a package with a sane dependency on libc6 and an objdump shows all those symbols being in libresolv.so and having sane versioning. Oh, crap. :-( I forgot to re-add -lresolv. With that, things now do work indeed. I wonder since when that is the case. I can see that at least 2.3.6.ds1-13etch9+ doesn't like this yet. That doesn't really narrow it down too much yet though. :-) But in that case, I'll just do a source NMU. I'm not sure if this actually fixes this exact problem, but at least it's more correct. Wilmer. -- + .''`. - -- ---+ +- -- --- - --+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: OpenPGP digital signature
Bug#551775: bitlbee: Uninstallable package due to conflict with libc6
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 documented in various places already, including IIRC O'Reilly's DNS BIND. I can see that as a good reason for using the static version in upstream bitlbee. Nevertheless debian does appear to provide a libresolv.so with a proper soname and linking against it does seem to give sane dependencies from dpkg-shlibdeps so maybe it would be a good idea to use it in the debian packages. Ccing debian-glibc to see if they have an opinion on the matter. It looks like you forgot to really Cc them BTW? So yeah, we'd need a libresolv.so that exports these: lib/lib.o: In function `srv_lookup': /home/wilmer/src/bitlbee/devel/lib/misc.c:483: undefined reference to `__res_query' /home/wilmer/src/bitlbee/devel/lib/misc.c:486: undefined reference to `ns_initparse' /home/wilmer/src/bitlbee/devel/lib/misc.c:489: undefined reference to `ns_parserr' I wonder if we could get this fixed in eglibc.. You could always sed it out of debian/substvars between the call to dpkg-shlibdeps and dpkg-gencontrol but it's a bit ugly to say the least. Heh, yeah, that was pretty much my last resort solution. But I'm sure I can cook up a proper regex as a workaround somehow to at least return the package to the old situation (before dpkg-shlibdeps detected use of these private symbols). Also, I have a bitlbee branch that uses evdns instead, which also makes the lookups asynchronous, but it's not ready for merging yet. Wilmer. -- + .''`. - -- ---+ +- -- --- - --+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: OpenPGP digital signature
Bug#551775: bitlbee: Uninstallable package due to conflict with libc6
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 AFAIK the problem is happening on more than just amd64. If that's not the case, the problem could be that I built the package on my amd64 testing box. Wilmer. -- + .''`. - -- ---+ +- -- --- - --+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: OpenPGP digital signature
Bug#551775: bitlbee: Uninstallable package due to conflict with libc6
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 this has any clue about this, I'd love to hear about it. If not, I'll probably try to see what's going on here during the weekend. Wilmer. -- + .''`. - -- ---+ +- -- --- - --+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: OpenPGP digital signature
Bug#531219: Bug#530345: bitlbee-dev currently uninstallable due to binNMUs
Adeodato Simó wrote:
Well, techincally they're different issues: you can fix #530345 just by
doing a sourceful upload with no changes, but source changes are needed
to fix #531219. But it seems you're interested in fixing #531219 already,
which is excellent. :-)
Fair point.. But yes, if I fix my package I want to fix it properly; I
just uploaded a BitlBee 1.2.3-2 that fixes a whole bunch of bugs. :-)
(And hopefully doesn't introduce anything too serious. :-P)
So with not possible I mean that you need, normally:
Depends: foo (= ${source:Version}), foo ( ${source:Version}.)
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.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net |
+--- -- - ` ---+ +-- - --- -- -+
signature.asc
Description: OpenPGP digital signature
Bug#531219: bitlbee-dev: package is not binNMU-safe
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. Wilmer. -- + .''`. - -- ---+ +- -- --- - --+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: OpenPGP digital signature
Bug#530345: bitlbee-dev currently uninstallable due to binNMUs
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.
--
+ .''`. - -- ---+ +- -- --- - --+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net |
+--- -- - ` ---+ +-- - --- -- -+
signature.asc
Description: OpenPGP digital signature
Bug#514572: (no subject)
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. -- + .''`. - -- ---+ +- -- --- - --+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: OpenPGP digital signature
Bug#498159: bitlbee: Another account hijacking bug
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. 1.2.3 fixed this problem and I'm about to upload it. I did a thorough review of all relevant code and made sure this can't happen again. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bitlbee depends on: ii adduser 3.110 add and remove users and groups ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii debianutils 2.30 Miscellaneous utilities specific t ii libc6 2.7-13 GNU C Library: Shared libraries ii libevent1 1.3e-3 An asynchronous event notification ii libglib2.0-0 2.16.4-2 The GLib library of C routines ii libgnutls26 2.4.1-1the GNU TLS library - runtime libr ii net-tools 1.60-19The NET-3 networking toolkit bitlbee recommends no packages. bitlbee suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495877: Not too fixable in the .deb
Hello, So actually the postinst already does a chown -R on $CONFDIR. I think the problem is that you upgraded your BitlBee, then reconnected to the new version. The old version (still running as root) then saved it settings, and there it broke. :-/ Unfortunately there's little the BitlBee package can do about this. Setting the setuid bit on a directory doesn't have any effects (and would be a bit odd anyway), so I guess this has to be the price of running testing/sid. I'll make the init script do a quick find + chown, hoping that people who get this problem will restart the BitlBee daemon, 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 | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: OpenPGP digital signature
Bug#494656: bitlbee: Runs as root
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 prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.16.60-xen (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages bitlbee depends on: ii adduser 3.108 add and remove users and groups ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii debianutils 2.30 Miscellaneous utilities specific t ii libc6 2.7-10 GNU C Library: Shared libraries ii libevent1 1.3e-3 An asynchronous event notification ii libglib2.0-0 2.16.4-2 The GLib library of C routines ii libgnutls26 2.4.1-1the GNU TLS library - runtime libr ii net-tools 1.60-19The NET-3 networking toolkit bitlbee recommends no packages. bitlbee suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474589: socket error when bitlbee is started
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 this make the software unusable? This is just a warning. This socket is not important at all for normal BitlBee in use. In fact, I'm not sure if there's anything that uses this socket so far. It's just there so future packages could maybe use it to send IPC commands to automatically restart the master daemon, for example. IOW, you just blew up a little bit of syslog noise into a bug that could throw BitlBee out of the next Debian release. :-) Btw, bitlbee has a User = directive in his configuration file, so i guess setting the user in the init script is useless and misleading. Yep, that one wasn't there yet when the init script was written (2 years ago). I got a patch here that switches to using this instead of letting start-stop-daemon do this, that'll solve the problem. I'll do an upload soonish. Wilmer v/d Gaast. -- + .''`. - -- ---+ +- -- --- - --+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: Digital signature
Bug#361503: bitlbee_1.0.2-1(amd64/unstable):
On 8 apr 2006, at 20:25, Frederik Schüler wrote: bitlbee misses a build dependency on po-debconf: *Oof* It indeed does. I'm building a new package now. Thanks for the quick notification. I have to clean up my BitlBee packaging stuff a bit, keeping two trees in sync is obviously not working out. :-) Wilmer van der Gaast. -- + .''`. - -- ---+ +- -- --- - --+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ PGP.sig Description: This is a digitally signed message part
Bug#349570: Where in policy?
Hello, I noticed this bug is keeping 1.0.x from entering testing. :-( So which part of the policy is violated by this behaviour? Don't touch, maintainer scripts will do it files aren't that rare in /etc, and it shouldn't be hard to run dpkg-reconfigure once to set the new port number. 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 `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349570: Bye bye inetd
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, without getting too many stability issues), including inter-Bee-communication. :-) I can't close these bugs yet, I don't know when this stuff will be ready for a release. If it takes a few months, I'll try to fix at least some of these bugs, but I'd rather close them all at once by introducing ForkDaemon. Wilmer. -- + .''`. - -- ---+ +- -- --- - --+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: Digital signature
Bug#333835: ctrlproxy: Eats up memory making the system unusable
On 19 nov 2005, at 10:41, Steve Langasek wrote: Do we actually have reason to believe that this is a memory leak, i.e., leaving the daemon running will continue to eat more memory? If the program simply needs 70-some MB to run, that's unfortunate Well, if a simple IRC proxy would require that much memory, I'd get worried anyway. ;-) if, OTOH, its memory usage continues to grow beyond the point shown in the bug report, I agree that sounds release-critical. Yeah, it doesn't really stop. It brought down my server once too. It grows by a couple of MBytes a day, depening 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 : :' : lintux.cx | | OSS Programmer www.bitlbee.org | | at `. `~' debian.org | | www.algoritme.nl www.lintux.cx | +--- -- - ` ---+ +-- - --- -- -+ PGP.sig Description: This is a digitally signed message part
Bug#333835: ctrlproxy: Eats up memory making the system unusable
Oops, didn't set up GMail yet to forward BTS mails too, so I missed this one for a while... On 13/10/05, Frans Pop [EMAIL PROTECTED] wrote: After running ctrlproxy for a fairly long time as daemon: Mem: 30180 29248932 0 1336 5596 -/+ buffers/cache: 22316 7864 Swap:60440 60440 0 After killing ctrlproxy and starting it again: total used free sharedbuffers cached Mem: 30180 17168 13012 0 1508 7412 -/+ buffers/cache: 8248 21932 Swap:60440 3576 56864 Ouch, that's pretty painful indeed. I had similar problems, it's one of the reasons I stopped using ctrlproxy for now. I just talked to the author, he says the code currently in SVN is not suitable for packaging yet. The only thing you can do for now is disable the linestack module, it's the main problem. But without that module, ctrlproxy isn't really useful... :-( Wilmer van der Gaast.
