Your message dated Thu, 28 Nov 2024 20:54:51 +0100 with message-id <84326f86-edd7-4904-a765-e3218e1bd595@debian.org> and subject line Re: Bug#1084900: transition: ppp has caused the Debian Bug report #1084900, regarding transition: ppp to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1084900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084900 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: transition: ppp
- From: Chris Boot <bootc@debian.org>
- Date: Thu, 10 Oct 2024 16:58:47 +0100
- Message-id: <172857592714.3194008.8517894278695825616.reportbug@dietrich.boo.tc>
Package: release.debian.org Severity: normal X-Debbugs-Cc: ppp@packages.debian.org Control: affects -1 + src:ppp User: release.debian.org@packages.debian.org Usertags: transition Hello Release Team friends, I have uploaded ppp 2.5.1-1+1~exp1 to experimental today, and have been testing it locally for a while prior to this. It's only a patch release, but all upstream releases require a transition due to other packages building plugins for it and the ABI being unstable. As usual this isn't a traditional library package upload so the Ben file looks a bit foreign. Thanks, Chris Ben file: title = "ppp"; is_affected = .build-depends ~ /ppp-dev/; is_good = .depends ~ /ppp \(>= 2\.5\.1-1\+~\)/ | .breaks ~ /ppp \(<< 2\.5\.1-1\+~\)/; is_bad = .depends ~ /ppp \(>= 2\.5\.0-1\+~\)/ | .breaks ~ /ppp \(<< 2\.5\.0-1\+~\)/;
--- End Message ---
--- Begin Message ---
- To: Chris Boot <bootc@debian.org>, 1084900-done@bugs.debian.org
- Subject: Re: Bug#1084900: transition: ppp
- From: Emilio Pozuelo Monfort <pochu@debian.org>
- Date: Thu, 28 Nov 2024 20:54:51 +0100
- Message-id: <84326f86-edd7-4904-a765-e3218e1bd595@debian.org>
- In-reply-to: <[🔎] 78157c5d-3e70-48f4-8dd3-7cb136edb429@debian.org>
- References: <172857592714.3194008.8517894278695825616.reportbug@dietrich.boo.tc> <172857592714.3194008.8517894278695825616.reportbug@dietrich.boo.tc> <ZwrovEvH8MTyT_re@ramacher.at> <[🔎] 01622f5f-7a50-4061-bbcb-93ac4ec48938@debian.org> <[🔎] 2fd9f38f-8d21-4066-a46f-f6d9cb98c113@debian.org> <[🔎] 53ac2fb8-8392-43c9-bfb6-e098f68da07c@debian.org> <[🔎] b982c299-736a-4b6a-ab86-0687e9980af6@debian.org> <[🔎] 78157c5d-3e70-48f4-8dd3-7cb136edb429@debian.org>
On 27/11/2024 08:53, Emilio Pozuelo Monfort wrote:On 26/11/2024 11:20, Chris Boot wrote:Hi, On 22/11/2024 15:30, Chris Boot wrote:On 22/11/2024 14:45, Chris Boot wrote:I'll try to run a few rebuilds this weekend and upload.I have now successfully rebuilt all the level-1 rdeps in a local test environment, and then uploaded 2.5.1-1+1 to sid.Please could you trigger binNMU rebuilds of the dependent packages in sid?Scheduled.I hinted it due to an autopkgtest failure due to the broken python3-apt, and it (ppp) has migrated. Closing this.Cheers, Emilio
--- End Message ---