How to force porters to rebuild a package
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 build as well? - Marco msg07496/pgp0.pgp Description: PGP signature
Re: How to force porters to rebuild a package
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 > architectures to try a new build as well? If you uploaded a new package, the buildds will automagically build it. I could take some time, though. -- Kind regards, ++ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to force porters to rebuild a package
* 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 package of mine now that debhelper has been fixed. - Marco msg07582/pgp0.pgp Description: PGP signature
Re: How to force porters to rebuild a package
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, 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 > > package of mine now that debhelper has been fixed. > > The autobuilder retry old packages that failed on a regular basis, just > wait some time for them to do it. Some will try daily, other weekly and > other will retry when they have time for it. > > You could wait a week or so, and if the situation doesn't improve, > contact the autobuilder maintainer. > > Alternatively, you could login on a debian paroject machine, and build > the program yourself. The best way to ensure the correct debhelper version is used would be a new package with a versioned build dependency anyway IMHO. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to force porters to rebuild a package
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 for them to do it. Some will try daily, other weekly and > other will retry when they have time for it. > > You could wait a week or so, and if the situation doesn't improve, > contact the autobuilder maintainer. > > Alternatively, you could login on a debian paroject machine, and build > the program yourself. Or just upload a new version. -- Kind regards, ++ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to force porters to rebuild a package
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 whole week now[1], but it still hasn't been uploaded to the archive[2]. All other architectures have been uploaded. Drew [1] http://buildd.debian.org/build.php?pkg=xprint-xprintorg [2] http://ftp.debian.org/debian/pool/main/x/xprint-xprintorg/ -- PGP public key available at http://people.debian.org/~dparsons/drewskey.txt Fingerprint: A110 EAE1 D7D2 8076 5FE0 EC0A B6CE 7041 6412 4E4A msg07585/pgp0.pgp Description: PGP signature
Dependencies to special versions
-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 (= ${Source-Version}), foo-misc (= ${Source-Version})
...
Package: foo-misc
Depends: ${shlibs:Depends}
...
Package: foo-doc
...
-
When I have installed an old version, say foo-1.0-1 and its children
with the same version, foo will depend on foo-doc-1.0-1 and
foo-misc-1.0-1.
Now I create a new version 1.0-2 of all packages and try to upgrade.
apt-get will download the files and unpacks them. Before
configuration of foo-1.0-2 it complains that foo-doc and foo-misc are
not installed in the newer version. Moreover it can't upgrade them
because it would break the dependency of the installed foo-1.0-1.
My theory is that this kind of dependencies is insane, because on
update there is no way to upgrade everything in an atomic action
which would be necessary to keep all dependencies working all the
time. Is this correct?
The work around/fix I imagine is to just depend on the package without
any revision or use something like
Depends: foo-doc (>= ${Source-Version}), foo-misc (>=
${Source-Version})
Is this correct or how would I solve a 1-1 relation between several
packages?
Thnx in advance
Schimmi
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE9rsfJHUDhE+YrLEURAgDaAKDzsNV0j8Nw/Ge8DibKDoxwsTKE/ACfSKxU
es2SM5CJfZdtQ7dnj8H4B3A=
=JOGR
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to force porters to rebuild a package
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 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 for them to do it. Some will try daily, other weekly and other will retry when they have time for it. You could wait a week or so, and if the situation doesn't improve, contact the autobuilder maintainer. Alternatively, you could login on a debian paroject machine, and build the program yourself. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to force porters to rebuild a package
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 autobuilder retry old packages that failed on a regular basis, just > > wait some time for them to do it. Some will try daily, other weekly and > > other will retry when they have time for it. > > > > You could wait a week or so, and if the situation doesn't improve, > > contact the autobuilder maintainer. > > > > Alternatively, you could login on a debian paroject machine, and build > > the program yourself. > > Or just upload a new version. It may be right in this case as michel said, but in general i don't think being impatient with the autobuilders warrants the upload of a new version. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debhelper files w/ meta values
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 gives me the shivers to think about; is there any straightforward way to do this other than building the file from an m4 source or such? -- *** Joel Baker System Administrator - lightbearer.com [EMAIL PROTECTED] http://users.lightbearer.com/lucifer/ msg07589/pgp0.pgp Description: PGP signature
Re: How to force porters to rebuild a package
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 other > architectures have been uploaded. I don't think you will be able to _force_ anybody to anything. But you could ask the porters (by writing to the mailing list of the particular port, for example) if too much time has passed (say, some weeks), to have a look at your problem. regards, Stefan -- > http://www.shockfrosted.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
$BL$>5Bz9-9p"(!!3FpJsDs6!$N$40FFb(B
$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?.$/$@$5$$!#(B (B (B $B!!7G<(HD$KEj9F$9$k$h$j8z2LE*$G$9!*(B (B $B!y!!#D#MMQ%a!<%k%"%I%l%9#1#5#0K|8D!!!y(B (B $B!!@kEA$N8z2LH472!*Bg9%I>!*%"%/%;%9?t$N>/$J$$7G<(HD$G$O!&!&!&(B (B $B!!9qFb$N#D#MMQ%a!<%k%"%I%l%9$,#1#5#0K|8D$"$j$^$9!#(B $B!!$44uK>$G$"$l$P!"%F%-%9%H%U%!%$%k$G2<5-$K<($92A3J$G$*>y$jCW$7$^$9!#(B $B!!$J$*!"=EJ#$7$F$$$k%a!<%k%"%I%l%9$OM-$j$^$;$s$,!J$3$l$OHs>o$K=EMW$J(B $B!!$3$H$G$9!K!";HMQ$G$-$J$/$J$C$F$$$k$b$N$OB?>/$4$6$$$^$9!#$G$9$,!"$"(B $B!!$i$+$8$a$=$NITB-J,$r==J,9MN8$7$F3dA}$7$F$"$j$^$9$N$G$40B?42<$5$$!#(B (B $B!!%a!<%k%"%I%l%9$r$44uK>$NJ}$O!"7oL>!V%a%k%"%I4uK>!W$H%a!<%k2<$5$$!#(B $B!!$=$N:]!"$44uK>8D?t$H!"EvJ}$NF~6b3NG'MQ$N$?$a$KBe6b?69~;~$N(B $B!!?69~$_L>!J%+%?%+%J!K$r$*CN$i$;2<$5$$!#(B (B $B@^$jJV$7!"%a!<%k%"%I%l%9%j%9%H$rE:IU$7!"EvJ};XDj$NBe6b?69~@h$r(B $B!!$4O"MmCW$7$^$9!#(B $B!!>0!"E>Aw;~4VC;=L$N$?$a$K05=L%U%!%$%k!J%Q%9%o!<%I0E9f2=!K$G(B $B!!$*Aw$jCW$7$^$9!#(B (B (B $B2A3J0lMw!'(B (B (B1$BK|7o!'(B 5,000$B1_(B (B5$BK|7o!'(B 9,000$B1_(B (B 10$BK|7o!'(B12,000$B1_(B (B 50$BK|7o!'(B15,000$B1_(B (B 150$BK|7o!'(B20,000$B1_(B (B $B!!>0!"A4?t$*Gc$$5a$aD:$/J}$K$O!"%5!<%S%9$G%"%I%l%9<}=8%=%U%H$H(B $B!!%@%V$j:o=|%=%U%H$bL5NA$K$FDs6!$7$F$*$j$^$9!#(B (B $B!!$^$?$3$NB>$K!"(B (B $B!!!&7HBS%"%I%l%9%j%9%H!'(B10,000$B1_(B $B!!!JHsHV9fLs(B37$BK|7oJ,!K(B (B (B $B!&%M%C%H%o!<%+!Jm!'(B10,000$B1_(B $B!!!JLs(B10$BK|L>J,!NETF;I\8)JL!O!'=;=j!\;aL>!\(BTEL$B!K(B (B $B!!!&FCA*N">pJs!'(B5,000$B1_(B $B!!!JpJs!'(B5,000$B1_(B $B!!!J%a%k%"%I!"K\L>!"=;=j!\(BTEL$B!"=P?H9;!"2CF~=!65CDBN!K(B (B $B!!$b$4$6$$$^$9$N$G!"$44uK>$NJ}$O$*Ld$$9g$o$;2<$5$$!#(B (B $B!!$*Ld9g$;@h!'%o%s%@!<%i%$%U(B [EMAIL PROTECTED] (B $B!!;3M|8)KL5pK`74D9:dD.>.9S4V(B29-982 (B$B!!(B090-8494-3572 (B (B (B (B-- (BTo UNSUBSCRIBE, email to [EMAIL PROTECTED] (Bwith a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: other way
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? Hi, other ways of proving your identity may be acceptable in case you cannot meet another debian developer to sign your key. How this can be done should be discussed with your application manger. Anyway, you should register your request on the key signing coordination page http://nm.debian.org/gpg.php. This way, debian members travelling you Chile can try to meet you. (For instance, I was in Chile myself 2 months ago). Good luck -Ralf.
How to force porters to rebuild a package
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 build as well? - Marco pgpjET0oyP7Y5.pgp Description: PGP signature
Re: How to force porters to rebuild a package
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 > architectures to try a new build as well? If you uploaded a new package, the buildds will automagically build it. I could take some time, though. -- Kind regards, ++ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: How to force porters to rebuild a package
* 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 package of mine now that debhelper has been fixed. - Marco pgptoDZGsDFP4.pgp Description: PGP signature
Re: How to force porters to rebuild a package
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 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 for them to do it. Some will try daily, other weekly and other will retry when they have time for it. You could wait a week or so, and if the situation doesn't improve, contact the autobuilder maintainer. Alternatively, you could login on a debian paroject machine, and build the program yourself. Friendly, Sven Luther
Re: How to force porters to rebuild a package
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, 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 > > package of mine now that debhelper has been fixed. > > The autobuilder retry old packages that failed on a regular basis, just > wait some time for them to do it. Some will try daily, other weekly and > other will retry when they have time for it. > > You could wait a week or so, and if the situation doesn't improve, > contact the autobuilder maintainer. > > Alternatively, you could login on a debian paroject machine, and build > the program yourself. The best way to ensure the correct debhelper version is used would be a new package with a versioned build dependency anyway IMHO. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast
Re: How to force porters to rebuild a package
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 for them to do it. Some will try daily, other weekly and > other will retry when they have time for it. > > You could wait a week or so, and if the situation doesn't improve, > contact the autobuilder maintainer. > > Alternatively, you could login on a debian paroject machine, and build > the program yourself. Or just upload a new version. -- Kind regards, ++ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: How to force porters to rebuild a package
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 whole week now[1], but it still hasn't been uploaded to the archive[2]. All other architectures have been uploaded. Drew [1] http://buildd.debian.org/build.php?pkg=xprint-xprintorg [2] http://ftp.debian.org/debian/pool/main/x/xprint-xprintorg/ -- PGP public key available at http://people.debian.org/~dparsons/drewskey.txt Fingerprint: A110 EAE1 D7D2 8076 5FE0 EC0A B6CE 7041 6412 4E4A pgp3Td8o86npm.pgp Description: PGP signature
Dependencies to special versions
-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 (= ${Source-Version}), foo-misc (= ${Source-Version})
...
Package: foo-misc
Depends: ${shlibs:Depends}
...
Package: foo-doc
...
-
When I have installed an old version, say foo-1.0-1 and its children
with the same version, foo will depend on foo-doc-1.0-1 and
foo-misc-1.0-1.
Now I create a new version 1.0-2 of all packages and try to upgrade.
apt-get will download the files and unpacks them. Before
configuration of foo-1.0-2 it complains that foo-doc and foo-misc are
not installed in the newer version. Moreover it can't upgrade them
because it would break the dependency of the installed foo-1.0-1.
My theory is that this kind of dependencies is insane, because on
update there is no way to upgrade everything in an atomic action
which would be necessary to keep all dependencies working all the
time. Is this correct?
The work around/fix I imagine is to just depend on the package without
any revision or use something like
Depends: foo-doc (>= ${Source-Version}), foo-misc (>=
${Source-Version})
Is this correct or how would I solve a 1-1 relation between several
packages?
Thnx in advance
Schimmi
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE9rsfJHUDhE+YrLEURAgDaAKDzsNV0j8Nw/Ge8DibKDoxwsTKE/ACfSKxU
es2SM5CJfZdtQ7dnj8H4B3A=
=JOGR
-END PGP SIGNATURE-
Re: How to force porters to rebuild a package
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 autobuilder retry old packages that failed on a regular basis, just > > wait some time for them to do it. Some will try daily, other weekly and > > other will retry when they have time for it. > > > > You could wait a week or so, and if the situation doesn't improve, > > contact the autobuilder maintainer. > > > > Alternatively, you could login on a debian paroject machine, and build > > the program yourself. > > Or just upload a new version. It may be right in this case as michel said, but in general i don't think being impatient with the autobuilders warrants the upload of a new version. Friendly, Sven Luther
Debhelper files w/ meta values
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 gives me the shivers to think about; is there any straightforward way to do this other than building the file from an m4 source or such? -- *** Joel Baker System Administrator - lightbearer.com [EMAIL PROTECTED] http://users.lightbearer.com/lucifer/ pgpWaDDIepVP4.pgp Description: PGP signature
Re: How to force porters to rebuild a package
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 other > architectures have been uploaded. I don't think you will be able to _force_ anybody to anything. But you could ask the porters (by writing to the mailing list of the particular port, for example) if too much time has passed (say, some weeks), to have a look at your problem. regards, Stefan -- > http://www.shockfrosted.org
未承諾広告※ 各種情報提供のご案内
<送信者> ワンダーライフ 佐久間 [EMAIL PROTECTED] 突然のメールの配信深くお詫び申し上げます。 これはWEB上にアドレスを公開されている方を対象に配信している広告 メールです。今後一切のメール配信不要の方はこのメールをそのまま ご返信ください。 掲示板に投稿するより効果的です！ ☆ ＤＭ用メールアドレス１５０万個 ☆ 宣伝の効果抜群！大好評！アクセス数の少ない掲示板では・・・ 国内のＤＭ用メールアドレスが１５０万個あります。 ご希望であれば、テキストファイルで下記に示す価格でお譲り致します。 なお、重複しているメールアドレスは有りませんが（これは非常に重要な ことです）、使用できなくなっているものは多少ございます。ですが、あ らかじめその不足分を十分考慮して割増してありますのでご安心下さい。 メールアドレスをご希望の方は、件名「メルアド希望」とメール下さい。 その際、ご希望個数と、当方の入金確認用のために代金振込時の 振込み名（カタカナ）をお知らせ下さい。 折り返し、メールアドレスリストを添付し、当方指定の代金振込先を ご連絡致します。 尚、転送時間短縮のために圧縮ファイル（パスワード暗号化）で お送り致します。 価格一覧： 1万件： 5,000円 5万件： 9,000円 10万件：12,000円 50万件：15,000円 150万件：20,000円 尚、全数お買い求め頂く方には、サービスでアドレス収集ソフトと ダブり削除ソフトも無料にて提供しております。 またこの他に、 ・携帯アドレスリスト：10,000円 （非番号約37万件分） ・ネットワーカー名簿：10,000円 （約10万名分［都道府県別］：住所＋氏名＋TEL） ・特選裏情報：5,000円 （実生活に役立つノウハウ等） ・芸能人情報：5,000円 （メルアド、本名、住所＋TEL、出身校、加入宗教団体） もございますので、ご希望の方はお問い合わせ下さい。 お問合せ先：ワンダーライフ [EMAIL PROTECTED] 山梨県北巨摩郡長坂町小荒間29-982 090-8494-3572
