/var/lib/transmission-daemon directory ownership
Hi. Now in debian squeeze ownership of /var/lib/transmission-daemon folder is set to 'root:root' $ ls -la /var/lib/transmission-daemon/ total 16 drwxr-xr-x 4 rootroot4096 Nov 1 13:41 . drwxr-xr-x 80 rootroot4096 Nov 1 13:41 .. drwsrwxr-x 2 debian-transmission debian-transmission 4096 Oct 19 2010 downloads drwsr-x--- 5 debian-transmission debian-transmission 4096 Nov 1 13:41 info but, i think, it should be set to 'debian-transmission:debian-transmission'. Also, i think that home folder of user 'debian-transmission' should also be set to '/var/lib/transmission-daemon' instead of '/home/debian-transmission'. What do you think about this? -- Dmitriy Matrosov -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAFdVUF=+b+Lm=Vabm6+vH_7SG9iKZDN_qXOM=xojnnducoa...@mail.gmail.com
Re: debian/rules binary and build target dependencies clarification
Thanks a lot for the explanation. 2011/10/10 Thibaut Paumard mlotpot.n...@free.fr: Hi, Le 08/10/11 19:51, Дмитрий Матросов a écrit : So, this means that there is no strict relationship between content of Build-Depends-* field and build-* target dependencies like: 'Build-Depends' field contains all dependencies for 'build-arch' target and nothing more, or 'Build-Depends-Indep' contains all dependencies for 'build-indep' target and nothing more. Am i understand you correctly? The idea is that architecture independent packages are not always built (actually, I believe they are _never_ automatically built, since they come with the source upload, and whatever binary package is uploaded with the source package is not rebuilt!) So Build-Depends-Indep should list those dependencies which only need to be installed to build the arch-indep packages, so that in the real-world situation where only the arch packages are built, those dependencies are not uselessly installed. On the other hand, there is no real-world use case to build _only_ arch-indep packages, without the arch packages. So both build-arch and build-indep can count on anything listed in Build-Depends. The theory (and I'm not sure of how it currently works in practice) is that the autobuilders, most of the time, install only Build-Depends on call only binary-arch. On the developer's machine however (or on a full rebuild), both Build-Depends and Build-Depends-Indep are installed, and both binary-arch and binary-indep are called. Regards, Thibaut. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e92a605.2010...@free.fr -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cafdvufnvjvnawcmdi7zhjgmlnvzw6ez9u2xyvl8cuax4_u1...@mail.gmail.com
Re: debian/rules binary and build target dependencies clarification
2011/10/7 Bernhard R. Link brl...@debian.org: * Дмитрий Матросов sgf@gmail.com [111007 16:27]: But in the section 7.7 of Debian policy manual: clean, build-arch, and binary-arch Only the Build-Depends and Build-Conflicts fields must be satisfied when these targets are invoked. build, build-indep, binary, and binary-indep The Build-Depends, Build-Conflicts, Build-Depends-Indep, and Build-Conflicts-Indep fields must be satisfied when these targets are invoked. And footnote 55: Anyone building the build-indep and binary-indep targets is assumed to be building the whole package, and therefore installation of all build dependencies is required. So, as i understand, in this case dependencies will look like binary : binary-arch binary-indep binary-indep : build-indep build-arch ? What you write here looks like makefile dependencies, i.e. like something written in debian/rules. In that sense it is obviously wrong. Nothing says you must have called build-arch to be able to run build-indep or binary-indep. All it says is that people are not required to add things to Build-Depends-Indep: which are already in Build-Depends:. So, this means that there is no strict relationship between content of Build-Depends-* field and build-* target dependencies like: 'Build-Depends' field contains all dependencies for 'build-arch' target and nothing more, or 'Build-Depends-Indep' contains all dependencies for 'build-indep' target and nothing more. Am i understand you correctly? P.S: Note that currently Build-Depends-Indep is not working as Debian is stalled in a decade old dream for a technical solution, so one has to put everything in Build-Depends anyway... Well, i just want to understand theory :) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cafdvufm4rhnwdt9--zydsl09ktqkfoskzxit38kc9_ucwn_...@mail.gmail.com
debian/rules binary and build target dependencies clarification
Hello. Not sure this is correct maillist, though. I can't clearly understand dependencies between debian/rules binary and build targets. Let's assume, that both 'build-arch' and 'build-indep' targets provided. In the Debian policy manual section 4.9 written: The build target should depend on those of the targets build-arch and build-indep that are provided in the rules file. .. binary may be (and commonly is) a target with no commands which simply depends on binary-arch and binary-indep. .. Both binary-* targets should depend on the build target, or on the appropriate build-arch or build-indep target, if provided,.. So, as i understand, this will look like binary : binary-arch binary-indep binary-arch : build-arch binary-indep : build-indep build : build-arch build-indep But in the section 7.7 of Debian policy manual: clean, build-arch, and binary-arch Only the Build-Depends and Build-Conflicts fields must be satisfied when these targets are invoked. build, build-indep, binary, and binary-indep The Build-Depends, Build-Conflicts, Build-Depends-Indep, and Build-Conflicts-Indep fields must be satisfied when these targets are invoked. And footnote 55: Anyone building the build-indep and binary-indep targets is assumed to be building the whole package, and therefore installation of all build dependencies is required. So, as i understand, in this case dependencies will look like binary : binary-arch binary-indep binary-indep : build-indep build-arch ? binary-arch : build-arch build : build-indep build-arch build-indep : build-arch? But the last one is wrong, isn't it? Thanks, Dmitriy Matrosov. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cafdvufnj2h+soj5wdwtsqzyf28hnfhwj75zb629bk6dpfkm...@mail.gmail.com
