Build-Depends-Indep dependencies
Sorry for the lame question, but I couldn't find an explanation of difference between Build-Depends and Build-Depends-Indep in Debian manuals. Can anybody explain when Build-Depends-Indep is required? -- anatoly t. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktiktmx1v5ufl6lk-6gjcatpzaorudmjo06ngw...@mail.gmail.com
Re: Build-Depends-Indep dependencies
On Tue, Oct 26, 2010 at 09:34, anatoly techtonik wrote: > Sorry for the lame question, but I couldn't find an explanation of > difference between Build-Depends and Build-Depends-Indep in Debian > manuals. Can anybody explain when Build-Depends-Indep is required? look it up on Debian Policy - and questions like this should be sent to debian-mentors: there's nothing python specify here. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=xcw6rtft31nk1wm0fp95wzq=gpf2yriv7g...@mail.gmail.com
Re: Build-Depends-Indep dependencies
On Tue, Oct 26, 2010 at 10:40 AM, Sandro Tosi wrote: >> Sorry for the lame question, but I couldn't find an explanation of >> difference between Build-Depends and Build-Depends-Indep in Debian >> manuals. Can anybody explain when Build-Depends-Indep is required? > > look it up on Debian Policy - and questions like this should be sent > to debian-mentors: there's nothing python specify here. I expected smb. to tell me that Python applications doesn't need Build-Depends-Indep, because ... Now I ought to educate myself about autotools, makefiles and all that low level stuff that I don't really care about when writing in Python. There are good chances that I won't do this, and as a result won't be able to help you in maintaining. -- anatoly t. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikchmejfsoes0be112_baaaempxeki8vos0k...@mail.gmail.com
Re: Build-Depends-Indep dependencies
On Tue, Oct 26, 2010 at 10:16, anatoly techtonik wrote: > On Tue, Oct 26, 2010 at 10:40 AM, Sandro Tosi wrote: >>> Sorry for the lame question, but I couldn't find an explanation of >>> difference between Build-Depends and Build-Depends-Indep in Debian >>> manuals. Can anybody explain when Build-Depends-Indep is required? >> >> look it up on Debian Policy - and questions like this should be sent >> to debian-mentors: there's nothing python specify here. > > I expected smb. to tell me that Python applications doesn't need > Build-Depends-Indep, because ... and I expected you to use google, find what b-d and b-d-i are, try to understand what's their use-case and in case of doubt ask here (if it's a strictly python question) or on debian-mentors (if it's a general questions) - unmatched expectation it seems. Ah, you can also look at what other packages does - it's a very good way to learn "how to package". > Now I ought to educate myself about autotools, makefiles and all that > low level stuff that I don't really care about when writing in Python. > There are good chances that I won't do this, and as a result won't be > able to help you in maintaining. ahah nice try - f.e. why would you need to "educate" yourself about autotools? it's a non sequitur from b-d vs b-d-i question: care to explain? Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikz4+gout=nqdvniu0w-9oo7hjfsnsxrgh=r...@mail.gmail.com
Re: Build-Depends-Indep dependencies
On Tue, Oct 26, 2010 at 11:28 AM, Sandro Tosi wrote: > On Tue, Oct 26, 2010 at 10:16, anatoly techtonik wrote: >> On Tue, Oct 26, 2010 at 10:40 AM, Sandro Tosi wrote: Sorry for the lame question, but I couldn't find an explanation of difference between Build-Depends and Build-Depends-Indep in Debian manuals. Can anybody explain when Build-Depends-Indep is required? >>> >>> look it up on Debian Policy - and questions like this should be sent >>> to debian-mentors: there's nothing python specify here. >> >> I expected smb. to tell me that Python applications doesn't need >> Build-Depends-Indep, because ... > > and I expected you to use google, find what b-d and b-d-i are, try to > understand what's their use-case and in case of doubt ask here (if > it's a strictly python question) or on debian-mentors (if it's a > general questions) - unmatched expectation it seems. I used Google to find http://www.debian.org/doc/debian-policy/ch-relationships.html#s-sourcebinarydeps It doesn't explain the terminology. > Ah, you can also look at what other packages does - it's a very good > way to learn "how to package". I'm already trying to understand the packaging of trac-bitten - that's why these questions. >> Now I ought to educate myself about autotools, makefiles and all that >> low level stuff that I don't really care about when writing in Python. >> There are good chances that I won't do this, and as a result won't be >> able to help you in maintaining. > > ahah nice try - f.e. why would you need to "educate" yourself about > autotools? it's a non sequitur from b-d vs b-d-i question: care to > explain? Because from Debian Policy I understand that Build-Depends-Indep affects some rules in debian/rules. This file is a Makefile. I remember that Makefiles in *nix systems were usually produced with some kind of autotools. Even though the policy doesn't explain what Build-Depends-Indep is, it says that Build-Depends-Indep should be present for these Makefile targets: build, build-indep, binary, and binary-indep But there are no such targets in trac-bitten debian/rules file, so I assume that some kind of autotools is used to execute/supply these targets when debian/rules is executed. As a Windows Python user, who just want to see new Bitten package in Debian to upload the package to production server, I can't really go into the gory details of Debian toolchains. It already takes more time than I could allow. -- anatoly t. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikrlrtqym37miqbnlce3irxettgfn9jj3fom...@mail.gmail.com
Re: Build-Depends-Indep dependencies
Hello, Anatoly, in fact, I understand that you are mainly asking for general packaging practice details. Have you looked at http://www.debian.org/doc/maint-guide/ which does a fairly good job at explaining the basics of Debian package preparation, and which is certainly the most appropriate gate to making correct Debian packages. Section http://www.debian.org/doc/maint-guide/ch-dreq.en.html#control will enlighten you about Build-Depends-Indep use. Roughly, one way to figure out if you need to specify something in that field is to ask yourself these questions in order : 1. Is my software dependent on the computer architecture (compiled source code), or is the source code interpreted so that it will run unmodified on all architectures ? 2. In case the source code is interpreted (like by the Python interpreter), is that code (in the form of modules or packages) requiring any particular software to be built ? If yes, you need to specify the name (and version, if necessary) of the Debian package that ships that software. If no, you do not need to fill that field. One example would be that one particular Python library would be required for your building of the software. That would be platform-independent software, but still you would require, when building you software that specific package. However, please, note that these are general packaging questions which should be posted on other mailing lists. In order for your questions to be well received by the Debian community (which is full of people willing to help), you should really make sure you have read the basic documents about packaging (not only Python stuff *all stuff* because packaging software for Debian requires an extensive understanding of how software works, not just Python scripts : any software). Also, when posting a question, please do refer to your readings by saying, for example, that you read some relevant documentation but could not find any answer to your specific question. A list of useful developer lists is located at http://lists.debian.org/devel.html, along with an easy subscription system. Finally, just a suggestion : do not state that you do not want to do this and this and that learning this and this is not useful... That kind of behaviour will call for sarcasm from Debianists, precisely because they became Debianists by not thinking the way you did in a previous mail. Makefile is the name of file which are understood by a program which is called 'make'. Makefiles are generated by a number of build systems, amongst which the autotools (GNU project), CMake, and others. It's good to see you are willing to help, but you may want to read some basics docs first. For example, have a look at http://www.gnu.org/software/make/manual/ No need to understand *everything* at first reading!! You just need to get the general picture. Do this for many docs and you'll get a useful sight on what programs are and how they should be dealt with in Debian packaging. I hope you will consider Debian as a wonderful "self-development platform", as the community is generous ; but you should try to be so also. Cheers, Filippo On Tue, Oct 26, 2010 at 01:03:32PM +0300, anatoly techtonik wrote: > > On Tue, Oct 26, 2010 at 11:28 AM, Sandro Tosi wrote: > > On Tue, Oct 26, 2010 at 10:16, anatoly techtonik > > wrote: > >> On Tue, Oct 26, 2010 at 10:40 AM, Sandro Tosi wrote: > Sorry for the lame question, but I couldn't find an explanation of > difference between Build-Depends and Build-Depends-Indep in Debian > manuals. Can anybody explain when Build-Depends-Indep is required? > >>> > >>> look it up on Debian Policy - and questions like this should be sent > >>> to debian-mentors: there's nothing python specify here. > >> > >> I expected smb. to tell me that Python applications doesn't need > >> Build-Depends-Indep, because ... > > > > and I expected you to use google, find what b-d and b-d-i are, try to > > understand what's their use-case and in case of doubt ask here (if > > it's a strictly python question) or on debian-mentors (if it's a > > general questions) - unmatched expectation it seems. > > I used Google to find > http://www.debian.org/doc/debian-policy/ch-relationships.html#s-sourcebinarydeps > It doesn't explain the terminology. > > > Ah, you can also look at what other packages does - it's a very good > > way to learn "how to package". > > I'm already trying to understand the packaging of trac-bitten - that's > why these questions. > > >> Now I ought to educate myself about autotools, makefiles and all that > >> low level stuff that I don't really care about when writing in Python. > >> There are good chances that I won't do this, and as a result won't be > >> able to help you in maintaining. > > > > ahah nice try - f.e. why would you need to "educate" yourself about > > autotools? it's a non sequitur from b-d vs b-d-i question: care to > > explain? > > Because from Debian Policy I understand that Build-De
Re: Build-Depends-Indep dependencies
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/26/2010 12:03 PM, anatoly techtonik wrote: Ah, you can also look at what other packages does - it's a very good >> way to learn "how to package". > > I'm already trying to understand the packaging of trac-bitten - that's > why these questions. > >>> Now I ought to educate myself about autotools, makefiles and all that >>> low level stuff that I don't really care about when writing in Python. >>> There are good chances that I won't do this, and as a result won't be >>> able to help you in maintaining. >> >> ahah nice try - f.e. why would you need to "educate" yourself about >> autotools? it's a non sequitur from b-d vs b-d-i question: care to >> explain? > > Because from Debian Policy I understand that Build-Depends-Indep > affects some rules in debian/rules. This file is a Makefile. I > remember that Makefiles in *nix systems were usually produced with > some kind of autotools. > > Even though the policy doesn't explain what Build-Depends-Indep is, it > says that Build-Depends-Indep should be present for these Makefile > targets: > build, build-indep, binary, and binary-indep > > But there are no such targets in trac-bitten debian/rules file, so I > assume that some kind of autotools is used to execute/supply these > targets when debian/rules is executed. As a Windows Python user, who > just want to see new Bitten package in Debian to upload the package to > production server, I can't really go into the gory details of Debian > toolchains. It already takes more time than I could allow. I don't mind that beginners in packaging have write access to our repositories, assuming that they're willing to learn the necessary details during their work within the team. But as you're neither willing to learn how packaging software for Debian works, nor you seem to know the necessary basics like makefiles, I've removed your write access to the Python teams' repositories. Of course you are still welcome to update packages, please send the according patches to me and I'll apply them. - -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJMxsVBAAoJEOs2Fxpv+UNfS+kP/21iwx2EwtpfiBX2xXwYSWWL PqcWTBPFKZoZ7AMmGzOLXVQDtPWPZjJ4P826tE+1j7yeZ9BSP6KaMRjjoh9mRgni 9Vp0e0elkE4D0m0fUOHHro5i9wrvzSttotYtyt4C1ZTU+effAzLAZFzsBSDY5dsJ WyEFW4/G3ezQ3dz6yUkbJM2QOOnLWOnwX4GtMXW54jl2R3shzwezF4dpRObK+n4x zk68ma5QrZokZEFhcDX/WhRMwCkAa16w1ap6eiP7QProEdwG5eFqo6TtCjeAahHu 9fkiU0NmPn1eJiVKVdgpTQG4rbOzz7hWejuhnzi0L1biZZHdWQj6Eaw59peQIZnd 924ffDQR4QPNaELZSS5XIP5/GASUY89sHp7CVyPFSKNCOBbxs12+cOqcwAIf5J26 u07o+pP/GfqCkfKAOhA7bhLg19S5e/gXgnKZDPG5Qy3Sh1T0mC++B1EtFXNwnVz+ wPwb7QQtV75jQ0fKIn+S5bww7eKT4lE5GH8rPQoSLIK15r2/rNPwiRmOm3hBX/P8 idia4FFeQ9aTVX/rRm8vg6/jdx+QCm7EOZTFGGvmUSY5ZNzdKxr09Y3jwujOMH7y 37Dq5Dhb+f31tO+ZMccF7C+NP7y7EsiUR/U05AOGi4k+7uPeFxiVdAJz59bW44aP djVepuWmFcY3FOEnv8eg =7084 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cc6c544.9030...@debian.org
Re: Build-Depends-Indep dependencies
On Tue, Oct 26, 2010 at 1:56 PM, Filippo Rusconi wrote: > > in fact, I understand that you are mainly asking for general packaging > practice details. Have you looked at > > http://www.debian.org/doc/maint-guide/ > > which does a fairly good job at explaining the basics of Debian > package preparation, and which is certainly the most appropriate gate > to making correct Debian packages. The size of this doc is about 100kB. The average reading speed is about 200 word per minute or about 1.5kB that will about 1 hour for non-technical text. Maint-guide is full of technical details, there are many references to Debian Policy and other docs, you also want to test examples, lookup unknown terms in Wikipedia, so the reading speed drops from 1 to 3-16 hours per manual (depending on your familiarity with unix). Another problem is that I've read it already several months ago, but I didn't need to understand Build-Depends-Indep and rereading this stuff from scratch is kind of ineffective in the end. So, the idea of the previous paragraph is that there should be another entrypoint that explains meaning to people, who primarily use Python rather than for people who primarily use unix. > Section > > http://www.debian.org/doc/maint-guide/ch-dreq.en.html#control > > will enlighten you about Build-Depends-Indep use. Thanks. I've missed this, it helps a little, but not much. Its first attempt to explain Build-Depends-Indep references to Policy 7.7 (which doesn't explain). The second explanation is "Build-Depends-indep is rarely used" and it obviously doesn't explain anything too. Third attempt tells that Build-Depends-Indep may or may not be used to specify packages with "Architecture: all" if they are not "listed in Build-Depends field to satisfy the Debian Policy requirement for the clean target". This sends to Google for Debian Policy requirement for the clean target, but doesn't explain this requirement. Just one more confusing indirection. > Roughly, one way to figure out if you need to specify something in > that field is to ask yourself these questions in order : > > 1. Is my software dependent on the computer architecture (compiled > source code), or is the source code interpreted so that it will run > unmodified on all architectures ? Well, I don't know if Python bytecode could be run unmodified on all architectures. Can it? But I guess Python packages don't ship compiled bytecode, and pure Python packages can run on "all architectures" as well as on "any architecture". What's the difference? From main-guide Build-Depends-Indep is only used with "Architecture: all", but why? > 2. In case the source code is interpreted (like by the Python > interpreter), is that code (in the form of modules or packages) > requiring any particular software to be built ? If yes, you need to > specify the name (and version, if necessary) of the Debian package > that ships that software. If no, you do not need to fill that > field. One example would be that one particular Python library would > be required for your building of the software. That would be > platform-independent software, but still you would require, when > building you software that specific package. You describe Build-Depends record - this one is pretty clear, but what about Build-Depends-Indep? > However, please, note that these are general packaging questions which > should be posted on other mailing lists. In order for your questions > to be well received by the Debian community (which is full of people > willing to help), you should really make sure you have read the basic > documents about packaging (not only Python stuff *all stuff* because > packaging software for Debian requires an extensive understanding of > how software works, not just Python scripts : any software). I understand that I need to read all the stuff and there are specialized lists. The problem that I feel depressed going through this book pile just to be able to bump a version number in small Python package I support in my free time. This is what I'd like to see changed if you want more useful packages in Debian like I do. > A list of useful developer lists is located at > http://lists.debian.org/devel.html, along with an easy subscription > system. ..no search and a lot of spam. =) > Finally, just a suggestion : do not state that you do not want to do > this and this and that learning this and this is not useful... That > kind of behaviour will call for sarcasm from Debianists, precisely > because they became Debianists by not thinking the way you did in a > previous mail. There wasn't so much text back in time, Python folks don't have to use Ubuntu, and Ubuntu didn't encourage people to contribute to Debian first. Back in time there wasn't so many things going on, so you can spend weeks studying exciting Debian infrastructure. I am not skipping rules that everybody is forced to obey - I just don't understand some things that are not clearly explained, and if it causes sarcasm i
Re: Build-Depends-Indep dependencies
On Tue, Oct 26, 2010 at 3:10 PM, Bernd Zeimetz wrote: > > I don't mind that beginners in packaging have write access to our > repositories, > assuming that they're willing to learn the necessary details during their work > within the team. But as you're neither willing to learn how packaging software > for Debian works, nor you seem to know the necessary basics like makefiles, > I've > removed your write access to the Python teams' repositories. You seem to read it the way you wanted. If I wasn't willing to learn how packaging software works, I've didn't read much about it already and asked some really dumb stuff. Even though I've apologized for the lame question, the thing I asked was quite complicated concept nobody was able to explain so far, and I still expect some on-topic ideas from this discussion. If you are fighting for justice then make an exam to test the knowledge of Build-Depends-Indep and revoke access for everybody who don't understand this. I am willing to elaborate on questionnaire form. =) I know basics about Makefiles - I know that target is and what 4-space indents from PEP-8 are unwelcome there. But Debian Policy tells that debian/rules should contain build-indep target for Build-Depends-Indep, and there is no such rule in trac-bitten. > Of course you are still welcome to update packages, please send the according > patches to me and I'll apply them. Ok. Can you upload edited trac-bitten package for previous version right now, before I send you patch for newer version? -- anatoly t. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikpqzo2dff2lkbztu6ebdrxwwt+4h8dvu1px...@mail.gmail.com
Re: Build-Depends-Indep dependencies
anatoly techtonik wrote: > I know basics about Makefiles - I know that target is and what 4-space > indents from PEP-8 are unwelcome there. But Debian Policy tells that > debian/rules should contain build-indep target for ^^ > Build-Depends-Indep, and there is no such rule in trac-bitten. Yes. "Should" is not "must". OdyX -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ia6uk0$a...@dough.gmane.org
Re: Build-Depends-Indep dependencies
On Tue, Oct 26, 2010 at 7:09 PM, Tristan Seligmann wrote: > On Tue, Oct 26, 2010 at 5:35 PM, anatoly techtonik > wrote: >> many places outdated (email-based bug-trackers, ML without search, > > FWIW: http://lists.debian.org/search.html Cool. Why Python Application Team list is not there? http://lists.alioth.debian.org/mailman/listinfo/python-apps-team -- anatoly t. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimsmx1ofy_ngpfpredfhyj81bz8q==znwqr9...@mail.gmail.com
Re: Build-Depends-Indep dependencies
On Tue, Oct 26, 2010 at 7:12 PM, Didier 'OdyX' Raboud wrote: > anatoly techtonik wrote: > >> I know basics about Makefiles - I know that target is and what 4-space >> indents from PEP-8 are unwelcome there. But Debian Policy tells that >> debian/rules should contain build-indep target for > ^^ > >> Build-Depends-Indep, and there is no such rule in trac-bitten. > > Yes. "Should" is not "must". Ok, but then Build-Depends-Indep doesn't make sense without build-indep target. Why it is present in debian/rules in trac-bitten? Another side is that Build-Depends should not be processed, because there is no build target also. But there is trac-bitten binary package, so the build process somehow works. This kind of magic is not explained in debian policy, and I am unable to see how this magic works to tell if Build-Depends-Indep should be dropped. -- anatoly t. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimuw-5dadwtaebwwx_o5ygexansyn0hjxaju...@mail.gmail.com
Re: Build-Depends-Indep dependencies
On Tue, Oct 26, 2010 at 5:35 PM, anatoly techtonik wrote: > many places outdated (email-based bug-trackers, ML without search, FWIW: http://lists.debian.org/search.html -- mithrandi, i Ainil en-Balandor, a faer Ambar -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktik1crswhtliccfsk=ht2cquremwnjkeuwxau...@mail.gmail.com
Re: Build-Depends-Indep dependencies
On 10/26/2010 06:04 PM, anatoly techtonik wrote: > On Tue, Oct 26, 2010 at 3:10 PM, Bernd Zeimetz wrote: >> >> I don't mind that beginners in packaging have write access to our >> repositories, >> assuming that they're willing to learn the necessary details during their >> work >> within the team. But as you're neither willing to learn how packaging >> software >> for Debian works, nor you seem to know the necessary basics like makefiles, >> I've >> removed your write access to the Python teams' repositories. > > You seem to read it the way you wanted. If I wasn't willing to learn > how packaging software works, I've didn't read much about it already > and asked some really dumb stuff. Even though I've apologized for the > lame question, the thing I asked was quite complicated concept nobody > was able to explain so far, and I still expect some on-topic ideas > from this discussion. > > If you are fighting for justice then make an exam to test the > knowledge of Build-Depends-Indep and revoke access for everybody who > don't understand this. I am willing to elaborate on questionnaire > form. =) > > I know basics about Makefiles - I know that target is and what 4-space > indents from PEP-8 are unwelcome there. But Debian Policy tells that > debian/rules should contain build-indep target for > Build-Depends-Indep, and there is no such rule in trac-bitten. I don't want to fight for anything, but I want to ensure that the packages in the teams stay in a proper shape. And I don't mind adding you again very soon when I'm sure that you know what you're doing. Actually there is a binary-indep rule in debian/rules, although it is well hidden as it uses cdbs to build the package. cdbs is probably the worst thing ever to learn packaging with... but if you follow the included files include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/class/python-distutils.mk you'll see that everything is there. >> Of course you are still welcome to update packages, please send the according >> patches to me and I'll apply them. > > Ok. Can you upload edited trac-bitten package for previous version > right now, before I send you patch for newer version? I could upload it to experimental. As Testing is frozen I'm not going to upload stuff to unstable as it would block pushing updates to the package via unstable into testing. But the current changes do not really warrant an upload, they're nice but don't change anything on the resulting package. So the best would be if you'd prepare the upload of the new version directly. Cheers, Bernd -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cc6ff41.8050...@debian.org
Re: Build-Depends-Indep dependencies
On Tue, Oct 26, 2010 at 6:16 PM, anatoly techtonik wrote: > On Tue, Oct 26, 2010 at 7:09 PM, Tristan Seligmann > wrote: >> On Tue, Oct 26, 2010 at 5:35 PM, anatoly techtonik >> wrote: >>> many places outdated (email-based bug-trackers, ML without search, >> >> FWIW: http://lists.debian.org/search.html > > Cool. Why Python Application Team list is not there? > http://lists.alioth.debian.org/mailman/listinfo/python-apps-team lists.alioth.debian.org is separate infrastructure to lists.debian.org, unfortunately. -- mithrandi, i Ainil en-Balandor, a faer Ambar -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikb4csmwl8vw8mzkdshba3yvm5r2+oy4c=by...@mail.gmail.com
how to search mailinglist archives [was: Re: Build-Depends-Indep dependencies]
On Tue, Oct 26, 2010 at 06:27:49PM +0200, Tristan Seligmann wrote: > On Tue, Oct 26, 2010 at 6:16 PM, anatoly techtonik > wrote: > > Cool. Why Python Application Team list is not there? > > http://lists.alioth.debian.org/mailman/listinfo/python-apps-team > > lists.alioth.debian.org is separate infrastructure to > lists.debian.org, unfortunately. Since most lists provide an open web archive one could try e.g. Google and limit the search scope with 'site:lists.alioth.debian.org' a bit. Or download all the mbox files from the list of your choice and use grep. Sven -- And I don't know much, but I do know this: With a golden heart comes a rebel fist. [ Streetlight Manifesto - Here's To Life ] -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101026171115.ga13...@marvin.lan
