Path: csiph.com!tncsrv06.tnetconsulting.net!newsfeed.endofthelinebbs.com!news.corradoroberto.it!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Matthias Klose Newsgroups: linux.debian.maint.java Subject: Re: gradle reboot -- 2024W49 update Date: Sat, 14 Dec 2024 13:20:01 +0100 Message-ID: References: X-Original-To: debian-java@lists.debian.org X-Mailbox-Line: From debian-java-request@lists.debian.org Sat Dec 14 12:11:53 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.698 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -2.7 Old-X-Envelope-From: doko@debian.org Old-X-Envelope-To: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Mailing-List: archive/latest/23564 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/ce7cef74-2aaf-40b0-8256-8f1ed009703b@debian.org Approved: robomod@news.nic.it Lines: 14 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sat, 14 Dec 2024 13:11:37 +0100 X-Original-Message-ID: X-Original-References: <5284bacb294ba1ff08f32a5a0b175dd4@free.fr> <8497785db64c2691266dc8269486d7c2@free.fr> <2c092ca6-5614-0eed-ea71-a1ffbb82cc2d@apache.org> <2db594d17e58f30adcba8b06a2fe0415@free.fr> <6ca68dd7-9da4-4f9f-82d9-b13b622107d9@debian.org> Xref: csiph.com linux.debian.maint.java:12857 On 14.12.24 11:49, sre4ever@free.fr wrote: > Le 2024-12-14 10:48, Matthias Klose a écrit : >> >> what about having two sets of packages? one set encapsulating the >> bootstrap, which always stays in unstable, and one "production" set, >> which then migrates to testing? Would that be better to keep the >> bootstrap knowledge up to date? > > That's a possibility, though I would keep them in the same repo and > manage them using branches, and maybe keep the bootstrap packages only > in experimental. experimental is fine, as long as there are no architecture dependent packages involved. re-bootstrapping then in unstable is a pain.