Bug#883872: bitlbee: Extremely incomplete d/copyright

>Side note: Considering that the maintainer of the package has no time >to care for RC bugs in copyright with patch attached the package might >be a good candidate for some force-modernise effort. That's a rather unfair way of phrasing it. I worked closely with wilmer on this issue, and we

Bug#883872: bitlbee: Extremely incomplete d/copyright

I've integrated the NMU and fixed the rest of the issues with the copyright file in the following pull request: https://github.com/bitlbee/bitlbee/pull/127 Please review. >- It implies all of the names listed hold copyright on most files This one is just a side effect of how "decopy", the tool

Bug#895393: tracker.debian.org thinks 3.9.8 is the latest standards version

Package: tracker.debian.org Severity: normal Dear Maintainer, The old package tracker complains that my package is "severely out of date", while the new one thinks it is up to date and doesn't complain about anything. Compare: https://packages.qa.debian.org/b/bitlbee.html

Bug#858136: ITP: bitlbee-facebook -- Facebook chat protocol plugin for BitlBee

On 18 March 2017 at 16:36, Sean Whitton wrote: > I believe that it is necessary to package the latest git snapshot of > this package as older versions cannot connect to Facebook's servers. > Despite this, I consider Facebook's protocol to be stable enough to > include

Bug#854688: bitlbee: The versions in stable/testing are vulnerable to CVE-2016-10189 and CVE-2016-10188

Package: bitlbee Version: 3.4.2-1.1 Severity: grave Tags: upstream security patch fixed-upstream Hi, I'm opening this bug since #853282, which was just fixed by the 3.5.1-1 upload, seems to apply to sid only. CVE-2016-10188 is "bitlbee-libpurple: Use after free when expiring file transfer

Bug#767230: bitlbee-plugin-otr: bitlbee no longer starts: libotr API version 4.1.0 incompatible with actual version 4.0.0

Like wilmer said, This should fix itself when libotr5 4.1 enters testing - that's plan B, except that doing binNMU for reverse deps isn't needed, IMO. API and ABI are still compatible, despite what the OTRL_INIT error may suggest. Everything will just work fine if you let the transition finish

Bug#759932: Actual fix available in upstream bzr

This is marked as fixed because it succeeded to build apparently, but i tested it and still fails for me (clean debian sid VM with systemd) There's an actual fix for this exact issue in upstream bzr, also included in the released 3.2.2 http://bugs.bitlbee.org/bitlbee/changeset/devel,1022/devel/