edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: MENGUAL Jean-Philippe <mengualjeanphi@free.fr>
To: Adam Thompson <arthompson1990@gmail.com>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Debian
Date: Wed, 24 Sep 2014 00:29:54 +0200	[thread overview]
Message-ID: <5421F462.60409@free.fr> (raw)
In-Reply-To: <20140923122300.GB12972@toaster.adamthompson.me.uk>

Hi,

Could you fill a bug on the Bug Tracker System, so that we could see 
what happens? We'd need to know if something is made in the Makefile 
(upstream) and not in the Deb package. Maybe it's due to a build 
dependency missing? What kind or dep could miss?

Oegards,

Le 23/09/2014 14:23, Adam Thompson a écrit :
> On Sun, Sep 21, 2014 at 11:20:43PM +0200, MENGUAL Jean-Philippe wrote:
>>>> So far no bugs has been reported about the experimental release of
>>>> Edbrowse. Do you plan a release soon? If yes, I'll package it in sid
>>>> so that it's in the next jessie. Otherwise, I could migrate the
>>>> current one from experimental to sid, but I don't like to import in
>>>> Debian dev releases of the packages.
> Unfortunately I was only able to install this on my work system yesterday,
> and so have only just found this bug.
> However, it appears that the experimental debian package is unable to resolve
> proxy server names, at least the one we're using where I work.
> This works when I hand-compile (i.e.
> use our makefile against the same libs as the debian package)
> so I think it's something to do with the way the program's being built for Debian.
> I can try and compose a proper bug report if that'll help,
> however I'm not sure of the best way to submit instructions to reproduce as I
> obviously can't talk too much about the nature of my workplace's proxy set up.
>
> Cheers,
> Adam.


-- 

Jean-Philippe MENGUAL

accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels

Mail: texou@accelibreinfo.eu

Site Web: http://www.accelibreinfo.eu


  reply	other threads:[~2014-09-23 22:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.8.1411327181.400.edbrowse-dev@lists.the-brannons.com>
2014-09-21 21:17 ` Chris Brannon
2014-09-21 21:20   ` MENGUAL Jean-Philippe
2014-09-23 12:23     ` Adam Thompson
2014-09-23 22:29       ` MENGUAL Jean-Philippe [this message]
2014-09-25 15:30       ` Chris Brannon
2014-09-25 17:23         ` MENGUAL Jean-Philippe
2014-09-24  7:13 Karl Dahlke
  -- strict thread matches above, loose matches on Subject: below --
2014-09-23 16:42 Karl Dahlke
2014-09-23 20:32 ` Adam Thompson
2014-09-24  4:54 ` Chris Brannon
2014-09-24 18:54   ` Adam Thompson
2014-09-21 21:19 Karl Dahlke
2014-09-22  5:53 ` Chris Brannon
2014-09-23 12:15   ` Adam Thompson
2014-09-23 14:56     ` Chris Brannon
2014-03-08 20:40 [Edbrowse-dev] debian Karl Dahlke
2014-03-08 20:45 ` MENGUAL Jean-Philippe
2014-04-01 11:20   ` Adam Thompson
2014-04-01 16:24     ` MENGUAL Jean-Philippe
2014-04-15  9:02       ` Adam Thompson
2014-01-04 20:03 Karl Dahlke
2014-01-04 17:28 Karl Dahlke
2014-01-04 18:18 ` Chris Brannon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5421F462.60409@free.fr \
    --to=mengualjeanphi@free.fr \
    --cc=arthompson1990@gmail.com \
    --cc=edbrowse-dev@lists.the-brannons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).