Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.devel.release > #90567
| From | Raphael Hertzog <hertzog@debian.org> |
|---|---|
| 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-29 14:30 +0200 |
| Message-ID | <yArIS-5O8-13@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <yvRkB-8kK-1@gated-at.bofh.it> <yvRXj-mJ-7@gated-at.bofh.it> <yAncd-2NT-3@gated-at.bofh.it> <yAr69-5ka-7@gated-at.bofh.it> <yArzb-5KL-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
(Note: pkg-security@tracker.d.o is not a valid email, dropped) Hi, On Thu, 29 Aug 2019, Holger Levsen wrote: > > In general, we (Debian) don't have a good answer to this problem and > > virtualbox is clearly a bad precedent. We really need to find a solution > > to this in concertation with the release managers. > > so I've added them to this thread. > > youtube-dl is in the same boat... To kickstart the discussion, I can try to make a proposal. 1/ We tag such packages in some way (let's say a new field "Backport-Only: yes") 2/ Those packages are considered like others for testing migration but when britney accepts them, instead of adding them to "<testing-codename>" it adds them to "<testing-codename>-backports". Obviously this requires britney to consider the combination of both repositories when considering migrations. And it will require changes to generate two separate output files for dak. The hardest part is ensuring that testing doesn't contain packages that would depend on packages present only in the backports part. Not sure we want to handle this directly within britney. It might be better to have QA tools for this and report bugs as appropriate. The good thing is that those applications are then available from day 1 in stable-backports after the release. The backports rules would have to be tweaked a bit to accept backports coming out of "<testing>-backports". But all those aspects are a relatively minor detail IMO. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
Back to linux.debian.devel.release | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
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
csiph-web