Tobias Hansen (17/06/2012):
> The patch looks fine to me. Do you do the upload?
Final diff attached.
(I almost proposed passing --parallel to dh, so that parallel=n
in DEB_BUILD_OPTIONS is automatically taken into account, but
your override prevents it from working. You may want to consider
usin
Am 17.06.2012 11:50, schrieb Cyril Brulebois:
> Tobias Hansen (17/06/2012):
>> Thanks! I reported the bug:
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53701
>
> Thanks.
>
>> If it works with gcc-4.7, we could just upload a package that uses
>> that on ia64 or not? Or do you mean gcc-4.7 crash
Tobias Hansen (17/06/2012):
> Thanks! I reported the bug:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53701
Thanks.
> If it works with gcc-4.7, we could just upload a package that uses
> that on ia64 or not? Or do you mean gcc-4.7 crashes on the next file?
I meant gcc-4.6 crashes on the next
Am 17.06.2012 00:33, schrieb Cyril Brulebois:
> Cyril Brulebois (16/06/2012):
>> I'll try to reproduce the FTBFS with 4.2 and 4.4 on a porter box.
>
> 4.2 builds fine, 4.4 doesn't. Building that particular file with
> gcc-4.7 was OK though. gcc-4.6 crashes then on the next file (cgfx16.c).
>
> I
Tobias Hansen (16/06/2012):
> Am 16.06.2012 14:16, schrieb Julien Cristau:
> > hmm, no, in that case if the bug can't get fixed we'd have to remove
> > all allegro reverse dependencies on ia64.
>
> How do we find out? Would you issue a rebuild of allegro4.2 on ia64?
I'll try to reproduce the FTB
Am 16.06.2012 14:16, schrieb Julien Cristau:
> On Sat, Jun 16, 2012 at 14:11:34 +0200, Tobias Hansen wrote:
>
>> Am 16.06.2012 13:49, schrieb Julien Cristau:
>>> On Wed, Jun 13, 2012 at 09:28:25 +0200, Tobias Hansen wrote:
>>>
allegro4.4 is now a migration candidate and I didn't get access
>>
On Sat, Jun 16, 2012 at 14:11:34 +0200, Tobias Hansen wrote:
> Am 16.06.2012 13:49, schrieb Julien Cristau:
> > On Wed, Jun 13, 2012 at 09:28:25 +0200, Tobias Hansen wrote:
> >
> >> allegro4.4 is now a migration candidate and I didn't get access
> >> to a porterbox yet. Can we continue the transi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 16.06.2012 13:49, schrieb Julien Cristau:
> On Wed, Jun 13, 2012 at 09:28:25 +0200, Tobias Hansen wrote:
>
>> allegro4.4 is now a migration candidate and I didn't get access
>> to a porterbox yet. Can we continue the transition?
>>
> I don't thi
On Wed, Jun 13, 2012 at 09:28:25 +0200, Tobias Hansen wrote:
> allegro4.4 is now a migration candidate and I didn't get access to a
> porterbox yet. Can we continue the transition?
>
I don't think so. Either that FTBFS gets fixed, or the transition gets
reverted, AFAICT.
Cheers,
Julien
signat
Am 04.06.2012 01:05, schrieb Cyril Brulebois:
> Tobias Hansen (04/06/2012):
>> I thought removing allegro4.2 would be the next step. But now that you
>> say it, that's not necessary, because liballegro4.2-dev was replaced,
>> right? Also alogg and allegro-demo-data, but they're also no obstacle
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 04.06.2012 01:05, schrieb Cyril Brulebois:
> Tobias Hansen (04/06/2012):
>> I thought removing allegro4.2 would be the next step. But now
>> that you say it, that's not necessary, because liballegro4.2-dev
>> was replaced, right? Also alogg and a
Tobias Hansen (04/06/2012):
> I thought removing allegro4.2 would be the next step. But now that you
> say it, that's not necessary, because liballegro4.2-dev was replaced,
> right? Also alogg and allegro-demo-data, but they're also no obstacle
> for the transition, except that alogg will FTBFS wi
Hi,
Am 04.06.2012 00:26, schrieb Cyril Brulebois:
>> Am I supposed to file RM requests now or does the Release Team
>> take care of that?
>
> Hmm, what do you want to see RM'd?
I thought removing allegro4.2 would be the next step. But now that you
say it, that's not necessary, because liballegro
Hello Tobias,
Tobias Hansen (03/06/2012):
> allegro4.4 is now in unstable, installed for all architectures except
> ia64 and mips. ia64 failed with an internal compiler error and mips is
> building for 12 hours now.
now installed on mips. Previously I tried a give back on ia64, just in
case it w
allegro4.4 is now in unstable, installed for all architectures except
ia64 and mips. ia64 failed with an internal compiler error and mips is
building for 12 hours now.
Am I supposed to file RM requests now or does the Release Team take
care of that?
I prepared a NMU for open-invaders that should
I just took note of the source package allegro-demo-data. That one can
also be removed in the course of this transition.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Am 20.05.2012 01:24, schrieb Steven Chamberlain:
> On 19/05/12 15:27, Tobias Hansen wrote:
>> Done. The package on mentors.debian.net is replaced:
>> http://mentors.debian.net/debian/pool/main/a/allegro4.4/allegro4.4_4.4.2-1.dsc
>
> Hi Tobias,
>
> I tried building your package on kfreebsd-i386 bu
On 19/05/12 15:27, Tobias Hansen wrote:
> Done. The package on mentors.debian.net is replaced:
> http://mentors.debian.net/debian/pool/main/a/allegro4.4/allegro4.4_4.4.2-1.dsc
Hi Tobias,
I tried building your package on kfreebsd-i386 but it fails because
ESTRPIPE is only defined for Linux. alleg
Tobias Hansen (19/05/2012):
> I can't reproduce this on a freshly updated amd64 sid pbuilder. Looks
> like cmake fails to copy a file. Did you make sure that there's enough
> space on the drive you're building on? A full drive is my best guess
> why this could happen.
Then I'll try and see what h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 19.05.2012 16:48, schrieb Cyril Brulebois:
> Tobias Hansen (19/05/2012):
>> Done. The package on mentors.debian.net is replaced:
>>
>> http://mentors.debian.net/debian/pool/main/a/allegro4.4/allegro4.4_4.4.2-1.dsc
>>
>>
>>
You can view the chan
Tobias Hansen (19/05/2012):
> Done. The package on mentors.debian.net is replaced:
>
> http://mentors.debian.net/debian/pool/main/a/allegro4.4/allegro4.4_4.4.2-1.dsc
>
> You can view the changes here:
>
> http://anonscm.debian.org/gitweb/?p=pkg-games/allegro4.4.git;a=commitdiff;h=ed9236b61ec35a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 19.05.2012 15:22, schrieb Cyril Brulebois:
> Tobias Hansen (19/05/2012):
>> Ok, one thing we should do before the upload is to remove the
>> sonames from all newly introduced dev package names, right? And
>> mention newly introduced packages expl
Tobias Hansen (19/05/2012):
> Ok, one thing we should do before the upload is to remove the sonames
> from all newly introduced dev package names, right? And mention newly
> introduced packages explicitly in the changelog. Anything else?
$ grep Package'.*'dev debian/control
Package: liballegro4.
Tobias Hansen (19/05/2012):
> > Despite <4fa98a44.8050...@gmx.de>,
>
> Did you mean to post an url?
That's called a message ID. :-)
http://lists.debian.org/4fa98a44.8050...@gmx.de works for all Debian things
http://mid.gmane.org/4fa98a44.8050...@gmx.de usually works for others as well.
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ok, one thing we should do before the upload is to remove the sonames
from all newly introduced dev package names, right? And mention newly
introduced packages explicitly in the changelog. Anything else?
-BEGIN PGP SIGNATURE-
Version: GnuPG
CC'ing the other maintainer, Andreas.
Am 19.05.2012 14:38, schrieb Cyril Brulebois:
> Tobias Hansen (19/05/2012):
>> I filed a sponsorship request with all the necessary information and
>> link to the source package:
>>
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673345
>
> Despite <4fa
Tobias Hansen (19/05/2012):
> I filed a sponsorship request with all the necessary information and
> link to the source package:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673345
Despite <4fa98a44.8050...@gmx.de>, I see a liballeggl4.4-dev package
there, which isn't even mentioned in t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
That would be great!
I filed a sponsorship request with all the necessary information and
link to the source package:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673345
Best regards,
Tobias
Am 19.05.2012 13:00, schrieb Cyril Brulebois:
> Tob
Tobias Hansen (19/05/2012):
> we are still looking for a sponsor. I really hope we find one in time
> for the freeze.
I pinged Ansgar but got no replies. Please point me at a source package,
I'll try and have a look soon.
Mraw,
KiBi.
signature.asc
Description: Digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
we are still looking for a sponsor. I really hope we find one in time
for the freeze.
Best regards,
Tobias
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAE
Hi Tobias,
Cyril Brulebois (08/05/2012):
> From the tracker, level 2 only depends on libdump, but no big deal:
> http://release.debian.org/transitions/html/liballegro.html
please go ahead with an upload to unstable. Your transition looks like
it shouldn't get entangled in any other transitions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Cyril,
thanks for progressing this so quickly!
Am 08.05.2012 22:34, schrieb Cyril Brulebois:
>
> And well, versions in -dev packages are harmful. If you want to
> rename it right now (still providing the old liballegro4.2-dev),
> I'd rather sug
Tobias Hansen (08/05/2012):
> These are the affected packages in Debian unstable:
The list looks good, from a quick diff against the tracker (see below).
> The transition should work like this:
>
> - Upload allegro4.4, remove allegro4.2 and libalogg1.
> - binNMUs for the libraries libdumb and g
Hi Tobias,
Tobias Hansen (08/05/2012):
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
thanks for the very detailed bug report, that's very much appreciated.
> These are the affected packages in Debian unstable:
[…]
I'll s
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I want to request a transition slot for the allegro4.2 -> allegro4.4
transition. allegro4.2 is orphaned and Andreas Rönnquist and myself packaged
allegro4.4.
We are not Debian Developers
35 matches
Mail list logo
