Hi,
On Tue, 18 Nov 2014, Maxime Chatelle wrote:
Is it a good practice to use the same Alioth packaging repository to
maintain two (and later, three) source packages ? Obviously the three
source package come from the same upstream git repository. The point is
to maintain 2 (or 3) development
Le 19/11/2014 11:21, Raphael Hertzog a écrit :
Hi,
On Tue, 18 Nov 2014, Maxime Chatelle wrote:
Is it a good practice to use the same Alioth packaging repository to
maintain two (and later, three) source packages ? Obviously the three
source package come from the same upstream git
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package python-instagram
Package name: python-instagram
Version : 1.2.0-1
Upstream Author : Instagram, Inc apidevelop...@instagram.com
URL :
Your message dated Wed, 19 Nov 2014 16:32:31 +
with message-id e1xr8bd-gk...@quantz.debian.org
and subject line closing RFS: ufoai-music/2.5-1 [ITP]
has caused the Debian Bug report #762228,
regarding RFS: ufoai-music/2.5-1 [ITP]
to be marked as done.
This means that you claim that the
Your message dated Wed, 19 Nov 2014 16:32:31 +
with message-id e1xr8be-gs...@quantz.debian.org
and subject line closing RFS: pktools/2.5.4-1~exp1
has caused the Debian Bug report #769604,
regarding RFS: pktools/2.5.4-1~exp1
to be marked as done.
This means that you claim that the problem
On Wed, Nov 19, 2014 at 11:55:20AM +0100, Thibaut Paumard wrote:
Le 19/11/2014 11:21, Raphael Hertzog a écrit :
Hi,
On Tue, 18 Nov 2014, Maxime Chatelle wrote:
Is it a good practice to use the same Alioth packaging repository to
maintain two (and later, three) source packages ?
On Wed, Nov 19, 2014 at 09:08:39AM +0100, Jörg Frings-Fürst wrote:
dget -x
http://mentors.debian.net/debian/pool/main/p/python-instagram/python-instagram_1.2.0-1.dsc
I think you should put the commit ID from which you've generated the orig
tarball into the package upstream version or at
Hi,
I'm trying to get Qemubuilder run for arm64 package building, but fails
so far. I've got a proper kernel and initrd, but breaks with:
Your architecture arm64 does not seem to be supported. Maybe that's
exactly how it is, is it?
Does anybody has got Qemubuilder run for arm64, or have any
Package: sponsorship-requests
Severity: important
I am looking for a sponsor for my package gnustep-base.
It builds these binary packages:
gnustep-base-common - GNUstep Base library - common files
gnustep-base-doc - Documentation for the GNUstep Base Library
gnustep-base-examples - Examples
On Wed, Nov 19, 2014 at 09:41:46PM +0100, Daniel Stender wrote:
Hi,
I'm trying to get Qemubuilder run for arm64 package building, but fails
so far. I've got a proper kernel and initrd, but breaks with:
Your architecture arm64 does not seem to be supported. Maybe that's
exactly how it is, is
+++ Daniel Stender [2014-11-19 21:41 +0100]:
Hi,
I'm trying to get Qemubuilder run for arm64 package building, but fails
so far. I've got a proper kernel and initrd, but breaks with:
Your architecture arm64 does not seem to be supported. Maybe that's
exactly how it is, is it?
I am not
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for the package digikam
The release team has pre-approved [1] the change, that you can download
here [2], it should be applied over the version you'll find in the PTS
[3] on the *stable* line. You can
12 matches
Mail list logo