> but either way, id like to suggest again, we move forward and
> rather discuss how we can improve the situation, do something about
> the split and move toward un-doing it!
We look forward to seeing you in Dublin then.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a s
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: python-hurry.filesize
Version : 0.9
Upstream Author : Martijn Faassen, Startifact
* URL : https://pypi.python.org/pypi/hurry.filesize
* License : ZPL-2.1
Programming Lang: Python
Descri
Package: wnpp
Severity: wishlist
X-Debbugs-CC:
debian-devel@lists.debian.org,pkg-bitcoin-de...@lists.alioth.debian.org
Package name: bitcointrader
Version: 1.07.99
Upstream Author: July IGHOR
URL: https://github.com/JulyIGHOR/QtBitcoinTrader
License: GPL-3+ with Op
Hi
On Thu, Aug 21, 2014 at 03:16:50AM +0200, Attila Kinali wrote:
> Servus,
>
> On Wed, 20 Aug 2014 18:43:18 +0900
> Norbert Preining wrote:
>
> > By continuing old fights, inspite of the very clearly friendly and
> > open offers and suggestions byu Michael, you and others from AV continue
> >
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: compass-blueprint-plugin
Version : 0.0.1
Upstream Author : Scott Davis
* URL : http://compass-blueprint.org/
* License : Expat
Programmi
Matthias Urlichs writes:
> Russ Allbery:
>> It's somewhat harder to maintain, but it's vastly better for
>> communicating to upstream or to other distributions.
> Mmh. Whenever Upstream uses git, my favorite method of sending a patch
> is to put the fix in a separate branch, and then tell ^w ask
Hi,
On 17.08.2014 00:49, Andreas Cadhalpun wrote:
I have now sent the pkg-config patches to the BTS [1].
I have found a simpler way to make it possible to link packages not
using pkg-config against FFmpeg in Debian:
The lib*-ffmpeg-dev packages now install symbolic links from the
standard li
Hi,
Russ Allbery:
> It's somewhat harder to maintain, but it's vastly better for
> communicating to upstream or to other distributions.
>
Mmh. Whenever Upstream uses git, my favorite method of sending a patch
is to put the fix in a separate branch, and then tell ^w ask them
to "git pull" it.
--
8 matches
Mail list logo