[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#991947: marked as done (apt-setup: Consider adding $codename-updates configuration to /etc/apt/sources.list (if available even if yet $codename is testing))

Your message dated Tue, 25 Apr 2023 23:04:00 +0000
with message-id <E1prRhY-001Qow-Ls@fasolo.debian.org>
and subject line Bug#991947: fixed in apt-setup 1:0.180
has caused the Debian Bug report #991947,
regarding apt-setup: Consider adding $codename-updates configuration to /etc/apt/sources.list (if available even if yet $codename is testing)
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.)


-- 
991947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991947
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: apt-setup
Version: 1:0.166
Severity: wishlist
Tags: d-i
X-Debbugs-Cc: carnil@debian.org

Dear Debian Install System Team,

When installing bullseye with the current RC3 I noticed that while the
debconf menu suggests (and has selected) to add release updates suites
($codename-updates) to the sources.list in case when bullseye is yet
testing, they are not added via generators/92updates because
generators/90services-select in case of the suite not beeng stable or
odstable, does not select it:

updates=y
if [ "$suite" != stable ] && [ "$suite" != oldstable ]; then
        disable_service updates || true
        updates=n
fi

I wonder if this could be handled in times before a stable release is
planned, and the suite is already present on the mirrors (this is at
some time before a stable release prepartion when release team starts to
interact with infrastructure teams I think to setup what is needed for
the next stable release)

The reason I ask this, is that the coverage would be bigger for people
having it in the sources.list if they install it in time shortly before
a stable release is released, and we strongly rely on updates to be
possible to push via the stable-updates mechanism, see for instance
https://lists.debian.org/debian-stable-announce/2021/06/msg00001.html ?

Cyril mentioned two ideas how this can be done. Either having a flag
which can be enabled one we switch from an Alpha  to some RC Release for
d-i once the installer matured enough and infrastructure is set up in
perspective of a future stable release.

One other alternative would be to do an online test if the suite is
already present and only add it in that case.

What do you think of this idea? If you think it's nonsense, feel free to
mark it straight as wontfix and close it.

Regards,
Salvatore

--- End Message ---
--- Begin Message --- 
Source: apt-setup
Source-Version: 1:0.180
Done: Cyril Brulebois <kibi@debian.org>

We believe that the bug you reported is fixed in the latest version of
apt-setup, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 991947@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois <kibi@debian.org> (supplier of updated apt-setup package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 26 Apr 2023 00:53:21 +0200
Source: apt-setup
Architecture: source
Version: 1:0.180
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Cyril Brulebois <kibi@debian.org>
Closes: 991947
Changes:
 apt-setup (1:0.180) unstable; urgency=medium
 .
   [ Cyril Brulebois ]
   * Don't disable -updates when installing for testing (Closes: #991947).
     It might make sense to have some flag to control this, and maybe only
     enable it once we move from D-I Alpha to D-I RC. In any case, let's
     turn this on right now for Bookworm!
 .
   [ Updated translations ]
   * Bulgarian (bg.po) by Damyan Ivanov
   * Estonian (et.po) by Kristjan Räts
   * Hungarian (hu.po) by SZERVÁC Attila
   * Georgian (ka.po) by Temuri Doghonadze
Checksums-Sha1:
 76a1700e37e7499fbb5030d15bfd53d5bf54e81a 1794 apt-setup_0.180.dsc
 0ef6de8bd3b5a46330c07afcabee249f1c0156a6 266984 apt-setup_0.180.tar.xz
 f1be9354fe619bb1661e5d31d55273b86168e063 6417 apt-setup_0.180_source.buildinfo
Checksums-Sha256:
 6ed775721f9aadb4c9599446f170b9fee590ca0576de92b539fae87c5fec534a 1794 apt-setup_0.180.dsc
 33aace0dc6f4f5223e801e79294458e147b7a9f79e05e0556f8b5edcd9760f6e 266984 apt-setup_0.180.tar.xz
 16d34f5155a7b23ec5ab55ac4962a21032655eb8766a892ee3ffb1ff8690c27a 6417 apt-setup_0.180_source.buildinfo
Files:
 1b4e7212fd13572a51d917e71d28dde9 1794 debian-installer optional apt-setup_0.180.dsc
 6e0896f96059e2b9d2b12a8788fa2654 266984 debian-installer optional apt-setup_0.180.tar.xz
 0029c8c8281f5d1efa0a059c4b1b3fd5 6417 debian-installer optional apt-setup_0.180_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJEBAEBCgAuFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmRIWfoQHGtpYmlAZGVi
aWFuLm9yZwAKCRD/kUrwwrNVIK6tD/wN8zqJ16xkHMJvMViG9OEHlAP5/xGy7+9f
VIlnqlN12AflrSALmA+kboIJcs+ptOZjmI3HOBoJfdioPTetznP+lXq5NexjiAnY
MkONgSleAraqNhVSgSwXs2FKVHIaZxn+vsiRAkIVPfU3TGfbVxmnASSUSBdlvU3c
mO2UTYmXY+JeSnQ5pK+MbIe1lyyChLy3Li8SGtvhdOg0mrLqh83gJL68R9ThaWHp
69Zcwo3V1E4WAwcynA7LmogdeZjRreM0p2uGWD+o24KB3ZyRYiSPhTUdfyzwlL7w
Ul96JvMTi4PtGo98QErEU+fyJv3iwN3hB1clSaU7q12kIwdfxrzjjmw7DTEPhWqC
/NcDlayeqszk5MAXhZclvhJ/jj19C8WG8Vxh9DTFhiUHzxgi+nzNvB1yVv/vxEmo
saXOXTzMJPCtPRCLgMs2MVa4oZGWz8Ovq4YIhihRI1M8arZlw0uxlDTpGIDVOk2l
LDtLsRRxmQ0gROuRL0nagWmP1DZcbw2rHRLaEqDpRJ2ZmPxQmzAqP4npq/EhtJT+
eZ0cNLSvH4B4gFRPMB6V9Pcdfa6ZXZtRfQlsGHxeNsqRpfwZCxgHMIg6nU5oVITr
tpO8sC64UCVEFUAaS/lyDxMD8hOAoar3JDYZUfL9Inu9zo8vW/1gPH6Nhwbc4qdT
4Su9X3e/mQ==
=IxsU
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: