Accepted:
libweed-dev_1.3.7-1_amd64.deb
to main/l/lives/libweed-dev_1.3.7-1_amd64.deb
libweed0_1.3.7-1_amd64.deb
to main/l/lives/libweed0_1.3.7-1_amd64.deb
lives-data_1.3.7-1_all.deb
to main/l/lives/lives-data_1.3.7-1_all.deb
lives_1.3.7-1.debian.tar.gz
to
fluidsynth-dssi_1.0.0-3_amd64.changes uploaded successfully to localhost
along with the files:
fluidsynth-dssi_1.0.0-3.dsc
fluidsynth-dssi_1.0.0-3.debian.tar.gz
fluidsynth-dssi_1.0.0-3_amd64.deb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
Accepted:
fluidsynth-dssi_1.0.0-3.debian.tar.gz
to main/f/fluidsynth-dssi/fluidsynth-dssi_1.0.0-3.debian.tar.gz
fluidsynth-dssi_1.0.0-3.dsc
to main/f/fluidsynth-dssi/fluidsynth-dssi_1.0.0-3.dsc
fluidsynth-dssi_1.0.0-3_amd64.deb
to main/f/fluidsynth-dssi/fluidsynth-dssi_1.0.0-3_amd64.deb
On Wed, Sep 15, 2010 at 08:02:28AM +, ales...@users.alioth.debian.org wrote:
The following commit has been merged in the master branch:
commit 3280bcec5230342bb12bcafb3c5a5978b07f
Author: Alessio Treglia ales...@debian.org
Date: Wed Sep 15 09:45:34 2010 +0200
Finalize changelog.
Package: hydrogen
Severity: normal
Tags: patch upstream
Forwarded:
https://www.assembla.com/spaces/hydrogen/tickets/133-ftbs-with-new-qt-4-7
Hi,
hydrogen fails to build on experimental with the latest Qt 4.7.
g++ -o libs/hydrogen/src/song.o -c -O3 -fomit-frame-pointer -funroll-loops -g
-O2
Jonas,
thanks for pointing out this.
On Wed, Sep 15, 2010 at 11:58 AM, Jonas Smedegaard d...@jones.dk wrote:
It seems to me that it contains important regression fixes and only few
things apart from that. If that is correct, I believe it is a good
candidate for Squeeze, and suggest to target
Hi,
Just switching to dpkg source format 3.0 does not work nicely with
git-buildpackage: the source format auto-applies patches and leave it as
such after package cleanup, while git-buildpackage expects patches to be
unapplied.
As some may have noticed in past threads, I have not liked the
Am 15.09.2010 13:40, schrieb Jonas Smedegaard:
I hereby propose that we recommend generally switching to source
format 3.0 (quilt) - even for packages not currently using patches -
and add the following info to debian/source/local-options:
unapply-patches = True
abort-on-uptream-changes = True
Am 15.09.2010 13:35, schrieb Alessio Treglia:
Many changes have been made, so I'd feel more comfortable to see a
sort of 'long term' support provided by upstream for the 1.3.4
release.
I am going to email the current maintainer about this situation.
Is it possible to backport all the patches
On 2010-09-14 22:41, Hans-Christoph Steiner wrote:
Honestly, I think he's heard it enough about it from IOhannes and me. I
think it would be helpful if others could start the discussion with him.
even though paul is really not very responsive these days i would hate
to do anything with one
ACK from me. Sounds really great.
On 9/15/10, Jonas Smedegaard d...@jones.dk wrote:
Hi,
Just switching to dpkg source format 3.0 does not work nicely with
git-buildpackage: the source format auto-applies patches and leave it as
such after package cleanup, while git-buildpackage expects
PS: in the meantime a rc-bug for the puredata packages has appeared
[1], which i cannot reproduce at all; if someone here could have a look
at it i would be thankful.
On today's sid
$ sudo apt-get install puredata --no-install-recommends
$ puredata
works.
- Fabian
I've tried to run git-buildpackage -S -sa to build the source package and...
dpkg-source: info: using options from
lives/debian/source/local-options: --unapply-patches=True
--abort-on-upstream-changes=True
dpkg-source: warning: --unapply-patches=True is not a valid option
for
On Wed, Sep 15, 2010 at 04:00:55PM +0200, Alessio Treglia wrote:
lives/debian/source/local-options: --unapply-patches=True
git-buildpackage won't complain if you omit =True in local-options,
but I haven't verified the generated debian.tar.gz
HTH
--
mail: a...@thur.de http://adi.thur.de
On Wed, Sep 15, 2010 at 2:11 PM, Fabian Greffrath fab...@greffrath.com wrote:
Is it possible to backport all the patches that fix an issue marked
regression to the current package in unstable?
Mmmh.. before backporting the patches, we should try to undertand
which of those regressions might
That's the solution!
On Wed, Sep 15, 2010 at 4:08 PM, Adrian Knoth a...@drcomp.erfurt.thur.de
wrote:
git-buildpackage won't complain if you omit =True in local-options,
...and works fine!
--
Alessio Treglia ales...@debian.org
Debian Ubuntu Developer | Homepage:
On Wed, Sep 15, 2010 at 04:13:25PM +0200, Alessio Treglia wrote:
That's the solution!
On Wed, Sep 15, 2010 at 4:08 PM, Adrian Knoth a...@drcomp.erfurt.thur.de
wrote:
git-buildpackage won't complain if you omit =True in local-options,
...and works fine!
I am to blame for that: I *guessed*
lives_1.3.8-1_amd64.changes uploaded successfully to localhost
along with the files:
lives_1.3.8-1.dsc
lives_1.3.8.orig.tar.bz2
lives_1.3.8-1.debian.tar.gz
lives_1.3.8-1_amd64.deb
libweed0_1.3.8-1_amd64.deb
libweed-dev_1.3.8-1_amd64.deb
lives-data_1.3.8-1_all.deb
Greetings,
Accepted:
libweed-dev_1.3.8-1_amd64.deb
to main/l/lives/libweed-dev_1.3.8-1_amd64.deb
libweed0_1.3.8-1_amd64.deb
to main/l/lives/libweed0_1.3.8-1_amd64.deb
lives-data_1.3.8-1_all.deb
to main/l/lives/lives-data_1.3.8-1_all.deb
lives_1.3.8-1.debian.tar.gz
to
Processing commands for cont...@bugs.debian.org:
#libffado (2.0.1+svn1856-2) UNRELEASED; urgency=low
#
# * Refactor common python code into ffado-python-support
#(Closes: #594568) (LP: #524702 #624514)
#
limit source libffado
Limiting to bugs with field 'source' containing at least one
On Sun, Aug 22, 2010 at 12:59:42PM +0200, Torquil Macdonald Sørensen wrote:
Hi!
Package: jackd2
Version: 1.9.5~dfsg-19
Severity: normal
Before I used jackd1 and the file /etc/security/limits.d/audio.conf.
At some point I upgraded to jackd2 and no longer have that file. I
have not deleted
Processing commands for cont...@bugs.debian.org:
tags 593922 + moreinfo
Bug #593922 [jackd2] jackd2: Missing /etc/security/limits.d/audio.conf
Added tag(s) moreinfo.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
593922:
On Wednesday 15 September 2010 07:40:56 Jonas Smedegaard wrote:
Hi,
Just switching to dpkg source format 3.0 does not work nicely with
git-buildpackage: the source format auto-applies patches and leave it as
such after package cleanup, while git-buildpackage expects patches to be
unapplied.
On Wed, Sep 15, 2010 at 12:29:42PM -0400, Andres Mejia wrote:
On Wednesday 15 September 2010 07:40:56 Jonas Smedegaard wrote:
I hereby propose that we recommend generally switching to source
format 3.0 (quilt) - even for packages not currently using patches -
and add the following info to
24 matches
Mail list logo
