Bug#803082: [Python-modules-team] Bug#803082: Bug#803082: ipython ftbfs (too new lessc version)

hic > > approach. So maybe you'll see less surprises with this one? > > Julien Puydt (CCed) has been filing a number of ITPs for > ipython/jupyter packages recently, so maybe he's also considering the > transition to ipython 4.0.0. > Yes, definitely. And I think the final dep of I

Bug#800744: setuptools-scm: maintainer address bounces

Hi, Le samedi 03 oct. 2015 à 09:18:25 (+0200), Ansgar Burchardt a écrit : > Source: setuptools-scm > Version: 1.8.0-1 > Tags: sid > Severity: serious > X-Debbugs-Cc: Tristan Seligmann > > [ CC'ed the sponsor. ] > > The maintainer address for setuptools-scm bounces, see

Bug#791251: (no subject)

Hi, I have a 0.4.3-1 in the git repository already. The gcc 5 transition is a rebuild away, since there are no rdeps. Thanks, Snark on #debian-science

Bug#780251: Doesn't work anymore

Package: python-cvxopt Version: 1.1.4-1.2 Severity: grave The package is now unusable, since it uses a symbol (lpx_create_prob) which isn't in glpk anymore -- trying to load the module raises a symbol not found error. Updating to latest upstream would definitely help. If you don't have time

Bug#760193: Should not be shipped in jessie

Package: flintqs Version: 20070817-1 Severity: serious This package is a part of the effort to package sagemath in debian ; before other various pieces are in place, this one has little interest for a stable release. In fact, there is even a good chance that its features will be pushed in

Bug#710635: pynac: FTBFS: ld: cannot find -lz

Hi, Le 21/03/2014 10:19, Tobias Hansen a écrit : Hi Julien, pynac 0.3.1 was released now. Cheers, Tobias I updated the git in something like october when it was released, but I don't remember if it was something ready to RFS or not. I think upstream broke the soname numbering, and

Bug#740097: Workaround?

Hi, I tried to modify the sources by hand and recompile (with make -f debian/rules build then binary), but the module still didn't load with the same error message, so there might be more to fix... Snark on #debian-science -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org

Bug#728361: Bug#729134: [Pkg-systemd-maintainers] Bug#729134: libpam-systemd wreaks havoc

Le 12/11/2013 09:51, Yves-Alexis Perez a écrit : On Tue, 2013-11-12 at 08:08 +0100, Julien Puydt wrote: Notice that you focus on lightdm but that removing libpam-systemd solved other problems. Could you point to those other problems where lightdm was not involved at all? The fact that I

Bug#728361: Bug#729134: [Pkg-systemd-maintainers] Bug#729134: libpam-systemd wreaks havoc

Le 12/11/2013 20:40, Yves-Alexis Perez a écrit : On Tue, 2013-11-12 at 20:37 +0100, Julien Puydt wrote: Le 12/11/2013 09:51, Yves-Alexis Perez a écrit : On Tue, 2013-11-12 at 08:08 +0100, Julien Puydt wrote: Notice that you focus on lightdm but that removing libpam-systemd solved other

Bug#728361: [Pkg-systemd-maintainers] Bug#729134: libpam-systemd wreaks havoc

Le 11/11/2013 23:31, Michael Stapelberg a écrit : Hi Julien, Julien Puydt julien.pu...@laposte.net writes: I was having issues with my computer lately: - I wasn't able to mount USB keys anymore in thunar ; - I wasn't able to shutdown/restart/hibernate anymore in xfce ; - even when logged

Bug#728361: libpam-systemd wreaks havoc

Package: libpam-systemd Version: 204-5 Severity: important I was having issues with my computer lately: - I wasn't able to mount USB keys anymore in thunar ; - I wasn't able to shutdown/restart/hibernate anymore in xfce ; - even when logged out, lightdm didn't allow shutdown/restart/hibernate. I

Bug#710635: Fix for pynac's FTBFS

Hi, thanks for pointing out the upstream patch to fix the issue, but I'm the one who provided it! And pynac upstream was supposed to publish 0.3.1 with the fix at the beginning of july... I'll get 0.3.0+patch pushed into debian soon, since it's starting to get annoying. Snark on #debian-science

Bug#710635: (no subject)

The problem will be fixed in the next release, version 0.3.1 which is due in two or three weeks ; I'll package it as soon as it is available. Snark on #debian-science -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#708517: Acknowledgement (Documentation doesn't build with recent texinfo)

Le 16/05/2013 11:36, Debian Bug Tracking System a écrit : Thank you for filing a new Bug report with Debian. In fact, upstream is aware of the issue already ; since months: https://sourceforge.net/p/maxima/bugs/2551/ Snark on #debian-science -- To UNSUBSCRIBE, email to

Bug#708517: Patch available

I just posted a patch on the upstream bugtracker to fix the problem. Camm, can you include it in your package until upstream pushes it into a new release? I hope it helps, Snark on #debian-science -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of

Bug#675301: license of palp 1.1

The problem has been settled for 2.1 since a few days. See my package page on mentors! Snark on #debian-science and #debian-mentors -- Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté. Bart Martens ba...@debian.org a écrit : Hello Harald, Please read the following

Bug#614175: Can't run after install

Package: prosody Version: 0.7.0-1 Severity: grave apt-get install prosody leads to : * Starting Prosody XMPP Server prosody ** A problem occured while reading the config file /etc/prosody/prosody.cfg.lua Error: /usr/share/lua/5.1/prosody/util/ztact.lua:34: bad

Bug#614175: Can't run after install

Hi, Le 20/02/2011 10:19, Matthew Wild a écrit : What is the output of `ls -la /etc/prosody` ? # ls -al /etc/prosody/ total 28 drwxr-xr-x 5 root root 83 20 févr. 10:30 . drwxr-xr-x 177 root root12288 20 févr. 10:30 .. drwxr-x--- 2 root prosody47 20 févr. 10:30 certs

Bug#521586: closed by m...@linux.it (Marco d'Itri) (Re: Bug#521586: Simple error in a rules file can make a system unbootable from disk)

Debian Bug Tracking System a écrit : This is an automatic notification regarding your Bug report which was filed against the udev package: #521586: Simple error in a rules file can make a system unbootable from disk It has been closed by m...@linux.it (Marco d'Itri). Their explanation is

Bug#521586: Simple error in a rules file can make a system unbootable from disk

Package: udev Version: 0.140-1 Severity: critical A simple label error in a rules file can make a system unbootable : at the head of a file in /etc/udev/rules.d, there was a (conditional) goto to an 'end' label ; but at the end of the file, the label was 'begin', so there was no 'end' label

Bug#453615: It's better now... but still useless

Hi, latest upload of 0.9.46-1 made the bus error issue go away. Unfortunately, the texts appear as symbols, as shown in the attached screenshot of winecfg... so it's still unusable :-/ Snark on #gnome-hackers inline: Screenshot.png

Bug#453615: Bus error

Package: wine Version: 0.9.45-1 Severity: grave Running winecfg or wine always gives the same error : /usr/bin/wine: line 396: 13812 Bus error $WINEBIN/$WINE_BIN_NAME $@ Setting severity to grave, since it makes the package unusable. Snark on #gnome-hackers -- To UNSUBSCRIBE, email to

Bug#439923: There's an easy fix!

Hi, I just installed debian/unstable on a new box and was hit by that bug. Rebuilding the texmacs package was enough to fix the issue. So that means uploading a newly-compiled texmacs package would close the bug. JP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of

Bug#390133: Here is a gdb backtrace

Hi, I have crashing issues, hopefully related. I checked the binary pid with ps -ef, then attached gdb and asked for the bt : #0 0xa717737f in osl_incrementInterlockedCount () from /usr/lib/openoffice/program/libuno_sal.so.3 #1 0xa7192d12 in rtl_uString_assign () from

Bug#296122: Muine package needs gstreamer0.8-gnomevfs

Package: muine Version: 0.6.3-6 Severity: grave Muine's package installs just fine, but won't run because it doesn't find gnomevfs support in gstreamer. Installing the gstreamer0.8-gnomevfs package solves it. Setting severity to grave since that means the package is unusable by default. Thanks,

<    1   2   3