Bug#872544: dbusada: Please update for gnat-7

2017-09-01 Thread Reto Buerki
Hi, On 09/01/2017 01:41 PM, Gianfranco Costamagna wrote: > since we got no answer, and this is blocking the gnat transition (one of the > last blockers), I think > we should bump severity and go ahead even without a maintainer answer (please > followup, there is still > time to address the issue

Bug#749806: pcscada: FTBFS - build depends gnat, gnat-4.6

2014-07-27 Thread Reto Buerki
Hi Breno On 07/26/2014 10:15 PM, Breno Leitao wrote: > On 07/24/2014 06:20 PM, Reto Buerki wrote: >> On 07/24/2014 10:21 PM, Breno Leitao wrote: >>> This is a bug that is impacting ppc64el bootstrap also. >>> >>> My recomendantion is to keep just a b

Bug#749806: (no subject)

2014-07-24 Thread Reto Buerki
On 07/24/2014 10:21 PM, Breno Leitao wrote: > This is a bug that is impacting ppc64el bootstrap also. > > My recomendantion is to keep just a build-depend on gnat, unless you have > strict > dependency of version 4.6, which is not the case in 90% of the packages that > depends on version 4.6 You

Bug#699194: diff for NMU 0.7.1-3.1

2013-01-29 Thread Reto Buerki
Hi, On 01/29/2013 09:56 PM, Anton Gladky wrote: > tags 699194 + pending > thanks > > Dear maintainer, > > I've prepared an NMU for pcscada (versioned as 0.7.1-3.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should delay it longer. Thanks for the NMU, but I already fixed

Bug#657417: NMU for pcscada

2012-02-19 Thread Reto Buerki
Hi, On 02/19/2012 01:18 PM, Sébastien Villemot wrote: > During the BSP in Paris at IRILL, I prepared an NMU for the pcscada > package, versioned as 0.7.1-1.1. I did not upload it since I am a > DM. The patch is attached. Thanks for the patch. I already fixed this bug but did not have time to uplo

Bug#647796: pcscada: diff for NMU version 0.6-2.1

2011-12-07 Thread Reto Buerki
Hi, On 12/07/2011 05:28 PM, Alexander Reichle-Schmehl wrote: > * Reto Buerki [21 22:45]: > >>>> Thanks for preparing a NMU for pcscada. But this is not needed in this >>>> case because I got the new PCSC/Ada version 0.7 almost ready for upload. >>> C

Bug#647796: pcscada: diff for NMU version 0.6-2.1

2011-11-21 Thread Reto Buerki
On 11/21/2011 10:38 PM, Luca Falavigna wrote: > Il 21/11/2011 22:20, Reto Buerki ha scritto: >> Thanks for preparing a NMU for pcscada. But this is not needed in this >> case because I got the new PCSC/Ada version 0.7 almost ready for upload. > > Cool! I've reschedule

Bug#647796: pcscada: diff for NMU version 0.6-2.1

2011-11-21 Thread Reto Buerki
Hi, On 11/21/2011 10:03 PM, Luca Falavigna wrote: > tags 647796 + patch pending > thanks > > I've prepared an NMU for pcscada (versioned as 0.6-2.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. Thanks for preparing a NMU for pcscada. But this is not

Bug#646927: Bug#642612: ahven: diff for NMU version 2.1-1.1

2011-11-17 Thread Reto Buerki
Hi, On 11/16/2011 11:55 AM, Didier Raboud wrote: > I've prepared an NMU for ahven (versioned as 2.1-1.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. Thanks for preparing an NMU for ahven. But I think the better approach would be for me to prepare a n

Bug#571436: polyorb: FTBFS: tests failed

2010-03-02 Thread Reto Buerki
Lucas Nussbaum wrote: > On 01/03/10 at 23:00 +0100, Reto Buerki wrote: >> Is there a policy which defines the network setup and firewall rules for >> an official build host? If every host is different, we better disable >> the MIOP test because testing multicast functionality

Bug#571436: polyorb: FTBFS: tests failed

2010-03-01 Thread Reto Buerki
Lucas Nussbaum wrote: > On 28/02/10 at 14:02 +0100, Reto Buerki wrote: >> The relevant part of the build log is: >> >>>> / Begin of Scenario CORBA_MIOP >>>> >>>> Scenario CORBA_MIOP >>>> Description: CORBA/MIOP te

Bug#571436: polyorb: FTBFS: tests failed

2010-02-28 Thread Reto Buerki
Hi, The relevant part of the build log is: >> / Begin of Scenario CORBA_MIOP >> >> Scenario CORBA_MIOP >> Description: CORBA/MIOP test >> Starting scenario CORBA_MIOP >> >> -- Begin of Test CORBA_MIOP_0 >> >> Read : test CORBA_MIOP_0 >> Id : Simple test >> Type: client_

Bug#562342: Bug #562342: polyorb: FTBFS: tests failed

2010-01-27 Thread Reto Buerki
Ludovic Brenta wrote: > The kfreebsd-i386 buildd, finzi.debian.org, had similar failures, > this time the error message is: > > polyorb.utils.sockets: connect to 172.17.12.2 failed: [61] Connection > refused > > (as opposed to 172.17.12.3 on fano.debian.org). > > Is it possible that these IP add

Bug#562342: Bug #562342: polyorb: FTBFS: tests failed

2010-01-27 Thread Reto Buerki
Ludovic Brenta schrieb: > Some of the tests of 2.6.0~20090423-4 just failed on the kfreebsd-amd64 > buildd (they all passed in the previous build). Apparently all the test > failures were due to: > > polyorb.utils.sockets: connect to 172.17.12.3 failed: [61] Connection > refused > > The IP addre

Bug#561158: polyorb: FTBFS: python: command not found

2009-12-19 Thread Reto Buerki
Ludovic Brenta wrote: > Should polyorb build-depend on Python? If so, why and which version of > Python? Excerpt from the buildd log: The support/reconfig script needs it to create the IDL tree accessors for idlac. - reto -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org

Bug#561156: polyorb: FTBFS on kfreebsd-amd64: only 42 out of 86 tests passed

2009-12-17 Thread Reto Buerki
Ludovic Brenta wrote: > Package: polyorb > Version: 2.6.0~20090423-1 > Severity: serious > Justification: FTBFS on kfreebsd-amd64 > > Excerpt from the buildd log: > > Running all 35 scenario files from: > /build/buildd-polyorb_2.6.0~20090423-1-kfreebsd-amd64-XNmMrY/polyorb-2.6.0~20090423/testsui

Bug#561155: polyorb: FTBFS on i386, one test failing in test suite

2009-12-15 Thread Reto Buerki
Ludovic Brenta wrote: > I rebuilt polyorb in my i386 chroot (on a dual-core amd64 system) and > the test suite passed, so I uploaded. I am not closing this bug yet > because I want to understand the test failure; if this test depends on > certain hardware or kernel versions to succeed, I want to k