Re: getting unstable lintian & linda into stable
Hi Christoph, On Friday, 11 Nov 2005, you wrote: > Maybe lintian could detect if if was running on stable when it should > be on unstable, and warn the user. I'm not sure how to do this, since > there are legitimate uses on stable where you wouldn't want to get the > warning. it could parse the changelog entry and try to detect if the upload is for stable-(security|proposed-updates). If not, and "APT prefers stable" (stolen from reportbug), lintian/linda could give a warning. This requires lintian/linda to run in the same enviroment than the package has been build (ie. a chroot). Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: getting unstable lintian & linda into stable
[Alexander Schmehl] > Curently it's quite easy to run unstables lintian, debootstrap and > pbuilder on system running stable for the other packages. So I don't > see a big problem creating and testing packages on a stable system. It would make more sense to me to run lintian *inside* pbuilder, then. Which I assume is what pdebuild does, not that I've looked at it closely to verify this. signature.asc Description: Digital signature
Re: getting unstable lintian & linda into stable
Hi, * Wouter Verhelst <[EMAIL PROTECTED]> [2005-11-11 23:41]: > Op vr, 11-11-2005 te 15:28 +0100, schreef Nico Golde: > > So what about a special exception which provides updated > > lintian & linda packages for the stable distribution? > > Doesn't sound like a particularly good idea to me. You need no just > unstable's linda/lintian; you also need unstable's libraries to be able > to make sure your package will work and build on unstable. There's no > way around that; there's way too many libraries that might have their > SONAME bumped, way too many packages that might have been split (or > merged) so that the packages you need to build-dep on in stable don't > exist anymore in unstable (or vice versa), etc. > > "Just" including linda/lintian in stable doesn't fix that. [...] Yes you are right. Should I file a wishlist bug against linda and lintian to answer for the described warning procedure? Regards Nico -- Nico Golde - JAB: [EMAIL PROTECTED] | GPG: 0x73647CFF http://www.ngolde.de | http://www.muttng.org | http://grml.org Forget about that mouse with 3/4/5 buttons - gimme a keyboard with 103/104/105 keys! pgpttGsaEbsmG.pgp Description: PGP signature
Re: getting unstable lintian & linda into stable
On Fri, Nov 11, 2005 at 03:28:31PM +0100, Nico Golde wrote: [...] > So what about a special exception which provides updated > lintian & linda packages for the stable distribution? > Is it technical possible? I mean becaused it should be > fixed. That's imho wrong idea because of at least one very important reason. Let's say that policy of unstable has changed and now it is required to put some kind of binaries in /foo/bar/, and lintian warns if you're going to put them in other place. It's possible that stable distribution even doesn't contain /foo/bar/ directory or some other needed tool which are now required in unstable. regards fEnIo -- ,''`. Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | irc:fEnIo : :' : 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Poland `. `' phone:+48602383548 | proud Debian maintainer and user `- http://skawina.eu.org | jid:[EMAIL PROTECTED] | rlu:172001 signature.asc Description: Digital signature
Re: getting unstable lintian & linda into stable
Op vr, 11-11-2005 te 15:28 +0100, schreef Nico Golde: > So what about a special exception which provides updated > lintian & linda packages for the stable distribution? Doesn't sound like a particularly good idea to me. You need no just unstable's linda/lintian; you also need unstable's libraries to be able to make sure your package will work and build on unstable. There's no way around that; there's way too many libraries that might have their SONAME bumped, way too many packages that might have been split (or merged) so that the packages you need to build-dep on in stable don't exist anymore in unstable (or vice versa), etc. "Just" including linda/lintian in stable doesn't fix that. > If not it would be great to add some kind of Warning to the > source code which checks the Debian versions and warns the > user that it is normally recommended to built on a newer > version. That could work. -- The amount of time between slipping on the peel and landing on the pavement is precisely one bananosecond -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: getting unstable lintian & linda into stable
Hi! * Nico Golde <[EMAIL PROTECTED]> [05 15:28]: > So what about a special exception which provides updated > lintian & linda packages for the stable distribution? > Is it technical possible? I mean becaused it should be > fixed. Curently it's quite easy to run unstables lintian, debootstrap and pbuilder on system running stable for the other packages. So I don't see a big problem creating and testing packages on a stable system. Yours sincerely, Alexander -- http://learn.to/quote/ http://www.catb.org/~esr/faqs/smart-questions.html signature.asc Description: Digital signature
Re: getting unstable lintian & linda into stable
On Fri, Nov 11, 2005 at 03:28:31PM +0100, Nico Golde wrote: > So what about a special exception which provides updated lintian & > linda packages for the stable distribution? Is it technical possible? > I mean becaused it should be fixed. It might not be necessary as an exception: perhaps the rule sets could be provided, in a seperate package, via volatile.debian.net ? > If not it would be great to add some kind of Warning to the source > code which checks the Debian versions and warns the user that it is > normally recommended to built on a newer version. I expect that could be implemented as a rule, and I think on it's own it is a good idea, as I often forget to make sure I'm in an unstable system when building packages. -- Jon Dowland http://jon.dowland.name/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: getting unstable lintian & linda into stable
Re: Nico Golde in <[EMAIL PROTECTED]> > So what about a special exception which provides updated > lintian & linda packages for the stable distribution? > Is it technical possible? I mean becaused it should be > fixed. This doesn't make sense. You need unstable to build on unstable, and only updating lintian and linda doesn't change that. > If not it would be great to add some kind of Warning to the > source code which checks the Debian versions and warns the > user that it is normally recommended to built on a newer > version. Maybe lintian could detect if if was running on stable when it should be on unstable, and warn the user. I'm not sure how to do this, since there are legitimate uses on stable where you wouldn't want to get the warning. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
getting unstable lintian & linda into stable
Hi, It seems that not every new maintainer is building a package on an unstable system which is recommended (or at least a version with the current policy version). So there are errors in packages which come to debian-mentors which are checked with an old version of the debian policy. So what about a special exception which provides updated lintian & linda packages for the stable distribution? Is it technical possible? I mean becaused it should be fixed. If not it would be great to add some kind of Warning to the source code which checks the Debian versions and warns the user that it is normally recommended to built on a newer version. Maybe this idea is crap but I think somehow it would be great to wanr users building on stable (not an error because of backports etc.) Regards Nico -- Nico Golde - JAB: [EMAIL PROTECTED] | GPG: 0x73647CFF http://www.ngolde.de | http://www.muttng.org | http://grml.org Forget about that mouse with 3/4/5 buttons - gimme a keyboard with 103/104/105 keys! pgpb2V6iDDmRu.pgp Description: PGP signature
