Package: wnpp
Severity: wishlist
Owner: Daniel Stender
* Package name: pyomo
Version : 4.0.9682
Upstream Author : William E. Hart
* URL : http://pyomo.org
* License : BSD
Programming Lang: Python
Description : Python Optimization Modeling Objects
Pyomo
Hi all,
Some folks in the publicity team are thinking about live-denting the
release. This will basically be relaying IRC to identi.ca/debian and
elswhere, with wording changes for people not as familiar with Debian.
In the past we have interspersed the updates with some filler during the
slow per
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: telepathy-gabble-legacy
Version : 0.16.7
Upstream Author : Collabora Ltd.
* URL : http://telepathy.freedesktop.org/wiki/
* License : LGPL-2.1
On Sun, Apr 12, 2015 at 5:14 AM, Paul Wise wrote:
> On Fri, Apr 10, 2015 at 11:44 PM, Marco d'Itri wrote:
>
>> What is mandatory is being able to rebuild everything from source with
>> tools available in Debian (main)
>
> Unfortunately we don't have any consistent way to manually or
> automaticall
Package: general
Severity: important
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation? updates of system
* What exactly did you do (or not do) that was effective (or
ineffectived) I tried to reinstall program, did not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
retitle 782646 [regression] segmentation fault running voaprop.exe
reassign 782646 wine
severity 782646 normal
tags 782646 +upstream +moreinfo
thanks
Hi,
This appears to be a wine bug, so I've reassigned it to the wine
maintainers. I'm fairly sure th
Processing commands for cont...@bugs.debian.org:
> retitle 782464 [regression] segmentation fault running voaprop.exe
Bug #782464 [general] general: access violation 7e9bc87f in module gdi32 dill
read of address 00aiffo2
Changed Bug title to '[regression] segmentation fault running voaprop.exe' f
On Mon, Apr 13, 2015 at 12:22 AM, Bastien ROUCARIES wrote:
> I prefer from a lintian maintainer point of view to rebuild everything
> from source. At least it is easier to detect.
That is indeed preferable since we can then prove we are distributing
the source but it is unlikely we can get there
Paul Wise writes:
> On Mon, Apr 13, 2015 at 12:22 AM, Bastien ROUCARIES wrote:
>
> > I prefer from a lintian maintainer point of view to rebuild
> > everything from source. At least it is easier to detect.
>
> That is indeed preferable since we can then prove we are distributing
> the source but
On Mon, Apr 13, 2015 at 11:37 AM, Ben Finney wrote:
> Can we agree, in the context of the original post of this thread:
>
> Rebuilding from source *is* a reasonable requirement, attainable with
> what we have today in Debian, for JavaScript works.
The first mail mentioned that grunt is not yet in
Paul Wise writes:
> On Mon, Apr 13, 2015 at 11:37 AM, Ben Finney wrote:
>
> > Can we agree, in the context of the original post of this thread:
> >
> > Rebuilding from source *is* a reasonable requirement, attainable with
> > what we have today in Debian, for JavaScript works.
>
> The first mail
On Mon, Apr 13, 2015 at 12:59 PM, Ben Finney wrote:
> Right, I wasn't clear enough: I'm saying that despite all the other
> non-JavaScript cases brought up later in the thread, the requirement
> (build from source form, with only build dependencies also in Debian)
> applies just fine to JavaScript
12 matches
Mail list logo
