<送信者> ワンダーライフ 佐久間
[EMAIL PROTECTED]
突然のメールの配信深くお詫び申し上げます。
これはWEB上にアドレスを公開されている方を対象に配信している広告
メールです。今後一切のメール配信不要の方はこのメールをそのまま
ご返信ください。
掲示板に投稿するより効果的です！
☆ ＤＭ用メールアドレス１５０万個 ☆
宣伝の効果抜群！大好評！アクセス数の少ない掲示板では・・・
国内のＤＭ用メールアドレスが１５０万個あります。
ご希望であれば、テキストファイルで下記に示す価格でお譲り致します。
なお、重複しているメールアドレスは有
Drew Parsons wrote:
> And more to the point [ ;) ], how do I force the autobuilder maintainers to
> actually upload my package once it has been autobuilt?
> The s390 version of xprint-xprintorg has been built for a whole week now[1],
> but it still hasn't been uploaded to the archive[2]. All oth
$B!!(B<$BAw?. $B%o%s%@!<%i%$%U!!:45W4V(B
$B!!G[?.Dd;_!'([EMAIL PROTECTED]
(B
$B!!FMA3$N%a!<%k$NG[?.?<$/$*OM$S?=$7>e$2$^$9!#(B
$B!!$3$l$O(BWEB$B>e$K%"%I%l%9$r8x3+$5$l$F$$$kJ}$rBP>]$KG[?.$7$F$$$k9-9p(B
$B!!%a!<%k$G$9!#:#8e0l@Z$N%a!<%kG[?.ITMW$NJ}$O$3$N%a!<%k$r$=$N$^$^(B
$B!!$4JV?.$/$
Is there a way to specify the following in a Debhelper file (such as
.dirs or .links)?
usr/include/$(SHELLVARIABLE)/foo.h
(Note: it doesn't *have* to be a shell variable; just some form of meta
value that I can control when invoking dh_installdirs or dh_installlinks,
etc).
I could use m4, but it
Drew Parsons wrote:
> And more to the point [ ;) ], how do I force the autobuilder maintainers to
> actually upload my package once it has been autobuilt?
> The s390 version of xprint-xprintorg has been built for a whole week now[1],
> but it still hasn't been uploaded to the archive[2]. All oth
Is there a way to specify the following in a Debhelper file (such as
.dirs or .links)?
usr/include/$(SHELLVARIABLE)/foo.h
(Note: it doesn't *have* to be a shell variable; just some form of meta
value that I can control when invoking dh_installdirs or dh_installlinks,
etc).
I could use m4, but it
On Thu, Oct 17, 2002 at 03:15:35PM +0200, Bas Zoetekouw wrote:
> Hi Sven!
>
> You wrote:
>
> > > Sorry, I did not make myself clear: I did not upload a new
> > > package -- I want to trigger a new build attempt for an old
> > > package of mine now that debhelper has been fixed.
> >
> > The autob
On Thu, Oct 17, 2002 at 03:15:35PM +0200, Bas Zoetekouw wrote:
> Hi Sven!
>
> You wrote:
>
> > > Sorry, I did not make myself clear: I did not upload a new
> > > package -- I want to trigger a new build attempt for an old
> > > package of mine now that debhelper has been fixed.
> >
> > The autob
On Thu, Oct 17, 2002 at 01:16:43PM +0200, Marco Kuhlmann wrote:
> * Bas Zoetekouw <[EMAIL PROTECTED]> (2002-10-17 12:17:56 +0200):
>
> > If you uploaded a new package, the buildds will automagically
> > build it. I could take some time, though.
>
> Sorry, I did not make myself clear: I did not u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have a problem with dependencies in some of my packages:
There is a "task" package which just depends on the concrete version
of the children. It looks like this:
- - debian/contrl ---
Package: foo
Depends: foo-doc (= ${S
On Thu, Oct 17, 2002 at 11:44:14AM +0200, Marco Kuhlmann wrote:
>
> How do I force a rebuild on buildd?
And more to the point [ ;) ], how do I force the autobuilder maintainers to
actually upload my package once it has been autobuilt?
The s390 version of xprint-xprintorg has been built for a who
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have a problem with dependencies in some of my packages:
There is a "task" package which just depends on the concrete version
of the children. It looks like this:
- - debian/contrl ---
Package: foo
Depends: foo-doc (= ${S
Hi Sven!
You wrote:
> > Sorry, I did not make myself clear: I did not upload a new
> > package -- I want to trigger a new build attempt for an old
> > package of mine now that debhelper has been fixed.
>
> The autobuilder retry old packages that failed on a regular basis, just
> wait some time f
On Don, 2002-10-17 at 13:40, Sven Luther wrote:
> On Thu, Oct 17, 2002 at 01:16:43PM +0200, Marco Kuhlmann wrote:
> > * Bas Zoetekouw <[EMAIL PROTECTED]> (2002-10-17 12:17:56 +0200):
> >
> > > If you uploaded a new package, the buildds will automagically
> > > build it. I could take some time, th
On Thu, Oct 17, 2002 at 11:44:14AM +0200, Marco Kuhlmann wrote:
>
> How do I force a rebuild on buildd?
And more to the point [ ;) ], how do I force the autobuilder maintainers to
actually upload my package once it has been autobuilt?
The s390 version of xprint-xprintorg has been built for a who
Hi Sven!
You wrote:
> > Sorry, I did not make myself clear: I did not upload a new
> > package -- I want to trigger a new build attempt for an old
> > package of mine now that debhelper has been fixed.
>
> The autobuilder retry old packages that failed on a regular basis, just
> wait some time f
On Thu, Oct 17, 2002 at 01:16:43PM +0200, Marco Kuhlmann wrote:
> * Bas Zoetekouw <[EMAIL PROTECTED]> (2002-10-17 12:17:56 +0200):
>
> > If you uploaded a new package, the buildds will automagically
> > build it. I could take some time, though.
>
> Sorry, I did not make myself clear: I did not u
* Bas Zoetekouw <[EMAIL PROTECTED]> (2002-10-17 12:17:56 +0200):
> If you uploaded a new package, the buildds will automagically
> build it. I could take some time, though.
Sorry, I did not make myself clear: I did not upload a new
package -- I want to trigger a new build attempt for an old
pack
On Don, 2002-10-17 at 13:40, Sven Luther wrote:
> On Thu, Oct 17, 2002 at 01:16:43PM +0200, Marco Kuhlmann wrote:
> > * Bas Zoetekouw <[EMAIL PROTECTED]> (2002-10-17 12:17:56 +0200):
> >
> > > If you uploaded a new package, the buildds will automagically
> > > build it. I could take some time, th
Hi Marco!
You wrote:
> How do I force a rebuild on buildd? One of my package could not
> be built due to a bug in debhelper which is now solved. Two of
> the architectures have already built the package successfully now
> that the new version is available; can I trigger the other
> architecture
Dear mentors:
How do I force a rebuild on buildd? One of my package could not
be built due to a bug in debhelper which is now solved. Two of
the architectures have already built the package successfully now
that the new version is available; can I trigger the other
architectures to try a new
* Bas Zoetekouw <[EMAIL PROTECTED]> (2002-10-17 12:17:56 +0200):
> If you uploaded a new package, the buildds will automagically
> build it. I could take some time, though.
Sorry, I did not make myself clear: I did not upload a new
package -- I want to trigger a new build attempt for an old
pack
Hi Marco!
You wrote:
> How do I force a rebuild on buildd? One of my package could not
> be built due to a bug in debhelper which is now solved. Two of
> the architectures have already built the package successfully now
> that the new version is available; can I trigger the other
> architecture
Dear mentors:
How do I force a rebuild on buildd? One of my package could not
be built due to a bug in debhelper which is now solved. Two of
the architectures have already built the package successfully now
that the new version is available; can I trigger the other
architectures to try a ne
On Wed, Oct 16, 2002 at 08:41:10PM +, Bruno Barrera C wrote:
> become as new mantainer, but i got a problem that there is no chilean
> debian developers , who could sign my GPG key, and i dont have drive
> card.
> It is possible if I send my Chilean Identify Card, as a way to identify
> me?
H
25 matches
Mail list logo
