On 19 August 2014 11:03, Brian May wrote:
> Any ideas how to fix
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755598 ?
>
> I have had a fiddle, but not really making any progress (apart from
> Python3 package which works fine).
>
> For example, I renamed migrations to south_migrations and
On 19 August 2014 13:22, Tianon Gravi wrote:
> Have you tried comparing the existing orig tarball from the archive to
> the corresponding tarball downloaded via uscan?
>
> $ curl -sSL '
> http://http.debian.net/debian/pool/main/libr/librabbitmq/librabbitmq_0.5.0.orig.tar.gz
> '
> | sha1sum
>
On 18 August 2014 18:11, Brian May wrote:
> Unfortunately, debian/watch (AFAIK) doesn't include any details of any
> changes that were made to the tar.gz file by the package developer.
It's been my understanding that this is exactly one of the main uses of
the "command" argument in debian/watch.
Hello,
Any ideas how to fix
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755598 ?
I have had a fiddle, but not really making any progress (apart from Python3
package which works fine).
For example, I renamed migrations to south_migrations and created a
Django1.7 compliant migrations directo
On 19 August 2014 09:55, Tianon Gravi wrote:
> Not that I'm involved in the packaging or the upstream here in any
> way, but I just wanted to point out that this is exactly what
> "debian/watch"[1] is for, which uscan(1) will read and use to find
> upstream versions.
>
Unfortunately, debian/watc
On Mon, Aug 18, 2014 at 6:52 PM, Brian May
wrote:
> However, just to make things more interesting, the 5.0 and 5.1 tar.gz file
> from github contains a "sub git repository" (not sure I have used correct
> git terminology here), with invalid relative reference, under
> rabbitmq-c-0.5.1/codegen, whi
On 18 August 2014 17:52, Brian May wrote:
> I take this to mean I should be downloading the orig.tag.gz from github.
Not that I'm involved in the packaging or the upstream here in any
way, but I just wanted to point out that this is exactly what
"debian/watch"[1] is for, which uscan(1) will read
Hello,
I would like to package the latest upstream version of librabbitmq.
However, the packaging is in git, and I am not sure how to insert the
latest upstream version in this git repository.
>From debian/control:
Homepage: https://github.com/alanxz/rabbitmq-c
Vcs-Git: git://anonscm.debian.org
Hello,
Just in case anyone is thinking of back porting my celery package to
Wheezy, it won't work without disabling the Python3 stuff first.
Otherwise it will fail with undefined symbols, I suspect this is because
Python3.2 is not supported.
(previously I had backported version 3.1.12 thinking i
Hi,
Thomas Goirand told me that I should just upload it to mentors with the Python
Module Packaging Team as maintainer and me as Uploader. The package can be
obtained using
dget -x
http://mentors.debian.net/debian/pool/main/p/pysdl2/pysdl2_0.9.3+dfsg1-1.dsc
The mentors sponsorship-request
On Wed, Jul 23, 2014 at 03:33:03PM +0200, Matthias Klose wrote:
> Asking what will happen with packages depending on wxPython 2.8 and
> which cannot be converted to 3.0.
There aren't many incompatible changes between wxPython 2.8 and 3.0.
With the C++ API, the Unicode changes have been quite painf
11 matches
Mail list logo
