y go ahead as planned, i.e., social costs are not considered,
but should be (IMHO).
Ansgar
gt; Sledge - 10, 17, 24 images team
> donald - 10, 17 press
Ansgar
copy installer version 20230217 from suite unstable to
| testing.
| Architectures to copy: i386, amd64, mipsel, ppc64el, s390x, armel, armhf,
arm64, mips64el
| Architectures to skip:
| Installer has been copied successfully.
+---
Thanks for your work on d-i!
Ansgar
On Thu, 2022-11-17 at 21:33 +, Adam D. Barratt wrote:
> Please could you indicate your availability and preferences between:
>
> - December 3rd
No time here.
> - December 10th
> - December 17th
These are still free.
Ansgar
however
debootstrap's internal Perl implementation of pkgdetails does remove
such a suffix:
+---
| $d =~ s/:.*//;
+---[ functions ]
Ansgar
[1]: https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/76
version 20220917 from suite bookworm-proposed-updates to
| testing.
| Architectures to copy: i386, amd64, mipsel, ppc64el, s390x, armel, armhf,
arm64, mips64el
| Architectures to skip:
| Installer has been copied successfully.
+---
Ansgar
seye anyway), so I suppose all of
> them could go away.
I moved them to the morgue to be archived (also snapshot.d.o should have
them anyway).
I removed 20210731 from testing as well. Testing now only contains the
freshly copied 20220914 version.
Ansgar
ite unstable to
| testing.
| Architectures to copy: i386, amd64, mipsel, ppc64el, s390x, armel, armhf,
arm64, mips64el
| Architectures to skip:
| Installer has been copied successfully.
+---
Ansgar
; before mounting, and then try to mount "-o subvol=@rootfs" as Ansgar
> suggested. One step more flexible is to have a Rescue policy of
> something like only supporting read-write subvolumes with a name that
> matches '.*\@rootfs.*', and that exist in the / of the
g the root filesystem failed: /target contained only a
"@rootfs" subdirectory. So running a shell in the target fs failed.
Manually mounting the filesystem with `-o subvol=@rootfs` worked.
This was with Debian 11.4.
Ansgar
he Priority in unstable will automatically propagate to
testing, but (old)stable will be unaffected.
Ansgar
at the same time or
> separately.
Either is fine with me.
Ansgar
entered is
unreachable."
Ansgar
d where example-preseed.txt comes from; a quick grep
through webwml.git did not find it. So I just write to this list :-)
Ansgar
[1]: https://www.debian.org/releases/stable/example-preseed.txt
t;C.UTF-8"
instead of "C" or there was at least an option for "C-UTF-8". I think I
tried setting "C.UTF-8" via preseeding recently and that was rejected
as an invalid choice (not 100% sure).
Ansgar
him not installed to /boot/efi) and a
non-booting system.
I think the logic selecting "shim" to be installed should also pull in
the signed version of grub explicitly to have at least a bootable
system even with install-recommends set to false.
Ansgar
-BULLSEYE-live-builder-AMD64
+---[ file:///etc/mailname ]
Ansgar
Hi,
On Fri, 2022-06-17 at 20:31 +0100, Adam D. Barratt wrote:
> - July 2nd (means freezing next weekend, but so be it)
> - July 9th
Both would work for me.
Ansgar
this problem: not
> cdebootstrap, not multistrap, not mdebstrap.
>
> Thus, debootstrap should simply not create tainted installs by
default.
Please don't use my bug report for trolling.
Thanks,
Ansgar
Hi,
On Tue, 2021-07-20 at 22:35 +0200, Paul Gevers wrote:
> We currently don't have any day yet with all involved
> teams comfortably present, the one coming closest is 4 September.
> Somebody from ftp available on 14 august?
That should be doable.
Ansgar
ied successfully.
+---
Ansgar
On Sun, 2021-05-30 at 09:09 +0200, Paul Gevers wrote:
> 26 June
> 3 July
> 10 July
> 17 July [Steve (CD), press]
> 24 July [Steve (CD), press]
> 31 July
> 7 August
> 14 August
Currently all of these are fine for me.
Ansgar
wanted to suggest so at least for Bookworm.
Ansgar
interesting things currently.
Ansgar
Cyril Brulebois writes:
> FTP Masters, please sync the installer from sid to testing, as it seems
> to be Installed for all release architectures (9 total):
>
> dak copy-installer 20201202
Done.
Ansgar
Cyril Brulebois writes:
> dak copy-installer 20200314
Done.
Ansgar
s versions in both testing and unstable.
I'll try to remember to do so in the next days.
Thanks for your tireless work on d-i.
Ansgar
o this in more detail currently
though. So I suggest to do an extra upload to NEW for now.
Ansgar
Harald Dunkel writes:
> I am not sure, but isn't systemd supposed to figure this out on the
> next run anyway?
Yes, but the "next run" might be the next system restart (or something
else running `systemctl daemon-reload`). One might get unexpected
behavior until such a time.
Ansgar
Cyril Brulebois writes:
> FTPmasters, please sync the installer from sid to testing, as it seems
> to be Installed for all release architectures (10 total):
>
> dak copy-installer 20190702
Done.
Ansgar
Cyril Brulebois writes:
> FTPmasters, please sync the installer from sid to testing:
>
> dak copy-installer 20190623
Done.
Thanks for your work,
Ansgar
Philipp Kern writes:
> 20/06/2019 20:22, Ansgar Burchardt wrote:
>> You look up which uid the _apt user inside the chroot has and use that.
>
> Yeah, but that scales poorly if you have a centralized firewall
> policy. It means that you need to maintain dynamic rules. I know it&#x
Trek writes:
> Ansgar Burchardt wrote:
>> For limiting network access, I would recommend instead using network
>> namespaces (to only provide limited network access for all processes)
>> and/or user namespaces (if filtering for single UIDs is really
>> needed). These
e file might be created in
dselect's postinst.
Ansgar
Ansgar Burchardt writes:
> (I don't maintain debootstrap.)
>
> I don't think it is a good idea to require debootstrap to know about
> such details.
>
> For limiting network access, I would recommend instead using network
> namespaces (to only provide limited network
ould recommend instead using network
namespaces (to only provide limited network access for all processes)
and/or user namespaces (if filtering for single UIDs is really needed).
These do not require any uids to match between in- and outside.
Ansgar
uld
work.
I don't think we should add a new component without having that
(component meaning main, contrib, non-free, non-free-firmware here).
They are not nice to handle on the archive side.
Ansgar
>> Hi,
>>
>> I think there was consensus to introduce the non-free-firmware s
fer to binaries in /usr/local/bin when they have locally installed
binaries and autodetection using $PATH is used? /usr/local/bin is
usually before /usr/bin and /bin after all.
dpkg could add a "not-built-in-a-clean-chroot" flag to detect those.
Ansgar
o have worked out
> ok, so I'd like to ask that the same be done with libnss-systemd.
>
> [1]
> https://salsa.debian.org/systemd-team/systemd/commit/577df340cad51d5779d646d9aefa28c3c1b90d4c
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803184
Asking -boot@ for an ack.
Ansgar
t the package uses a different
value, but it should choose "optional" if nothing is done to explicitly
choose a different priority).
Ansgar
om suite unstable to
| testing.
| Architectures to copy: s390x, kfreebsd-i386
| Architectures to skip: i386, amd64, mipsel, ppc64el, mips, armel, armhf,
arm64, mips64el, hurd-i386
| Installer has been copied successfully.
+---
Copying kfreebsd-* looks like a bug. copy-installer should probably be
patched to only copy architectures that exist in testing.
Ansgar
Cyril Brulebois writes:
> FTPmasters, please sync the installer from sid to testing:
>
> dak copy-installer 20181206
Done.
Thanks for your work on d-i :-)
Ansgar
is: there are only very few packages
causing problems and these should have a patch soon.
In addition one has to actually built one of the very few packages in a
merged-/usr environment and then install them in a non-merged-/usr
environment to actually trigger the problem and debootstrap already
Ansgar Burchardt writes:
> There were discussions about enabling this by default years ago, I
> don't think minor issues should be a reason to delay this change.
>
> Note that it has been delayed for after the stretch release as there
> were major issues back then (it was enab
t;5 months for someone to find a problem this time
which is pretty good for any change.
Ansgar
Hi,
"Adam D. Barratt" writes:
> - November 10th
This would work if needed, though I don't mind someone else doing the
archive side (still have some things to sort out *sigh*).
Ansgar
ther or both of those dates?
>
> The 7th is looking like the favourite so far (although would mean
> freezing next weekend), but we still need an ftp-master (N)ACK on
> either / both date.
I still have time on either weekend.
Ansgar
Hideki Yamane writes:
> Hi,
>
> On Tue, 19 Jun 2018 08:09:17 +0200
> Ansgar Burchardt wrote:
>> The `-k` option doesn't work for older releases (some packages do
>> replace files there). It should always be used for newer releases (>=
>> stretch) to have
replace files there). It should always be used for newer releases (>=
stretch) to have less differences between --merged-usr and
--no-merged-usr.
(As it should always be applied it shouldn't be set in
`setup_merged_usr` as that is misleading.)
Ansgar
stage_install().
debootstrap should default to non-merged-usr for stretch, but it should
be possible to enable merged-usr via the command-line parameter to avoid
the regression in debuerreotype.
Ansgar
Cyril Brulebois writes:
> FTPmasters, please sync the installer from sid to testing:
>
> dak copy-installer 20180610
Done.
Thanks for maintaining d-i,
Ansgar
fine with me; Joerg wanted to do the 8.11 one, but if he has
time restrictions on June 23rd and doing 8.11 after 9.5 would be too
late for him, I could probably also do both.
(If Joerg wants to do both, that's also fine with me.)
Ansgar
gs-Cc: debian-boot@ by default for bugs
filed against the ftp.debian.org pseudo-package that request an
override change which changes the priority of packages.
Override changes that only affect the section should not be Cc'ed to
debian-boot@.
Ansgar
-e "$TARGET"/* ]; then
That doesn't work:
+---
| $ dash -c '[ -e /bin/* ]'
| dash: 1: [: /bin/2to3-2.7: unexpected operator
+---
Ansgar
ch 24
> - March 31
These might work.
Given Steve doesn't have time on the later dates, it might be better to
have another ftpmaster handle the point release on March 3 or 10.
Ansgar
> certainly not provide them).
So who should provide them? debootstrap? base-files?
The correct long-term fix is probably for packages to eventually install
to the location in /usr anyway. That doesn't work without some
transition period of 1-2 releases though.
Ansgar
te responses earlier
> in the thread Ansgar links to as [1]).
There were 11 mails in the thread I linked as [1] in my initial mail.
None were really negative, just one person wondering if this means /
and /usr on separate filesystems is no longer supported (even though I
explicitly said it is in
On Thu, 2017-11-16 at 08:02 +, Adam D. Barratt wrote:
> I believe we still need ftp-master and press confirmation, but I've
> been failing at poking.
Either of 2017-12-02 or 2017-12-09 should be fine for me.
Ansgar
Jonathan Wiltshire writes:
> Ok, does 7th October work any better? I'm keen not to get too far adrift
> from the interval though.
Should be okay if no other ftpmaster volunteers.
Ansgar
Cyril Brulebois writes:
> FTPmasters, please sync the installer from sid to testing:
>
> dak copy-installer 20170828
Done.
Ansgar
Emmanuel Kasper writes:
> The default base system installed by debootstrap includes all packages
> with Pritority essential and
> important, but this was not yet documented.
There is no "essential" priority. There is only "required" (and its
dependencies).
Ansgar
y call. But I'd be fine reworking to that
> approach if that's more acceptable, though.
You can always introduce a `mknod_if_not_exists` function or so. Though
I'm not sure this is worth here (the name is so long the `test -e` is
almost shorter).
Ansgar
Hi,
Russ Allbery writes:
> Ansgar Burchardt writes:
>> I discussed this a bit on IRC with the other ftp-masters and we came to
>> this summary:
[...]
>> 2) We wonder if the 'standard' priority can also be dropped: as far as
>>we know, it is used only by
#x27;ve Cc'ed -boot@ as this policy change affects them (I don't think they
have to read all of the way too long bug history though).
Ansgar
'm tempted to give debian-boot@ people a chance to react in case
> images from 2016 should stay a bit longer. Of course this can wait
> post-release, no urgency from my point of view.
Not done yet, but we should probably also do the clean-up for stretch.
Ansgar
Cyril Brulebois writes:
> FTPmasters, please sync the installer from sid to testing:
>
> dak copy-installer 20170608
Done. Also removed dists/testing/main/installer-* for non-release
architectures.
Ansgar
d.o in a
browser.
So changing the mirror from httpredir.d.o to deb.d.o should be very
low-risk :-)
Ansgar
Cyril Brulebois writes:
> FTPmasters, I've just uploaded d-i 20170525 to the archive, and need to
> leave for the day, so it would be nice if you could please sync the
> installer from sid to testing when all builds are ready:
>
> dak copy-installer 20170525
Done.
Ansgar
t; * April 22-23
> * April 29-30
> * May 6-7
These should all be okay.
Ansgar
e dependencies just pull it in if needed?!
>
> (Yes, sure there might be some important package depending on it
> and policy says yada, yada... but sooner or later policy
> will get fixed -> #758234 )
I agree that we should try to downgrade libraries to Priority: optional
if possible.
I would still like an ACK from the d-i team (X-Debbugs-Cc'ed).
Ansgar
it at
the end of the installation again?) so the priority of the tasksel and
tasksel-data packages could be downgraded.
Ansgar
Package: ftp.debian.org
blends-tasks is not used by d-i currently so there is no need to have it
included in the default install.
See also the discussion in #846002.
Ansgar
Cyril Brulebois writes:
> FTPmasters, please sync the installer from sid to testing:
>
> dak copy-installer 20170127
Done.
Ansgar
Hi,
there is a second implementation of pkgdetails in C (part of the base-
installer source package). I assume that would also need to be patched
to ignore architecture qualifications?
Ansgar
issue for more packages):
there needs to be a mount for /dev/pts to accommodate for the changes in
debootstrap (and optionally a bind mount for /dev/ptmx if there are
still old chroots around).
Ansgar
Cyril Brulebois writes:
> FTPmasters, please sync the installer from sid to testing:
>
> dak copy-installer 20161031
Done.
Ansgar
Cyril Brulebois writes:
> FTPmasters, please sync the installer from sid to testing:
>
> dak copy-installer 20161027
Done. Can we remove older version from testing and unstable?
Ansgar
an testing/unstable in the last weeks.
Ansgar
alling the package lxcguest in
> /usr/share/lxc/templates/lxc-ubuntu the install is successful.
Ansgar
rather than
later to give time to find some more bugs. With this change, the
currently known bugs[4] should also be raised to "serious", but I don't
think any of them should be a blocker.
Ansgar
[1] <https://lists.debian.org/debian-devel/2016/09/msg00269.html>
[2] <
Ansgar Burchardt writes:
> debootstrap should support archives that only provide Packages.xz.
>
> I'll try to take a look at implementing this soon. From a quick glance
> it shouldn't be too difficult given several compression formats are
> already supported (bz2,
tag 838388 + patch
thanks
Ansgar Burchardt writes:
> Ah, I'm to blame for that. [1] added `-k` to the options passed to tar
> in order to avoid replacing the new symlinks from / to /usr with real
> directories. However it looks like tar returns an error when there are
> actu
ks like tar returns an error when there are
actual file conflicts (as opposed to just symlink vs. directory).
Only adding -k for newer distributions (i.e. the ones that merged-/usr
supports) should work around the problem.
Just --keep-directory-symlink would of course be ideal, but I doubt it
is s
ease cycle).
Please remember that this still allows / and /usr to reside on different
filesystems: in this case the initramfs has to make sure /usr is mounted
as well. This is already required for various reasons (again, see [1]).
Ansgar
[1] https://lists.debian.org/debian-devel/2016/01/msg00
Package: debootstrap
Version: 1.0.82
Owner: Ansgar Burchardt
Control: block 818463 by -1
debootstrap should support archives that only provide Packages.xz.
I'll try to take a look at implementing this soon. From a quick glance
it shouldn't be too difficult given several compression f
.e. anyone has
`dpkg-deb` available, but busybox' tar instead of GNU's tar), but the
attached patch avoids the problem by calling the installed `dpkg-deb`
in the second stage.
(The patch should go in after the ones from #810301.)
Ansgar
-- System Information:
Debian Release: stretch/sid
On Thu, 2016-09-08 at 16:09 +0200, Ansgar Burchardt wrote:
>
> debootstrap should validate that ${suite} is listed in the Release
> file in either the Suite: or Codename: fields. Additionally storing
> the codename in a variable would also be useful for suite-specific
> workarou
On Thu, 2016-09-08 at 15:36 +0200, Ansgar Burchardt wrote:
> Could you use the "Codename" field from Release to normalize the
> suite name? That should work even when the meaning of "stable"
> changes.
I've updated Marco's patch to include this change and p
The current stable cannot work with a merged /usr, so
> I expected that this would be changed just before stretch is
released.
Could you use the "Codename" field from Release to normalize the suite
name? That should work even when the meaning of "stable" changes.
(Which makes me wonder: does debootstrap check that the suite it is
asked to install is either in the Release file's Suite or Codename
field?)
Ansgar
the Release
file in either the Suite: or Codename: fields. Additionally storing
the codename in a variable would also be useful for suite-specific
workarounds, such as [1].
Ansgar
[1] <https://bugs.debian.org/810301#69>
-- System Information:
Debian Release: stretch/sid
APT prefers un
>
> August 27th/28th - public holiday weekend in the UK; doesn't work for
> me
These don't work for me either. (Also they are probably too close by
now.)
> September 3rd/4th
Might work with some extra planning, but not that well.
> September 10th/11th
>
> September 17th/18th
These should be okay for me.
Ansgar
tract the right part
is quite error-prone. (As Julien notes and I agree.) Quite a lot of
tools in Debian got this wrong, see for example CVE-2013-1051.
As far as I understand, splitting `InRelease` into data and detached
signature is also what `apt` does these days.
Ansgar
.org/830901
All three packages should get pulled in by "sysvinit-core" on systems
not using systemd.
Ansgar
ficial Debian releases in the future.
Ansgar
[1] <https://buildd.debian.org/stats/graph-ports-week-big.png>
to "required". The "minbase" variant then installs no
additional base packages (base="apt" is already installed).
Helmut confirmed that adding another packages ("ed") as an additional
base package to the "minbase" variant made `debootstrap` complete
successfully.
I've reverted the priority of "apt" back to "important" for now.
Ansgar
nts.
On the d-i side, I hope this doesn't break anything as debootstrap's
default variant should not be affected by these changes, unless d-i
can also install a "minbase" variant?
And just for the record: a system with no "init" should have a
"policy-rc.d&qu
Cyril Brulebois writes:
> Thanks, please rerun with the binNMU now so that we get the
> brltty/espeakup fixes for Stretch Alpha 6:
>
> dak copy-installer 20160516+b1
Done.
Ansgar
This should also allow demoting several perl modules:
libtext-iconv-perl, libtext-wrapi18n-perl, libtext-charwidth-perl (or
demoting those even to "optional" with the reasoning given in #758234)
Ansgar
Cyril Brulebois writes:
> FTPmasters, please sync the installer from sid to testing:
>
> dak copy-installer 20160516
Done.
Thanks for your work on d-i,
Ansgar
elif doing_variant minbase; then
| base="apt"
| fi
+---[ file:///usr/share/debootstrap/scripts/sid ]
If apt was Priority: required, debootstrap wouldn't need to pretend it
was. It also seems more honest ;)
Ansgar
1 - 100 of 159 matches
Mail list logo
