Re: microwindows build status
Michael Schmitz <[EMAIL PROTECTED]> writes: > (I rarely do these > days, rather rely on the maintainer to check build status and > logs). This is not such a good idea. Maintainers are generally not responsible for checking build status and logs; the port maintainer (whoever is responsible for making the binary NMU) should do that andn file an RC bug. Indeed, there are many packages that miss getting into testing because of some problem uploading or building one port or another, and maintainers in general seem to be totally unaware of these. I think the people who take responsibility for uploading the binary NMUs for various ports need to also take the responsibility for filing bugs when things are failing.
Re: microwindows build status
Michael Schmitz <[EMAIL PROTECTED]> writes: > I've rescheduled the 0.88pre11-4 build hoping the build dependencies > install now. But that doesn't relate to #121459 at all. As far as I can tell, it doesn't work: http://buildd.debian.org/fetch.php?&pkg=microwindows&ver=0.88pre11-4&arch=powerpc&stamp=1010178840&file=log&as=raw As yet, I'm still having trouble having anyone tell me that they reproduce #121459. Here's the deal... One of the following needs to happen: 1) Someone with access to a powerpc reports that they were able to build microwindows from current package source. Then, regardless of whatever happens with the buildd/freetype2 problem, #121459 could be closed. The buildd problem is for the buildd and powerpc porters to solve. 2) Someone with access to a powerpc says "here's the patch that fixes 121459", and says "when I apply that patch, the source builds". Then I will upload a new microwindows with the patch, and close #121459. 3) Someone says "here's a powerpc machine that you can ssh to now using your Debian account and which has the build dependencies installed". And then I can go there and deal with #121459 myself. Thomas
[판촉물,카렌다] debian-qa님 안녕하십니까?
Title: 제목없음 안녕하세요.기프트나라입니다 허락없이 글을 올리게 되어 죄송 합니다. 제품 제조사와의 직거래 유통을 통하여 저렴한 단가로 다양한 제품을 판매하고자 하오니 기타 궁금하신 점을 문의하여 주시면 최선을 다하여 답해드리겠습니다. 용도: 선물용품/기념품/판촉용품/개업용품/행사용품/ 광고용품/생활용품/가정용품/사무용품/***카렌다*** 위생용품/차량용품등 전화:055-277-9919 팩스:055-277-9916 H.P:011-597-9514 http://www.giftnala.co.kr [추천 사이트] [수신거부]
Processed: Fixed in NMU of gtranscript 0.2.0-3
Processing commands for [EMAIL PROTECTED]: > tag 117589 + fixed Bug#117589: ITA: gtranscript -- GNOME SQL database client Tags added: fixed > tag 68528 + fixed Bug#68528: gtranscript: not including postgres plugin Tags added: fixed > tag 75997 + fixed Bug#75997: gtranscript should suggest a plugin Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: microwindows build status
On Fri, Jan 04, 2002 at 07:21:16PM +0100, Michael Schmitz wrote: > Please note that I haven't filed any bug of that sort (I rarely do these > days, rather rely on the maintainer to check build status and logs). FYI: It's worth telling to maintainers - a huge proportion won't pay any attention unless information is pushed at them, particularly given that the porting process is normally so transparent. (actually, there seem to be a couple of people looking at the buildd stats pages for PowerPC so you probably don't need to bother). -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpXMbMnhegIn.pgp Description: PGP signature
Re: microwindows build status
Michael Schmitz <[EMAIL PROTECTED]> writes: > I've rescheduled the 0.88pre11-4 build hoping the build dependencies > install now. But that doesn't relate to #121459 at all. Oh yes, and Michael: direct mail to you still bounces with your mail server saying "We don't accept mail from spammers".
Re: microwindows build status
Mark Brown <[EMAIL PROTECTED]> writes: > On Thu, Jan 03, 2002 at 07:10:58PM -0800, Thomas Bushnell, BSG wrote: > > > I would like to close bug 121459, and rely on powerpc to attempt a > > build by the normal process and report a new bug against the current > > Please don't. I just tried to build it and got exactly the same error > as in the build report. What do you mean by "the build report"? Do you mean bug report 121459? Or do you mean the following: http://buildd.debian.org/fetch.php?&pkg=microwindows&ver=0.88pre11-4&arch=powerpc&stamp=1010178840&file=log&as=raw Which failed because microwindows depends on freetype2-dev, and that package depends on freetype2, and for some unknown reason, apt failed to install it.
Re: microwindows build status
Michael Schmitz <[EMAIL PROTECTED]> writes: > > > > Please don't. I just tried to build it and got exactly the same error > > > > as in the build report. > > > > > What version of apt do you have installed? > > > > 0.5.4. Why? > > Because I suspected a problem with apt at the bottom of these 'freetype2 > cannot be installed' problems. Next guess. Michael: Mail to you from me is bouncing. It needs fixed.
help needed with a reformime bug
Hi, I'd appreciate if someone could adjust the patch in #115625 to work with our version of reformime in the stable maildrop package. -- 2. That which causes joy or happiness.
Re: microwindows build status
> > libs/microwindows_0.88pre11-4: Dep-Wait by schmitz-pb [optional:uncompiled] > > Dependencies: freetype2-dev (>= 1.3.1-1), freetype2 (= 1.3.1-1) > > That may be a repercussion of using an outdated version of apt on my > autobuilder - I can retry that build. It's obvious after attempting to install freetype2 manually. What you get on an unstable system is 1.4pre.20011029-1. Even though freetype2-dev 1.3.1-1 is in stable (and depends on freetype2 (= 1.3.1-1)) apt makes no attempt at satisfying the dependency on my system by itself, I need to request freetype2-dev/stable explicitly (something the autobuild scripts just won't do). Michael
