severity 334164 normal thanks > yada rebuilds the debian/control file when it is run, *AND* it goes and > *modifies* data in the first paragraph of it. > > This is *really* broken and should never be done, except by the > maintainer itself. The reason is simple: If its done automagically and > noone checks it, it can produce results which may break later, for > example in security updates.
If the security update is prapared with sane environment (in sarge system), there is no possibility to break the debian/control's Build-Dependencies. Please, tell me, how yada can break the package? I'm using this tool for years and it happened *never*. In fact, the Build-Depends are changed only for yada itself. If security update is prepared with wrong tool, the result will be also wrong. If updated is prepared with the proper environment, the result will be OK. My example - the phpmyadmin 2.6.2-3: autogenerated debian/control in original package: Build-Depends-Indep: yada (>= 0.34), po-debconf autoregenerated debian/control in sid environment: Build-Depends-Indep: yada (>= 0.48), po-debconf autogenerated debian/control in sarge environment (i.e. for security update) Build-Depends-Indep: yada (>= 0.34), po-debconf So, it is the same version as in original package. Everything is all right. -- .''`. Piotr Roszatycki, Netia SA : :' : mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
