Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.security > #5677
| From | Alexander Wirt <formorer@formorer.de> |
|---|---|
| Newsgroups | linux.debian.devel.release, linux.debian.security |
| Subject | Re: how to deal with widely used packages unsuitable for stable (was Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments.) |
| Date | 2019-08-30 22:10 +0200 |
| Message-ID | <yAVnz-8ps-1@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <yAJmp-ou-3@gated-at.bofh.it> <yAJFL-vn-3@gated-at.bofh.it> <yAKVd-1ew-43@gated-at.bofh.it> <yAL4R-1za-7@gated-at.bofh.it> <yAQnU-4Xu-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
On Fri, 30 Aug 2019, Raphael Hertzog wrote: > Hi, > > On Fri, 30 Aug 2019, Alexander Wirt wrote: > > > We're not speaking of crap software, we're just speaking of software that > > > can't be maintained multiple years by backports of security patches, where > > > we get fixes only with new upstream versions (mixed with new features). > > I don't want to draw that line, someone would have decide if the software is > > just crap, the maintainer too lazy or if its really fast pacing. Wordpress is > > an example of a software that should really be supported within stable. If > > not its just crap. > > > > Imho we should have packages in testing that will not be part of the next > > release. And we don't want any form of automated migrations. Full stop. > > People should build and *test* their packages against stable. > > I don't know if I'm expressing myself very badly, but there's clearly a > misunderstanding. > > Right now there is no "stable" release where you would build packages for > bullseye-backports. If you keep the same logic of building next release > packages against the current release, then for bullseye-backports that > would mean building packages from unstable in a testing environment. I have a problem with your definition(s). There is no bullseye-backports yet and it will only be available short before its release. Backports is meaned to support a stable release. Alex
Back to linux.debian.security | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments. Holger Levsen <holger@layer-acht.org> - 2019-08-16 22:50 +0200
Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments. Markus Koschany <apo@debian.org> - 2019-08-16 23:30 +0200
Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments. Moritz Mühlenhoff <jmm@inutil.org> - 2019-08-29 09:40 +0200
Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments. Raphael Hertzog <hertzog@debian.org> - 2019-08-29 13:50 +0200
how to deal with widely used packages unsuitable for stable (was Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments.) Holger Levsen <holger@layer-acht.org> - 2019-08-29 14:20 +0200
Re: how to deal with widely used packages unsuitable for stable (was Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments.) Raphael Hertzog <hertzog@debian.org> - 2019-08-29 14:30 +0200
Re: how to deal with widely used packages unsuitable for stable (was Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments.) Paul Gevers <elbrus@debian.org> - 2019-08-29 15:20 +0200
Re: how to deal with widely used packages unsuitable for stable (was Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments.) Dan Clery <dan@savevsgeek.com> - 2019-08-29 16:40 +0200
Re: how to deal with widely used packages unsuitable for stable (was Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments.) Raphael Hertzog <hertzog@debian.org> - 2019-08-30 09:20 +0200
Re: how to deal with widely used packages unsuitable for stable (was Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments.) Alexander Wirt <formorer@formorer.de> - 2019-08-30 09:40 +0200
Re: how to deal with widely used packages unsuitable for stable (was Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments.) Raphael Hertzog <hertzog@debian.org> - 2019-08-30 11:00 +0200
Re: how to deal with widely used packages unsuitable for stable (was Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments.) Alexander Wirt <formorer@formorer.de> - 2019-08-30 11:10 +0200
Re: how to deal with widely used packages unsuitable for stable (was Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments.) Raphael Hertzog <hertzog@debian.org> - 2019-08-30 16:50 +0200
Side issue/question -- {Re: how to deal with widely used packages ...} Richard Owlett <rowlett@cloud85.net> - 2019-08-30 17:20 +0200
Re: how to deal with widely used packages unsuitable for stable (was Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments.) Alexander Wirt <formorer@formorer.de> - 2019-08-30 22:10 +0200
Re: how to deal with widely used packages unsuitable for stable (was Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments.) Moritz Mühlenhoff <jmm@inutil.org> - 2019-08-30 10:20 +0200
Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments. Moritz Mühlenhoff <jmm@inutil.org> - 2019-09-04 21:40 +0200
csiph-web