Hi Sandro,
On 9 September 2012 13:18, Sandro Tosi wrote:
> Hello Xavier,
> [...]
> That seems like the pager you have had some problems; what is the
> pager you use? it's either $PAGER or the one launched by
> sensible-pager.
>
My $PAGER variable is unset and sensible-pager points to less. I b
Hi Sandro,
On 10 September 2012 20:48, Sandro Tosi wrote:
> On Mon, Sep 10, 2012 at 8:31 PM, Xavier Lüthi wrote:
> > My $PAGER variable is unset and sensible-pager points to less. I
> believe it
> > is a classical configuration.
>
> yes indeed, can you replicate it or
Package: cairo-dock
Version: 3.4.0-1
Followup-For: Bug #744693
This bug is still present with the current version in sid.
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores
found 285360 1.9.36.3+nmu1
tags 285360 +confirmed
thanks
It seems this old bug is still present in the latest version of
apt-proxy. Here is my log confirming it:
[EMAIL PROTECTED] ~/debian]$ ls -l apt-proxy/
total 2952
-rw-r--r-- 1 xavier xavier 3017514 2008-10-26 15:23
aptitude_0.4.11.10-1len
tags 314738 +wontfix
thanks
As this bug imply the migration from one very old version of apt-proxy
(even no more present in the oldstable distrib), I think this bug won't
be fixed anymore.
By the way, do we have to keep it opened?
Cheers,
Xavier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
tags 432221 +unreproducible
Hi,
With the current version of apt-proxy (1.9.36.3+nmu1), I cannot
reproduce your bug. In fact, if I'm setting an IP address not linked
to my machine, apt-proxy does not start: I do not see any clear message
on the console, but it's quite clear in apt-proxy.log:
200
ROTECTED]>
> On Fri, Sep 05, 2008 at 04:56:27PM +0200, Xavier Lüthi wrote:
> > I cannot find your patch attached to your email. Can you please
> > send it as I want might be interested in reviewing it!
>
> There it is...
>
> --Cheers,
>
> --Seb
>
Hi Seb,
I cannot find your patch attached to your email. Can you please send it as
I want might be interested in reviewing it!
Thanks,
Xavier
Hi all,
Sorry for not responding sooner to your emails.
I'm not using b2evolution anymore, thus explaining my lack of
responsiveness.
Anyway, I'm ready to package a new version of b2evolution for Debian.
Currently, two upstream versions are available:
- 1.10.3 dated from 2007-11-01 and which
Hi,
Le Wed, 27 Jan 2010 22:43:31 +0100,
"Francesco P. Lovergine" a écrit :
> severity 460338 grave
> thanks
>
I agree to raise the severity of this bug as it renders the package
unusable.
> I finally removed today apt-proxy in my work LAN because this hanging
> onto update is a too common p
Hi Arnaud,
On 10/03/2008, Arnaud Guiton <[EMAIL PROTECTED]> wrote:
>
> Xavier wrote:
>
> > Hi all,
>
> Hi!
>
>
>
> > Currently, two upstream versions are available:
> >
> > - 1.10.3 dated from 2007-11-01 and which is a stable version.
> > - 2.4.0 dated from 2008-01-23 and which is a RC4 version
On Fri, 27 Nov 2009 06:40:43 +0100
Ralf Treinen wrote:
> Package: exaile,pixelpost
> Version: exaile/0.2.14+debian-2.1
> Version: pixelpost/1.7.1-6
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-file-overwrite
>
> Date: 2009-11-26
> Architecture: amd64
> Distribution: sid
>
> H
reopen 555244
thanks
Hi,
The patch to solve this bug is not correct. Insteand of linking
towards prototype.js from libjs-prototype package, it links towards a
file from the pixelpost package (see bug #558219 for details).
I'm thus reopening this bug in order to have it solved correctly.
Cheers
tags 555244 patch
tags 558219 patch
thanks
Hi,
To solve these bugs, the file debian/link must be changed to
link
/usr/lib/exaile/plugins/httpserver/data/prototype.js
towards
/usr/share/javascript/prototype/prototype.js
The attached trivial patch corrects this (not tested yet).
Cheers,
Xavier
14 matches
Mail list logo
