Bug#821112: crash with assertion failed

Package: liquidsoap Version: 1.1.1-7+b1 Severity: grave Liquidsoap crashes after a while here. It ran for 21 hours before exiting with this series of errors: 2016/04/15 12:16:10 [mp3:3] Finished with "/srv/mp3/Doors/American Prayer/04-Newborn Awakening.mp3". 2016/04/15 12:16:10 [stderr:3]

Bug#821040: fails with "can't open connector"

Package: darkice Version: 1.2-0.2 Severity: grave I can't use darkice at all. It's been a long time since i tried it out, so maybe I am really rusty, but it just doesn't work here. $ sudo darkice -v10 -c ~/.darkice.cfg DarkIce 1.2 live audio streamer, http://code.google.com/p/darkice/ Copyright

Bug#807735: gmpc-plugins: FTBFS: libmpd-internal.h:210:10: error: expected identifier or '(' before '__extension__'

Actually, more than jamendo is affected, so I needed to turn off a bunch more stuff: diff --git a/debian/rules b/debian/rules index 5797a8a..470ceb8 100755 --- a/debian/rules +++ b/debian/rules @@ -9,7 +9,12 @@ DEB_DH_STRIP_ARGS:=--dbg-package=$(DBG_NAME) dh $@ --with autoreconf

Bug#807735: NMU for gmpc-plugins

Hi! I have two bugs (in CC) that I would like to see fixed in gmpc-plugins. Since there hasn't been an upload for a long time in the package, i figured you wouldn't mind! But just in case, I'll give you a few days to review the patches in case you want to interject, then I will upload the

Bug#818590: [pkg-otr-team] Bug#818590: irssi-plugin-otr: mismatching ABI version with current irssi

On 2016-03-18 21:34:43, Andreas Beckmann wrote: > On Fri, 18 Mar 2016 16:09:45 +0100 intrigeri wrote: >> Someone (who can first verify that this would fix the problem) should >> get a binNMU scheduled, I guess :) > > While this would probably make the package installable

Bug#818590: [pkg-otr-team] Bug#818590: irssi-plugin-otr: mismatching ABI version with current irssi

On 2016-03-28 18:37:18, micah wrote: > Antoine Beaupré <anar...@debian.org> writes: > >> On 2016-03-27 15:40:23, micah wrote: >>> Antoine Beaupré <anar...@debian.org> writes: >>> >>>> But before anyone starts working on this now -

Bug#818590: [pkg-otr-team] Bug#818590: irssi-plugin-otr: mismatching ABI version with current irssi

On 2016-03-27 15:40:23, micah wrote: > Antoine Beaupré <anar...@debian.org> writes: > >> But before anyone starts working on this now - i have what i think is a >> working package now here: >> >> http://paste.anarc.at/otr/ >> >> It's been tested by

Bug#818590: [pkg-otr-team] Bug#818590: irssi-plugin-otr: mismatching ABI version with current irssi

On 2016-03-26 07:31:46, intrigeri wrote: > Hi, > > Andreas Beckmann wrote (19 Mar 2016 01:34:43 GMT) : >> On Fri, 18 Mar 2016 16:09:45 +0100 intrigeri wrote: >>> Someone (who can first verify that this would fix the problem) should >>> get a binNMU scheduled, I guess :) > >>

Bug#817172: [pkg-otr-team] Bug#818590: irssi-plugin-otr: mismatching ABI version with current irssi

I have built a new package for 1.0.1 that should fix some of the issues mentionned here, and it is available for testing here: http://paste.anarc.at/otr/ the changes file is signed with my pgp key and should be used to authenticate the package. unfortunately, i can't test the peculiar

Bug#742347: overview of the tilemill situation and alternatives (mapbox, kosmtik)

so I am not sure this RFP is still relevant anymore. there hasn't been a tilemill release since 2012. here's a summary of a discussion that happened in #742347 (for some reason, I sent the discussion there... sorry). 1. Mapbox people have released a new product in september 2014 named

Bug#809136: borgbackup: Mention API incompatibilities in README

On 2016-01-14 04:53:31, Danny Edel wrote: > Hi Antoine, > > On 01/13/2016 07:50 PM, anar...@debian.org wrote: >> The readme is not quite accurate: *some* borg versions are actually >> compatible across the network. It's only on the 0.29 boundary that there >> is a problem. > > Is this[1] wording

Bug#810721: pepper: Package does not contain any binaries

On 2016-01-11 10:20:50, Michael A Bosse' wrote: > Package: pepper > Version: 0.3.3-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Today I ran apt install pepper, and the package installed as expected. I > looked > on system for the binary but did not find

Bug#809136: Block borgbackup migration to stable for now

On 2016-01-09 05:24:41, Danny Edel wrote: > Hello Antoine, > > thank you for your detailed answer. I will try to address inline. > > On 01/08/2016 10:45 PM, Antoine Beaupré wrote: >> Borg has actually shown great API stability since it forked from >> Attic. The change

Bug#809136: Block borgbackup migration to stable for now

On 2016-01-09 05:43:57, Gianfranco Costamagna wrote: [...] >>Furthermore, it's very likely that borg 1.0 gets released before >>stretch, so all those arguments will be completely irrelevant because >>borg *will* be API stable. > > this would fix the issue once for all To be fair, while this

Bug#809136: Block borgbackup migration to stable for now

On 2016-01-09 05:49:36, Gianfranco Costamagna wrote: > BTW Antoine, > > > would you consider joining the packaging team? A DD, user, and upstream > developer > is so much appreciated :) regarding that, i consider myself as part of the team, already, in a way. :p I have participated in the WNPP

Bug#809136: Block borgbackup migration to stable for now

Source: borgbackup Followup-For: Bug #809136 [TL;DR: keep borg in testing. let it be released with stable when streth gets released. use backports to ensure compatibility works across debian releases, if necessary (and it is not, right now!).] Both as a user and developer of borg backup, I

Bug#809359: redmine is outdated in Debian

Source: redmine Severity: grave It seems Redmine Debian package is seriously outdated in Debian. It shouldn't be shipped as such into Stretch, in my opinion, as it does not seem to follow any upstream stable branch (2.6, 3.0, or 3.1). I am also puzzled as to why this was shipped in Jessie in the

Bug#809359: long-term redmine debian packaging

Hi! ["out of date redmine" bug report in CC. this is a followup email to the generic "we're going to LTS redmine!" notification which expands on the situation and hopefully the future of the Redmine packaging] I am trying to figure out how to maintain Redmine in the long term, especially in the

Bug#806377: fails to build jessie image

On 2015-12-03 23:56:51, Jameson Graef Rollins wrote: > On Thu, Nov 26 2015, Antoine Beaupré <anar...@debian.org> wrote: >> Package: debirf >> Version: 0.34 >> Severity: grave >> >> I can't seem to build a jessie image with debirf: >> >>

Bug#806377: fails to build jessie image

Package: debirf Version: 0.34 Severity: grave I can't seem to build a jessie image with debirf: W: See /home/anarcat/debirf/rescue/root/debootstrap/debootstrap.log for details (possibly the package systemd is at fault) The error seems to be: Setting up systemd (215-17+deb8u2) ... Initializing

Bug#742347: [Pkg-javascript-devel] Bug#742347: tilemill vs mapbox studio?

On 2015-11-05 09:52:19, Bas Couwenberg wrote: > The openstreetmap-carto developers have mostly switched to kosmtic: > > https://github.com/kosmtik/kosmtik is that a fork of tilemill? how does it differ? maybe a new ITP should be opened for this then? -- C'est avec les pierres de la loi qu'on a

Bug#742347: tilemill vs mapbox studio?

This are moving fast out there. Mapbox folks have released a new product in september 2014 named "Mapbox studio classic": https://www.mapbox.com/mapbox-studio-classic/#linux The code is still free: https://github.com/mapbox/mapbox-studio-classic It seems to be a fork of tilemill:

Bug#795343: zotero-standalone: Package stopped working after iceweasel upgrade.

Package: zotero-standalone Version: 4.0.22-1 Followup-For: Bug #795343 Control: fixed 795343 4.0.26.2-1 I confirm the same problem here. As far as I can tell, this happened after the Jessie upgrade (from Wheezy), since I don't use Zotero very often. *But* it's possible that zotero worked on

Bug#796466: pepper: FTBFS: error: ‘svn_sort__hash’ was not declared in this scope

Not sure how to fix this: it seems that pepper uses private declarations that have been removed from libsvn in 1.9... We would need to report this upstream, but their tracker is down: http://sourceforge.net/tracker/?group_id=386093 I have therefore put the Pepper author in CC in the hope we will

Bug#796466: pepper: FTBFS: error: ‘svn_sort__hash’ was not declared in this scope

This was fixed in pysvn by rewriting that code, which seems pretty amazing, but could be considered a canonical way. http://pysvn.tigris.org/source/browse/pysvn/trunk/pysvn/Extension/Source/pysvn_client_cmd_info.cpp?r1=1601r2=1600pathrev=1601 And I *think* this is how it was fixed in kdevelop:

Bug#784041: exceptions.OSError: [Errno 2] No such file or directory

Package: torbrowser-launcher Version: 0.1.9-1+deb8u1 Followup-For: Bug #784041 Confirmed. The bug is still present in Debian 8.1. A. -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2

Bug#788749: tty-clock: FTBFS: undefined reference to `delscreen'

On 2015-07-15 11:08:52, Axel Beckert wrote: Antoine: Do you want me to NMU this? I see there is already a 2.1 package in your git repository which seem to fix this, too, just differently: https://redmine.koumbit.net/projects/tty-clock/repository/revisions/debian/entry/debian/changelog But I

Bug#792485: etckeeper/git sets SSH host key perms to 644

Hi, Thanks for the bug report. Normally, such bugs should be reported to secur...@debian.org with the package maintainer in CC instead of in a public bug tracker, but let's deal with it now that it's public... I can confirm the bug: doing a checkout or a reset exposes private files in `/etc` to

Bug#792485: etckeeper/git sets SSH host key perms to 644

Control: tags -1 -security Control: severity -1 normal Actually, looking back at this, this is not a vulnerability directly with etckeeper, or at least, nothing that wasn't already clearly explained in the README. To quote it: ## security warnings First, a big warning: By checking /etc into

Bug#779613: no such file or directory trying to connect through the blueman-applet

On 2015-03-04 02:20:45, Christopher Schramm wrote: Anyway, connecting to a NAP should work. You just have to select the service from the device menu and not use the generic connect item for that. There's no service from the menu, in fact, the Serial server menu item is gone. So you are

Bug#779613: no such file or directory trying to connect through the blueman-applet

On 2015-03-03 01:57:24, Christopher Schramm wrote: Hi Antoine, unfortunately BlueZ 5's generic connect method is a misconception in my eyes as in your case it will not connect the NAP service. In the current upstream master you will not get a generic connect item in the menu anymore, but see

Bug#779613: no such file or directory trying to connect through the blueman-applet

Package: blueman Version: 1.99~alpha1-1 Severity: grave Since I upgraded this laptop to jessie, I cannot use Blueman to connect to the internet by tethering to my phone. I think this is an upstream bug described here: https://github.com/blueman-project/blueman/issues/161 In the GUI, I see No

Bug#778695: wheezy - jessie: no gdm3 prompt, dependency loops and broken initrd

Package: upgrade-reports Severity: grave This is the third jessie upgrade I perform from jessie. The previous one was documented in #774314. It seems that the dependency loop problems are still there, and there were so many problems with the upgrade that I don't believe it would be right to

Bug#774316: fails to upgrade to jessie with cannot add entry with empty dn

Package: slapd Version: 2.4.40-3 Severity: grave This package cannot be upgaded to jessie: Paramétrage de slapd (2.4.40-3) ... Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.31-1+nmu2... done. Moving old database directories to /var/backups: Loading from

Bug#773321: [pkg-otr-team] Bug#773321: Bug#773321: irssi-plugin-otr segfaults unexpectedly

On 2014-12-16 18:53:54, Holger Levsen wrote: On Mittwoch, 17. Dezember 2014, Antoine Beaupré wrote: i can reproduce this without the xmpp warning. which versions of irssi and irssi-plugin-otr do you use? ii irssi 0.8.17-1~bpo70+1

Bug#773321: irssi-plugin-otr segfaults unexpectedly

Package: irssi-plugin-otr Version: 1.0.0-1~bpo70+1+b2 Severity: critical the otr plugin is severly damaged, both in jessie and wheezy-backports. in wheezy, irssi completely crashes after i /load otr. this is even without the xmpp plugin loaded, so it's different from #499229.

Bug#773321: [pkg-otr-team] Bug#773321: irssi-plugin-otr segfaults unexpectedly

On 2014-12-16 18:10:04, Holger Levsen wrote: control: tags -1 + moreinfo Hi Antoine, On Dienstag, 16. Dezember 2014, Antoine Beaupré wrote: Severity: critical the otr plugin is severly damaged, both in jessie and wheezy-backports. in wheezy, irssi completely crashes after i /load otr

Bug#770900: monkeysign: 'MonkeysignScan' object has no attribute 'dialog'

On 2014-11-26 14:21:02, Daniel Kahn Gillmor wrote: On 11/25/2014 10:44 PM, Antoine Beaupré wrote: It seems you have stumbled upon a dusty path in the GTK UI that is neither unit tested or often used by graphical users. I believe you may be attempting to sign a key that is already in your local

Bug#770900: monkeysign: 'MonkeysignScan' object has no attribute 'dialog'

On 2014-11-26 16:20:23, Daniel Kahn Gillmor wrote: On 11/26/2014 04:15 PM, Antoine Beaupré wrote: On 2014-11-26 14:21:02, Daniel Kahn Gillmor wrote: The monkeyscan main window freezes and an strace reveals that the process is stuck in a futex() call. So i don't think this is resolved for me

Bug#771032: monkeysign: Crash due to encoding error

On 2014-11-25 22:42:01, Antoine Beaupré wrote: Control: tags -1 +patch I believe the attached patch will fix the problem. From 330a9e6cbdd04475cea53122e12496f4e99e0104 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= anar...@koumbit.org Date: Tue, 25 Nov 2014 22:29:12 -0500

Bug#771032: monkeysign: Crash due to encoding error

Control: tags -1 +patch I believe the attached patch will fix the problem. From 330a9e6cbdd04475cea53122e12496f4e99e0104 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= anar...@koumbit.org Date: Tue, 25 Nov 2014 22:29:12 -0500 Subject: [PATCH] try to handle error when import

Bug#771034: monkeysign: Attempts to sign wrong uid

Control: tags -1 +patch Thanks again for the bug report! Pretty amazing that no one noticed this major bug before... I have fixed this in git, with the following patch. commit e2ddadcf643fd42a749c16cb9664a6fd3d5b76e1 Author: Antoine Beaupré anar...@koumbit.org Date: Tue Nov 25 23:26:00 2014

Bug#770104: seivot completely fails with cannot run genbackupdata: No such file or directory

Package: seivot Version: 1.17-1 Severity: grave Seivot, as packaged in Debian, simply doesn't run: anarcat@marcos:~$ seivot /usr/bin/time: cannot run genbackupdata: No such file or directory ERROR: command failed: ['genbackupdata', '/tmp/tmpiWI_PW/data', '--create', '1024', '--file-size',

Bug#770104: seivot completely fails

Control: retitle -1 seivot completely fails In fact, there's more to it than this: anarcat@marcos:seivot$ ./seivot --log=foo.log --log-level=debug \ --initial-data=1m --incremental-data=1m --generations=2 \ --output=foo.seivot Generating: 976.6 KiB of 976.6 KiB 100 % (92.36

Bug#762796: [Packaging] Bug#762796: munin: Undefined subroutine main::header

On 2014-10-14 05:54:57, Holger Levsen wrote: control: tags -1 + pending Hi, fixed in git by Steve, thanks! 2.0.22-1 should arrive soon... Any idea when 2.0.22 will be released? It doesn't seem to be shipped even upstream... In my mind, this should be fixed in jessie at least... a. --

Bug#764011: fails to capture with Unexpected short read from authority file

Package: shutter Version: 0.92-0.1 Severity: grave Shutter now fails to perform simple screenshots in Jessie. Here's an example of this problem: ``` anarcat@marcos:~$ shutter -s defined(@array) is deprecated at /usr/bin/shutter line 3727. (Maybe you should just omit the defined()?)

Bug#764011: more details

found 764011 0.90.1-0.1 found 764011 0.88.3-1 severity 764011 normal thanks Well, that's a PITA: older versions also behave similarly. Interestingly, moving away my .shutter directory fixes the problem. so i guess that's not something that deserves grave severity... I have been able to isolate

Bug#609537: /etc/init.d/mysql stop leaves a process but exits with 0 status

found 609537 5.5.38-0+wheezy1 thanks I have found this bug happening even on wheezy, on a server that doesn't exit immediately after a mysladmin shutdown. I find that the expectation of the shutdown procedure of Debian's initscript is a little unreasonable: it issues a shutdown command, and if

Bug#724471: Bug#707225: smokeping: patch for bugs #707225, #724471 and #752393

On 2014-06-23 10:11:20, Rowan Thorpe wrote: I've attached an updated diff based on the below feedback. Because the changes only affect this bug I won't update the diff on the other two bugs until this version is confirmed good. On 14:20 Mon 23 Jun 2014, Niko Tyni wrote: On Mon, Jun 23, 2014

Bug#738493: LWPx::ParanoidAgent still broken

Control: reopen -1 Control: notfixed -1 1.10-2 This is still broken: anarcat@marcos:~$ dpkg -l liblwpx-paranoidagent-perl Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements |/

Bug#738493: bumped severity

Control: severity -1 critical I bumped the severity of this bug because it basically breaks all the authentication of TLS certificates in Perl, so it affects other software (for example Ikiwiki): http://ikiwiki.info/bugs/openid_login_fails_wirth_Could_not_determine_ID_provider_from_URL/ See

Bug#745570: fails to display

On 2014-04-23 03:37:44, Tomasz Buchert wrote: Your problem has probably something to do with: Failed to initialize the OpenGL 2 renderer, falling back to the OpenGL 1 renderer So: 1) does your OpenGL work in general (try glxgears) okay, so glxgears fails in a similar way here. 2) did

Bug#745570: fails to display

Package: stellarium Version: 0.12.4-1 Severity: grave Stellarium just doesn't startup. A window pops up, but it is blank and just sits there doing nothing. -s or -f no do not help. anarcat@marcos:~$ stellarium -s Using default graphics system specified at build time: raster User config

Bug#743148: borken symlink

Package: node-tilelive-mapnik Version: 0.6.1-1 Severity: grave This package is basically unusable. While trying to package tilemill, I was trying to load this library, and got this: Error: Cannot find module 'tilelive-mapnik' The reason for this is this broken symlink:

Bug#743151: two more missing modules (htmlparser2 and nwmatcher)

Package: node-jsdom Version: 0.8.10+dfsg1-1 Severity: grave In addition to cssstyle (#742347), there are two more modules missing for this nodejs module to work: nwmatcher and htmlparser2. The latter is especially fun: htmlparser2@3.7.1 /usr/lib/node_modules/htmlparser2 +-- domelementtype@1.1.1

Bug#743148: [Pkg-javascript-devel] Bug#743148: borken symlink

On 2014-03-30 18:59:19, Jérémy Lal wrote: Le dimanche 30 mars 2014 à 18:46 -0400, Antoine Beaupré a écrit : Package: node-tilelive-mapnik Version: 0.6.1-1 Severity: grave This package is basically unusable. While trying to package tilemill, I was trying to load this library, and got

Bug#726370: gphoto2: Nikon D300, Darktable hangs and Dolphin shows error code 150.

On 2014-03-09 08:22:03, Laurent Bigonville wrote: Hello Antoine, Thanks for the feedback. Did you also saw the dataloss that the initial reporter is mentioning? I'm not sure i followed that part of the initial report, but i did not see dataloss - merely that I sometimes have trouble

Bug#726370: gphoto2: Nikon D300, Darktable hangs and Dolphin shows error code 150.

On 2014-03-09 13:22:28, Laurent Bigonville wrote: [...] I've quickly discussed with upstream and told me you probably should check the following things: [...] 2) Run gphoto2 -L --debug --debug-logfile=xx.log to have some debug logs. If you could also attach the logs to the bug that would

Bug#726370: gphoto2: Nikon D300, Darktable hangs and Dolphin shows error code 150.

Package: gphoto2 Version: 2.4.14-1 Followup-For: Bug #726370 Control: tags -1 - moreinfo Control: found -1 2.5.3.1-1 Control: affects -1 libgphoto2-6 The problem is not actually with the gphoto2 binary package, but with the library, which is what darktable really uses. Case in point: i purged

Bug#735898: pavucontrol segmentation fault

On 2014-03-04 16:08:15, Léo Cavaillé wrote: The patch is on pavucontrol debian git, and I finished the packaging of 2.0 version today, tomorrow I will upload pavucontrol 2.0-1 to the archive. That's great, thanks! Do you want me to remove the upload from DELAYED/2? It should be overriden by

Bug#735898: pavucontrol segmentation fault

Package: pavucontrol Followup-For: Bug #735898 Control: tags -1 pending I'll upload this patch shortly (NMU, 2 days delay), since it seems to fix the problem and pavucontrol is threatened by autoremoval. Cheers, A. -- System Information: Debian Release: jessie/sid APT prefers testing APT

Bug#724471: smokeping: FTBFS: configure.ac:24: error: required file 'conftools/compile' not found

On 2014-02-14 05:42:16, Niko Tyni wrote: On Tue, Sep 24, 2013 at 08:50:59AM +0300, Damyan Ivanov wrote: Package: src:smokeping Version: 2.6.8-2 Severity: serious Justification: FTBFS smokeping fails to build in a clean current sid pbuilder chroot: make[1]: Entering directory

Bug#737494: fails to upgrade from wheezy to jessie

debug info - i set monkeysphere debugging and enabled tracing in the postinst: anarcat@marcos:~$ sudo env MONKEYSPHERE_LOG_LEVEL=DEBUG apt-get install Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait 0 mis à jour, 0 nouvellement

Bug#724077: charybdis: FTBFS: configure.ac:18: error:, required file './compile' not found

On 2014-02-01 11:50:11, Andreas Moog wrote: On Tue, 15 Oct 2013 21:52:47 -0400, Antoine Beaupre anar...@orangeseeds.org wrote: Control: tags -1 +pending Sure, upload coming rght up, thanks!! A. ping? ;) Totally forgot, sorry! I'll upload soon. A. -- Voter, c'est abdiquer

Bug#737494: fails to upgrade from wheezy to jessie

Package: monkeysphere Version: 0.36-1 Severity: serious I couldn't upgrade this package from wheezy to jessie, because of this error: Setting up monkeysphere (0.36-1) ... gpg: can't open `/var/lib/monkeysphere/authentication/sphere/pubring.gpg' gpg: keydb_get_keyblock failed: eof gpg: no

Bug#737496: upgrade to jessie hoses notmuch-emacs

Package: notmuch Version: 0.17-3 Severity: serious It seems that upgrading from wheezy to jessie has mostly destroyed my capability of using notmuch in emacs. My workflow was simply to call M-x notmuch after starting emacs. I load notmuch as follows, from my .emacs: (safe-require 'notmuch)

Bug#737496: upgrade to jessie hoses notmuch-emacs

Control: severity -1 normal So it turns out I had a newline in my `notmuch-saved-searches', which didn't matter before the upgrade but crashed latest notmuch version. A bit of a WTF, but recoverable. Not sure how to deal with this, but I'll at least downgrade severity. A. pgpDAVUagfVPJ.pgp

Bug#727044: Could not load plugin

Package: liquidsoap-plugin-gstreamer Version: 1.0.1+repack1-1.1 Severity: grave This plugin doesn't work at all in wheezy: anarcat@marcos:src$ liquidsoap 'out(input.gstreamer.audio(pipeline=udpsrc multicast-group=224.0.0.56 port=5004 ! \application/x-rtp, media=(string)audio, clock-rate=44100,

Bug#724077: charybdis: FTBFS: configure.ac:18: error: required file './compile' not found

Control: tags -1 +pending Sure, upload coming rght up, thanks!! A. On 2013-10-15 08:06:33, Hideki Yamane wrote: Control: tags -1 +patch Hi, Attached patch would fix this FTBFS, could you consider to apply it, please? -- The idea that Bill Gates has appeared like a knight in

Bug#711071: still relevant

Control: found -1 3.2-1.2 As I said, I think this issue should stay opened. If I understand transitions properly, once the build bots pass, this issue will become irrelevant to the transition anyways. *And*, once the libotr5 bitlbee code hits debian, if it fails then we'll have this issue to

Bug#717622: found fix

Control: severity -1 normal Control: tags -1 +pending I have found a fix. The situation was that the public key was unusable for encryption, as it was expired. Refreshing the key fixed the problem, so this is purely a usability issue. I have fixed the error handling in git, this will be part of

Bug#717622: crashes when sending email

[expiry: 1464748981] Fingerprint = 8DC9 01CE 6414 6C04 8AD5 0FBB 7921 5252 7B75 921E uid 1 [unknown] Antoine Beaupré (home address) anar...@anarcat.ath.cx uid 2 [unknown] Antoine Beaupré (work) anar...@koumbit.org uid 3 [unknown] Antoine Beaupré anar...@orangeseeds.org uid 4

Bug#717622: more info

I have started working on unit tests for this and made some refactoring to allow unit tests to cover mail generation more thoroughly, but so far no luck. Note that the key I am trying to sign already has a non-exportable (-l local) signature, this may be the root of the problem here. -- The

Bug#701744: fix also confirmed here

We have two machines that are identical here. I had the bug reproduced fairly reliably on both machines regularly, last week it happened exactly at the same time. I installed the squeeze4~ijc0 kernel on one of them this weekend, and today only the one without the kernel failed. In other words,

Bug#701438: working on this

Control: block -1 by 711152 Hi, I am working on porting the new upstream stable release to sid. It is proving to be more difficult than i thought, and I opened several issues with upstream: https://github.com/atheme/charybdis/issues/created_by/anarcat?state=open 4 out of those are patched in

Bug#705000: cryptsetup now says: evms_activate is not available

Package: dmsetup Version: 2:1.02.74-7 Severity: grave On my last reboot of my wheezy server, the crypto drives cannot be mounted properly by the initramfs. I am not sure dmsetup is the culprit, but cryptsetup didn't seem to have change since the last reboot, so I am tempted to blame this on

Bug#659390: bug#670232

Hi Ana, and others, I will not have time to process this bug in the next two weeks, feel free to NMU or RM. A. -- Evil exists to glorify the good. Evil is negative good. It is a relative term. Evil can be transmuted into good. What is evil to one at one time, becomes good at another time to

Bug#703274: why the epoch update on file?

On 2013-03-18, Adam D. Barratt wrote: On 18.03.2013 03:57, Antoine Beaupré wrote: Why did this upload have to bump the epoch number up? It seems to me a 5.11-2.1, or -2.2 upload would have been fine here. Unstable already had 5.12-2, so a new upload as 5.11 would have been rejected

Bug#703274: why the epoch update on file?

Why did this upload have to bump the epoch number up? It seems to me a 5.11-2.1, or -2.2 upload would have been fine here. A. -- Modern man has a kind of poverty of the spirit which stands in great contrast to his remarkable scientific and technological achievements. We've learned to walk in

Bug#700738: downgrading severity to unblock wheezy

Control: severity -1 important So it seems we don't have a clear solution here. But more importantly, I do not believe the bugs described here are serious enough to block the wheezy release (as they are doing now) or provoke a removal of the package from the archive (as they could mean).

Bug#659899: CVE-2012-0790: XSS

Control: found -1 2.6.7-1 Control: fixed -1 2.6.9-1~exp0 Control: fixed -1 2.3.6-5+squeeze1 Control: tags -1 pending Control: block -1 with 703193 On 2013-03-16, Salvatore Bonaccorso wrote: Control: fixed -1 2.6.7-1 Hi Steven On Sat, Mar 16, 2013 at 12:40:04PM +, Steven Chamberlain

Bug#659899: CVE-2012-0790: XSS

On 2013-03-16, Steven Chamberlain wrote: Another difference is that upstream 2.6.9 used a replacement character of underscore rather than a dot. Attached is my suggested revision of Salvatore's patch (also adds filtering of time specifiers). I've tested this on an existing wheezy/sid

Bug#700738: valgrind summary

On 2013-03-08, Sebastian Ramacher wrote: On 2013-03-06 20:02:16, Antoine Beaupré wrote: So I ran the patched version under valgrind, which I am not familiar with at all so YMMV. I attach the output. Basically, what I see is one of those: ==3852== Conditional jump or move depends

Bug#700738: valgrind summary

details of leaked memory ==3852== ==3852== For counts of detected and suppressed errors, rerun with: -v ==3852== Use --track-origins=yes to see where uninitialised values come from ==3852== ERROR SUMMARY: 375 errors from 50 contexts (suppressed: 4 from 4) -- Antoine Beaupré +++ Réseau Koumbit Networks

Bug#700738: one patch, but plenty more needed

On 2013-03-04, gregor herrmann wrote: On Sun, 03 Mar 2013 10:30:21 -0400, David Bremner wrote: The use-after-frees are quite trivial to fix There's a package on mentors now: http://mentors.debian.net/package/tty-clock https://lists.debian.org/debian-mentors/2013/03/msg00069.html So that

Bug#698813: Too many levels of symbolic links on upgrade

On 2013-01-23, Rob Browning wrote: Antoine Beaupré anar...@koumbit.org writes: anarcat@angela:~$ ls -ald /etc/emacs* drwxr-xr-x 3 root root 4096 jan 22 19:16 /etc/emacs lrwxrwxrwx 1 root root 11 oct 3 10:43 /etc/emacs23 - /etc/emacs/ So yeah, this is a symlink pointing to itself

Bug#698813: Too many levels of symbolic links on upgrade

Package: emacsen-common Version: 2.0.5 Severity: grave I get this trying to upgrade from 2.0.3 to 2.0.5: Setting up emacsen-common (2.0.5) ... Install emacsen-common for emacs23 emacsen-common: Handling install of emacsen flavor emacs23 Error occurred processing

Bug#698024: how is this done?

On 2013-01-16, Daniel Baumann wrote: On 01/16/2013 06:47 AM, Antoine Beaupré wrote: I don't understand why this bug report was closed. as indicated when closing the bug, it doesn't serve any purpose. I thought it did: to make sure that the wheezy version was stable. I don't understand how

Bug#698024: how is this done?

On 2013-01-16, Daniel Baumann wrote: On 01/16/2013 01:40 PM, Antoine Beaupré wrote: You may still want to use this patch then: as indicated in my previous mail, this has already been fixed in git together with marking the bug as 'pending'. Ah, I didn't notice that in your previous mail

Bug#698024: how is this done?

I don't understand why this bug report was closed. It was explicitely about having a stable version for wheezy, and the response was to use the version from sid - how does that help with the actual issue? I understand that the sid version fixes issues, and that's great, but I think this issue

Bug#698024: stabilize live-build for wheezy

Package: live-build Version: 3.0~a51-1 Severity: grave There are serious problems with live-build in wheezy. For example, the rescue package list is completely broken (#694823) and there are some problems with grub (#696578). In both bug reports, users are being targeted to the latest 3.x

Bug#697722: NMU uploaded to security

tags 697722 +pending thanks I uploaded a NMU to security-master.debian.org just now. This should be sufficient to fix rails security on squeeze since #697744 / CVE-2013-0155 doesn't affect 2.x. I don't have more time to work on this issue so others will pick up the upload for sid. Thanks to the

Bug#697092: charybdis: CVE-2012-6084: remote denial of service

On 2013-01-02, John Paul Adrian Glaubitz wrote: Hi, attaching proposed debdiff containing the upstream patch as well an updated debian/changelog for an NMU. Would be willing to do the NMU if no one else volunteers. Please do NMU, but the following chunk should be removed from the patch:

Bug#696208: Error downloading: server replied forbidden 202

Package: minitube Version: 1.7-1.1 Severity: grave Minitube doesn't work at all in wheezy. I get the following backtrace: Network error: Error downloading

Bug#696210: no video, only audio

Package: minitube Version: 1.9-1 Severity: grave Pretty much any video I can look at with minitube has no video output. The sound comes in fine and everything seems okay, but there's just no video at all. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500,

Bug#696210: Acknowledgement (no video, only audio)

block 696210 by 681652 thanks This bug was also reported on Ubuntu here: https://bugs.launchpad.net/debian/+source/minitube/+bug/990891 A workaround is: apt-get install phonon-backend-vlc apt-get remove phonon-backend-gstreamer So I guess this may be moved to the gstreamer backend package, as

Bug#692936: No remote address supplied after a while

Package: openvpn-auth-ldap Version: 2.0.3-4 Followup-For: Bug #692936 Hum. It seems that this packaging is failing to build on kfreebsd, and for good reasons: https://buildd.debian.org/status/fetch.php?pkg=openvpn-auth-ldaparch=kfreebsd-amd64ver=2.0.3-4stamp=1352718255 auth-ldap.m:538:4:

Bug#692936: No remote address supplied after a while

Package: openvpn-auth-ldap Version: 2.0.3-1 Severity: grave After using this plugin for a while and seeing a few connexions (from less than 10 clients at a time!), I get this: Nov 10 21:40:25 vpn0 ovpn-public-auth[10087]: No remote address supplied to OpenVPN LDAP Plugin

Bug#692936: No remote address supplied after a while

about this address, we fail only when really necessary. Author: Antoine Beaupré anar...@debian.org Origin: vendor Bug: https://code.google.com/p/openvpn-auth-ldap/issues/detail?id=4 Bug-Debian: http://bugs.debian.org/692936 Forwarded: yes Last-Update: 2012-11-10 --- openvpn-auth-ldap-2.0.3.orig/src

Bug#689522: Lisp directory `/etc/emacs23' does not exist

On 2012-10-27, Axel Beckert wrote: Antoine Beaupré wrote: I started getting this error when using emacs after the latest wheezy upgrade: Warning: Lisp directory `/etc/emacs23' does not exist. I mark this grave as it makes most emacs parts unusable... My .emacs is not loaded, for example

<    1   2   3   4   >