Control: tags -1 moreinfo
Hi Dmitry
On Wed, Aug 23, 2023 at 08:10:17PM +0300, Dmitry Baryshkov wrote:
> The linux-libc-dev package provides only a limited set of uAPI headers.
> For example, scsi, drm, video, etc. headers are missing from the
> package.
scsi headers are shipped by libc6-dev,
Control: tags -1 moreinfo
Hi Dmitry
On Wed, Aug 23, 2023 at 08:10:17PM +0300, Dmitry Baryshkov wrote:
> The linux-libc-dev package provides only a limited set of uAPI headers.
> For example, scsi, drm, video, etc. headers are missing from the
> package.
scsi headers are shipped by libc6-dev,
On Sat, Aug 12, 2023 at 09:47:57AM -0400, pgnd via Postfix-users wrote:
> postconf -n | grep -i tls | grep -i cipher
> smtp_tls_ciphers = medium
> smtp_tls_exclude_ciphers = EXP, LOW, MEDIUM, aNULL, eNULL, SRP,
> PSK, kDH, DH, kRSA, DHE, DSS, RC4, DES, IDEA,
On Mon, Jul 24, 2023 at 07:56:03PM +0200, Bastian Blank wrote:
> On Sat, Jan 21, 2023 at 11:58:26PM +0100, Bastian Blank wrote:
> > Please verify that this login works for you. I would like to remove
> > existing users in a few weeks.
> I will cleanup the remaining users at t
On Thu, Jul 27, 2023 at 01:39:39PM +0200, Bastian Blank wrote:
> There exists now a branch "use-identity". This seems to work with
> Firefox. At least the authentication part itself works and I already
> recorded the correct URL in the application. You just can't use the
Control: tags -1 pending
On Thu, Jul 27, 2023 at 06:44:56AM +0200, Martin Pitt wrote:
> We could adjust our scripts for the renaming, but this smells like a bug --
> it may be nice to have cloud images with some/all backports enabled, but can
> we
> also have the "pure bullseye" images back?
Control: tags -1 pending
On Thu, Jul 27, 2023 at 06:44:56AM +0200, Martin Pitt wrote:
> We could adjust our scripts for the renaming, but this smells like a bug --
> it may be nice to have cloud images with some/all backports enabled, but can
> we
> also have the "pure bullseye" images back?
Hi Antonio
On Wed, Jul 26, 2023 at 11:17:42PM +0200, Bastian Blank wrote:
> I know. You are welcome to try and get this to work.
There exists now a branch "use-identity". This seems to work with
Firefox. At least the authentication part itself works and I already
recorded th
Hi Antonio
On Wed, Jul 26, 2023 at 05:34:53PM -0300, Antonio Terceiro wrote:
> I have to say, though, that being forced to use Chromium is not exactly
> fun, as I use Firefox for everything else.
I know. You are welcome to try and get this to work. The extension
itself should work fine, I
Hi
On Mon, Jul 24, 2023 at 08:29:41PM +0200, Lucas Nussbaum wrote:
> How can I verify that this login works for me?
> I installed the extension. What's next?
You can access the extension this way:
https://salsa.debian.org/-/snippets/648
Or go directly to
Hi
On Sat, Jan 21, 2023 at 11:58:26PM +0100, Bastian Blank wrote:
> Please verify that this login works for you. I would like to remove
> existing users in a few weeks.
I will cleanup the remaining users at the end of the week.
Regards,
Bastian
--
You're too beautiful to ignore. To
On Thu, Jul 13, 2023 at 09:16:15PM +0200, Bastian Blank wrote:
> Please share your thoughts or if we have a better solution overall.
After a lot of thinking, maybe a solution that allows for incompatible
package updates without renames would be more useful. Something like:
We uncou
On Wed, Jul 19, 2023 at 11:23:53PM -0400, Viktor Dukhovni via Postfix-users
wrote:
> > #systemctl status postfix
> > ? postfix.service - Postfix Mail Transport Agent
> > Loaded: loaded (/lib/systemd/system/postfix.service; enabled; preset:
> > e>
> > Active: active (exited) since Wed
On Fri, Jul 14, 2023 at 04:17:34PM +0200, Ben Hutchings wrote:
> On Thu, 2023-07-13 at 21:16 +0200, Bastian Blank wrote:
> [...]
> > ## Proposed behaviour
> >
> > This tries to make sure everything apart from experimental gets new
> > names and ABI on every u
On Fri, Jul 14, 2023 at 04:17:34PM +0200, Ben Hutchings wrote:
> On Thu, 2023-07-13 at 21:16 +0200, Bastian Blank wrote:
> [...]
> > ## Proposed behaviour
> >
> > This tries to make sure everything apart from experimental gets new
> > names and ABI on every u
Hi
On Thu, Jul 13, 2023 at 11:28:31PM +0300, Adrian Bunk wrote:
> On Thu, Jul 13, 2023 at 09:16:15PM +0200, Bastian Blank wrote:
> > ### NMU
> > Can be easily added back by adding "bX" or so to the ABI.
> That would be confusing, bX is naming convention for binNMUs in
Hi
On Thu, Jul 13, 2023 at 11:28:31PM +0300, Adrian Bunk wrote:
> On Thu, Jul 13, 2023 at 09:16:15PM +0200, Bastian Blank wrote:
> > ### NMU
> > Can be easily added back by adding "bX" or so to the ABI.
> That would be confusing, bX is naming convention for binNMUs in
On Thu, Jul 13, 2023 at 11:53:40PM -0700, Vagrant Cascadian wrote:
> Any objections to me merging these patches? Prefer if they remain
> separate or squash them into a single patch?
Hmm, I have to check, but dpkg-buildflags should already provide this
flag and all the modified locations are for
On Thu, Jul 13, 2023 at 11:53:40PM -0700, Vagrant Cascadian wrote:
> Any objections to me merging these patches? Prefer if they remain
> separate or squash them into a single patch?
Hmm, I have to check, but dpkg-buildflags should already provide this
flag and all the modified locations are for
Hi folks
You might have heard that the masters of Linux Secure Boot, aka shim
reviewers, have spoken. They have told us that our way of handling
kernel modules is not longer acceptable. For some context see #1040901.
This means for us that we have to make sure that kernel and modules
can't be
Hi folks
You might have heard that the masters of Linux Secure Boot, aka shim
reviewers, have spoken. They have told us that our way of handling
kernel modules is not longer acceptable. For some context see #1040901.
This means for us that we have to make sure that kernel and modules
can't be
Control: tags -1 confirmed
Hi
On Sat, Jul 08, 2023 at 08:41:03PM +0200, John Paul Adrian Glaubitz wrote:
> Please enable building the linux-libc-dev package for the new Debian
> architecture loong64.
> The corresponding kernel architecture is called "loongarch".
I can't find loong64 in the
Control: tags -1 confirmed
Hi
On Sat, Jul 08, 2023 at 08:41:03PM +0200, John Paul Adrian Glaubitz wrote:
> Please enable building the linux-libc-dev package for the new Debian
> architecture loong64.
> The corresponding kernel architecture is called "loongarch".
I can't find loong64 in the
Hi
On Wed, Jul 12, 2023 at 01:00:43AM +0300, Taavi Eomäe via mailop wrote:
> On 11/07/2023 20:43, Bastian Blank via mailop wrote:
> > Given that this host only reacts on port 25 but not on port 587, I
> > assume this is MX.
> Ideally one would offer implicit TLS on port 46
Hi
On Tue, Jul 11, 2023 at 05:47:12PM +0200, Paul Menzel via mailop wrote:
> Testing the mail setup, I was surprised to have the key exchange parameters
> flagged [1]:
> > a1241.mx.srv.dfn.de.DH-2048 insufficient
This test is for web or e-mail? MX or MSA?
Given that this host
On Fri, Jul 07, 2023 at 06:07:58PM -0600, Sam Hartman wrote:
> >>>>> "Bastian" == Bastian Blank writes:
> Bastian> Why do we need to have the priority adjusted instead of fix
> Bastian> d-i to install what it knows the user needs?
> Because it's
On Wed, Jul 05, 2023 at 09:06:24PM -0300, Santiago Ruano Rincón wrote:
> For the moment, ifupdown is still installed by the debian-installer as
> default network interfaces manager. And after sleeping over it, and
> discussing with debian fellows, I would like to call for consensus to
> rise
On Thu, Jul 06, 2023 at 09:39:43AM +0100, Luca Boccassi wrote:
> Yes I will bump the dependency in the next azcli upload, but I wanted
> to push the fix immediately.
Okay. Any reason for not just merging the two into one source? Can be
automated and you don't need to think about it again.
On Thu, Jul 06, 2023 at 09:39:43AM +0100, Luca Boccassi wrote:
> Yes I will bump the dependency in the next azcli upload, but I wanted
> to push the fix immediately.
Okay. Any reason for not just merging the two into one source? Can be
automated and you don't need to think about it again.
Hi Luca
>* New upstream version 20230705+git (Closes: #1040406)
Could you please describe how a new version of the azure module can fix
that? The dependency needs to be updated as well at least.
Also, how can it be that azure-cli is updated without the corresponding
azure?
Bastian
--
Hi Luca
>* New upstream version 20230705+git (Closes: #1040406)
Could you please describe how a new version of the azure module can fix
that? The dependency needs to be updated as well at least.
Also, how can it be that azure-cli is updated without the corresponding
azure?
Bastian
--
Package: python3-azure-cli
Version: 2.50.0-1
Severity: grave
azure-cli with all dependencies fullfilled does not allow "az" to run:
| % az vm -h
| The command failed with an unexpected error. Here is the traceback:
| No module named 'azure.mgmt.compute.v2022_11_01'
| Traceback (most recent call
Package: python3-azure-cli
Version: 2.50.0-1
Severity: grave
azure-cli with all dependencies fullfilled does not allow "az" to run:
| % az vm -h
| The command failed with an unexpected error. Here is the traceback:
| No module named 'azure.mgmt.compute.v2022_11_01'
| Traceback (most recent call
Control: reassign -1 src:linux 6.3.11-1
Control: tags -1 unreproducible
On Wed, Jul 05, 2023 at 11:31:06AM +0100, Klaus Ethgen wrote:
> > But this is what you want, you want to use the full resolution of the
> > output and scale the output (this is called HiDPI). If you try to
> > change the
Control: reassign -1 src:linux 6.3.11-1
Control: tags -1 unreproducible
On Wed, Jul 05, 2023 at 11:31:06AM +0100, Klaus Ethgen wrote:
> > But this is what you want, you want to use the full resolution of the
> > output and scale the output (this is called HiDPI). If you try to
> > change the
Control: reassign -1 dkms
On Wed, Jul 05, 2023 at 10:53:19AM +0200, Vincent Lefevre wrote:
> On 2023-07-04 16:13:56 +0200, Andreas Beckmann wrote:
> > This needs to be fixed before linux 6.3.0-2-* can migrate to testing,
> > otherwise it will break dkms module building for everyone still having
>
Control: reassign -1 dkms
On Wed, Jul 05, 2023 at 10:53:19AM +0200, Vincent Lefevre wrote:
> On 2023-07-04 16:13:56 +0200, Andreas Beckmann wrote:
> > This needs to be fixed before linux 6.3.0-2-* can migrate to testing,
> > otherwise it will break dkms module building for everyone still having
>
Control: reassign -1 dkms
On Wed, Jul 05, 2023 at 10:53:19AM +0200, Vincent Lefevre wrote:
> On 2023-07-04 16:13:56 +0200, Andreas Beckmann wrote:
> > This needs to be fixed before linux 6.3.0-2-* can migrate to testing,
> > otherwise it will break dkms module building for everyone still having
>
Control: tags -1 moreinfo
Hi Klaus
On Tue, Jul 04, 2023 at 06:42:40PM +0100, Klaus Ethgen wrote:
> With this update of linux-image, there is only the highest resolution
> available anymore. As this is 3840x2400, it leaves the screen completely
> unreadable and unusable.
But this is what you
Control: tags -1 moreinfo
Hi Klaus
On Tue, Jul 04, 2023 at 06:42:40PM +0100, Klaus Ethgen wrote:
> With this update of linux-image, there is only the highest resolution
> available anymore. As this is 3840x2400, it leaves the screen completely
> unreadable and unusable.
But this is what you
Control: severity -1 normal
Hi
On Tue, Jul 04, 2023 at 06:35:44PM +0200, Hauke Fath wrote:
> /misc /etc/auto.misc
> -nfsvers=3,proto=udp,resvport,retrans=5,rsize=16384,wsize=16384,rw,hard
And if you set it to TCP (the default) or better directly switch to
NFSv4?
> This upstream
Control: severity -1 normal
Hi
On Tue, Jul 04, 2023 at 06:35:44PM +0200, Hauke Fath wrote:
> /misc /etc/auto.misc
> -nfsvers=3,proto=udp,resvport,retrans=5,rsize=16384,wsize=16384,rw,hard
And if you set it to TCP (the default) or better directly switch to
NFSv4?
> This upstream
Hi Julien
On Wed, Apr 26, 2023 at 02:10:05PM +0200, Julien Cristau wrote:
> I haven't been able to get connections to the host working again after
> the dhcp issues, can we maybe start over, using debian 11, and if
> possible some form of OOB access?
I finally managed to get to it, sorry about
Hi
On Sun, Jul 02, 2023 at 03:12:21PM +0200, antonio wrote:
> Kernel: Linux 6.3.11-2-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT)
This is no Debian. You have to verify that on Debian.
Bastian
--
Yes, it is written. Good shall always destroy evil.
-- Sirah the Yang, "The
Hi
On Sun, Jul 02, 2023 at 03:12:21PM +0200, antonio wrote:
> Kernel: Linux 6.3.11-2-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT)
This is no Debian. You have to verify that on Debian.
Bastian
--
Yes, it is written. Good shall always destroy evil.
-- Sirah the Yang, "The
On Wed, Jun 28, 2023 at 10:01:13AM +0200, Thomas Goirand wrote:
> It's not. As written by Russ in this thread, filling a bug against
> orphan-sysvinit-scripts so it takes over the abandoned script is. I wouldn't
> mind seeing this mandatory, and written in the policy.
I do. This also does not
On Mon, Jun 26, 2023 at 01:22:38PM -0400, Scott Kitterman wrote:
> > Less prone to errors than a manual process might be to watch
> > automatically where legacy startup scripts disappear anyway; it's not
> > that complicated to do. People tend to forget things.
>
> That sounds reasonable. It
On Sun, Jun 25, 2023 at 03:15:24PM +0100, Mark Hindley wrote:
> To avoid breakage of existing systems and facilitate ongoing support for
> non-systemd inits, I would like to establish a consensus for
> - stating that initscripts remain useful.
> - requiring a coordinated transition of any
On Thu, Jun 22, 2023 at 08:51:01PM +0200, Philipp Kern wrote:
> TBH time is too short to manually provision IP addresses on servers.
And DHCP is gladly enough entirely optional since SLAAC exists. But
for that you need systemd-networkd/systemd-resolved or a whole bunch of
other software.
On Tue, Jun 20, 2023 at 06:50:10PM +0200, Ben Hutchings wrote:
> > This was replaced by hyperv_drm, which provides a standard mode
> > selection output.
> ...although we do still build hyperv_fb for the cloud-amd64 flavour,
> which seems like a mistake.
Because the cloud-amd64 flavour disables
On Tue, Jun 20, 2023 at 06:50:10PM +0200, Ben Hutchings wrote:
> > This was replaced by hyperv_drm, which provides a standard mode
> > selection output.
> ...although we do still build hyperv_fb for the cloud-amd64 flavour,
> which seems like a mistake.
Because the cloud-amd64 flavour disables
On Tue, Jun 20, 2023 at 03:32:19PM +0200, RSA wrote:
> Hello, I think kernel module hyperv_fb.ko is missing in the package. It was
> present in version 5.10.0-22 before upgrading to debian 12.
>
> $ find /lib/modules/5.10.0-23-amd64 -name hyperv_fb.ko
>
On Tue, Jun 20, 2023 at 03:32:19PM +0200, RSA wrote:
> Hello, I think kernel module hyperv_fb.ko is missing in the package. It was
> present in version 5.10.0-22 before upgrading to debian 12.
>
> $ find /lib/modules/5.10.0-23-amd64 -name hyperv_fb.ko
>
Package: cloud.debian.org
Severity: serious
Hi Martin
Thanks for reporting this.
On Tue, Jun 20, 2023 at 08:03:48AM +0200, Martin Pitt wrote:
> This isn't done by any package postinst -- `grep -r netdev
> /var/lib/dpkg/info/*`
> shows no relevant hits. So this must be somewhere in the scripts
Package: cloud.debian.org
Severity: serious
Hi Martin
Thanks for reporting this.
On Tue, Jun 20, 2023 at 08:03:48AM +0200, Martin Pitt wrote:
> This isn't done by any package postinst -- `grep -r netdev
> /var/lib/dpkg/info/*`
> shows no relevant hits. So this must be somewhere in the scripts
Package: cloud.debian.org
Severity: serious
Hi Martin
Thanks for reporting this.
On Tue, Jun 20, 2023 at 08:03:48AM +0200, Martin Pitt wrote:
> This isn't done by any package postinst -- `grep -r netdev
> /var/lib/dpkg/info/*`
> shows no relevant hits. So this must be somewhere in the scripts
Control: forcemerge 1036755 -1
On Wed, Jun 14, 2023 at 10:40:55AM +0100, Al Sutton wrote:
> Debain 12 has been released with a known bug which causes Android firmware
> builds to
> fail (https://lkml.org/lkml/2023/3/2/797) which makes bookwork unusable for
> the Android
> firmware community.
Control: forcemerge 1036755 -1
On Wed, Jun 14, 2023 at 10:40:55AM +0100, Al Sutton wrote:
> Debain 12 has been released with a known bug which causes Android firmware
> builds to
> fail (https://lkml.org/lkml/2023/3/2/797) which makes bookwork unusable for
> the Android
> firmware community.
Control: reassign -1 src:linux
Control: severity -1 important
On Mon, Jun 12, 2023 at 05:31:53PM +0200, Andreas Beckmann wrote:
> As a consequence, if cruft *-dkms packages are still installed, but fail
> to build the module for current kernels, this may result in upgrade
> failures. Therefore
Control: reassign -1 src:linux
Control: severity -1 important
On Mon, Jun 12, 2023 at 05:31:53PM +0200, Andreas Beckmann wrote:
> As a consequence, if cruft *-dkms packages are still installed, but fail
> to build the module for current kernels, this may result in upgrade
> failures. Therefore
Control: reassign -1 src:linux
Control: severity -1 important
On Mon, Jun 12, 2023 at 05:31:53PM +0200, Andreas Beckmann wrote:
> As a consequence, if cruft *-dkms packages are still installed, but fail
> to build the module for current kernels, this may result in upgrade
> failures. Therefore
On Fri, Jun 09, 2023 at 12:25:21PM +0800, Paul Wise wrote:
> Has anyone checked what percentage of these binaries will still run
> adequately after 2038 with 32-bit time_t?
All, because you don't need to provide those programs with a correct
time. But this is all a positive decisions.
>
On Thu, Jun 08, 2023 at 11:19:15AM +0800, Paul Wise wrote:
> On Tue, 2023-06-06 at 11:45 +0100, Simon McVittie wrote:
> > 2. i386 as a multiarch foreign architecture to run legacy binaries on
> > modern x86_64 systems
> > 2a. legacy native Linux i386 binaries
> > 2b. legacy Windows i386
On Mon, Jun 05, 2023 at 10:21:47AM +0200, Matus UHLAR - fantomas via
Postfix-users wrote:
> I've read a trick to reject particular recipient with temporary failure,
> which results in mail for other recipient being accepted, and further retry
> from sending server should only include that
On Mon, May 29, 2023 at 03:43:53PM +0200, Guilhem Moulin wrote:
> Package: sssd
> Version: 1.16.3-3.2+deb10u1
> CVE ID : CVE-2018-16838 CVE-2019-3811 CVE-2021-3621 CVE-2022-4254
> Debian Bug : 919051 931432 992710
This update is broken. libsss-certmap.so.0 was changed
On Sun, May 28, 2023 at 08:27:16PM +0200, Ansgar wrote:
> I think this entry from the changelog is meant:
>
> +---
> | 2020-02-15 Florian Weimer
> |
> | COMMIT: 3a0ecccb599a6b1ad4b149dc569c0080e92d057b
> | ld.so: Do not export free/calloc/malloc/realloc functions [BZ
> #25486]
Hi Jeremy
On Mon, May 22, 2023 at 08:14:14AM +, Jeremy Collin wrote:
> We are seeing right now that you have change the network management to
> netplan for debian12.
Yep. And this means network setup via cloud-init will actually work in
a lot more ways then before.
> One of my colleague
Hi Gunar
On Thu, May 18, 2023 at 12:14:42PM -0600, Gunnar Wolf wrote:
> dpkg has many bits that make it special. It has been discussed whethe
> dpkg should be a native package or it should become non-native; if it
> were non-native, having a patch that contradicts the upstream author's
> wishes
Hi Gunar
On Thu, May 18, 2023 at 12:14:42PM -0600, Gunnar Wolf wrote:
> dpkg has many bits that make it special. It has been discussed whethe
> dpkg should be a native package or it should become non-native; if it
> were non-native, having a patch that contradicts the upstream author's
> wishes
Source: youtube-dl
Version: 2021.12.17-2
Severity: serious
We have a maintained and uptodate fork of this package in the archive
and the release: yt-dlp. Do we really need to release this package in a
not so usable state?
Hint: transitional packages are supposed to be at the target of a
Source: youtube-dl
Version: 2021.12.17-2
Severity: serious
We have a maintained and uptodate fork of this package in the archive
and the release: yt-dlp. Do we really need to release this package in a
not so usable state?
Hint: transitional packages are supposed to be at the target of a
On Tue, May 16, 2023 at 09:44:41AM -0400, Wietse Venema via Postfix-users wrote:
> Looks like you have a *local* DNS problem. Check your routing,
> including netmasks.
The domain is broken. See
https://dnsviz.net/d/info.apr.gov.rs/dnssec/
On of the listed name servers is unresponsive and also
On Tue, May 16, 2023 at 07:32:55PM +0300, Eugene R via Postfix-users wrote:
> Am I correct that the string in question should normally contain the SASL
> response? While the "Password:" is apparently some interactive prompt,
> indicating that something might be wrong with the connection or
>
Hi Steve
On Mon, May 15, 2023 at 02:01:15AM +0100, Steve McIntyre wrote:
> Russ has described copying *binaries* out of packages and running them
> elsewhere. I've done that too, from time to time. This is one of the
> things made possible by the ABI contract being followed.
And nothing in that
On Thu, May 11, 2023 at 06:25:00PM +0200, Guilhem Moulin wrote:
> On Thu, 11 May 2023 at 18:12:52 +0200, Bastian Blank wrote:
> > Nope, not really. Half VG was never a real thing. It might work in
> > some cases.
> And these use-cases are unbootable since 2.03.15…
Those
On Thu, May 11, 2023 at 06:25:00PM +0200, Guilhem Moulin wrote:
> On Thu, 11 May 2023 at 18:12:52 +0200, Bastian Blank wrote:
> > Nope, not really. Half VG was never a real thing. It might work in
> > some cases.
> And these use-cases are unbootable since 2.03.15…
Those
On Wed, May 10, 2023 at 03:09:04AM +0200, Guilhem Moulin wrote:
> There might be a better way to detect an initramfs-tools environment
> than checking whether ‘/run/initramfs’ exists (and ‘/run/systemd/system’
> doesn't).
The only acceptable way would be a different udev rules file for the
On Wed, May 10, 2023 at 03:09:04AM +0200, Guilhem Moulin wrote:
> There might be a better way to detect an initramfs-tools environment
> than checking whether ‘/run/initramfs’ exists (and ‘/run/systemd/system’
> doesn't).
The only acceptable way would be a different udev rules file for the
Hi
Our next team meeting is scheduled for 2023-05-10 20:00 UTC. We'll be
on jitsi: https://jitsi.debian.social/DebianCloudMeeting20230510.
Regards,
Bastian
--
Another dream that failed. There's nothing sadder.
-- Kirk, "This side of Paradise", stardate 3417.3
Source: linux
Version: 6.1.25-1
Severity: important
Microsoft asked to backport the jumbo frame support in the Microsoft
Azure Network Adapter from current master. The changes are not suitable
for stable@ and contained to this one driver.
Commit ids are something like
Source: linux
Version: 6.1.25-1
Severity: important
Microsoft asked to backport the jumbo frame support in the Microsoft
Azure Network Adapter from current master. The changes are not suitable
for stable@ and contained to this one driver.
Commit ids are something like
Control: tags -1 wontfix
On Wed, Mar 30, 2022 at 08:17:51AM +, Thomas Wouters wrote:
> So I tried to reproduce it with `virt-install` to figure out what's
> going on and could replicate similar behavior: the cloud-init user-data
> is, by default (for x86), provided to the guest as a SATA
Control: tags -1 wontfix
On Wed, Mar 30, 2022 at 08:17:51AM +, Thomas Wouters wrote:
> So I tried to reproduce it with `virt-install` to figure out what's
> going on and could replicate similar behavior: the cloud-init user-data
> is, by default (for x86), provided to the guest as a SATA
Package: podman
Version: 4.4.0+ds1-1
Severity: normal
podman 4.4 introduces quadlet and with it "real" systemd style units to
manage containers. See https://www.redhat.com/sysadmin/quadlet-podman
Please install the quadlet binary and the appropriate symlinks to use it
as systemd generator (see
Package: podman
Version: 4.4.0+ds1-1
Severity: normal
podman 4.4 introduces quadlet and with it "real" systemd style units to
manage containers. See https://www.redhat.com/sysadmin/quadlet-podman
Please install the quadlet binary and the appropriate symlinks to use it
as systemd generator (see
On Mon, Apr 03, 2023 at 08:42:18AM +0200, Dirk Heinrichs wrote:
> So the request is to also ship the agent preinstalled in the Debian AMIs. See
> https://packages.ubuntu.com/search?keywords=ec2-hibinit-agent=names
> for Ubuntu (source) packages or
> https://github.com/aws/amazon-ec2-hibinit-agent
On Mon, Apr 03, 2023 at 08:42:18AM +0200, Dirk Heinrichs wrote:
> So the request is to also ship the agent preinstalled in the Debian AMIs. See
> https://packages.ubuntu.com/search?keywords=ec2-hibinit-agent=names
> for Ubuntu (source) packages or
> https://github.com/aws/amazon-ec2-hibinit-agent
On Sat, Mar 25, 2023 at 05:54:23PM +0100, наб wrote:
> Naturally, it should succeed in every scenario.
This is
https://www.kernel.org/doc/html/latest/admin-guide/sysctl/fs.html#protected-symlinks
Bastian
--
We have found all life forms in the galaxy are capable of superior
development.
On Sat, Mar 25, 2023 at 05:54:23PM +0100, наб wrote:
> Naturally, it should succeed in every scenario.
This is
https://www.kernel.org/doc/html/latest/admin-guide/sysctl/fs.html#protected-symlinks
Bastian
--
We have found all life forms in the galaxy are capable of superior
development.
On Sun, Mar 19, 2023 at 11:47:21PM +, James Addison wrote:
> Would it be fair to raise the severity of this bug to a release-critical
> level?
No, it would be fair to remove Geode LX from the set of supported
processors. Those are now over 15 years old.
Bastian
--
No one wants war.
On Sun, Mar 19, 2023 at 11:47:21PM +, James Addison wrote:
> Would it be fair to raise the severity of this bug to a release-critical
> level?
No, it would be fair to remove Geode LX from the set of supported
processors. Those are now over 15 years old.
Bastian
--
No one wants war.
Upstream changed the default for the DNSSEC option to "allow-downgrade"
and that is whats everywhere is documented. Debian overrides it to
"no".
Bastian
--
Prepare for tomorrow -- get ready.
-- Edith Keeler, "The City On the Edge of Forever",
stardate unknown
Upstream changed the default for the DNSSEC option to "allow-downgrade"
and that is whats everywhere is documented. Debian overrides it to
"no".
Bastian
--
Prepare for tomorrow -- get ready.
-- Edith Keeler, "The City On the Edge of Forever",
stardate unknown
Package: systemd-resolved
Version: 252.5-2
Severity: important
systemd-resolved now replaces /etc/resolv.conf to point to the stub
resolver. This resolver is not equivalent to the existing external one
in terms of DNSSEC check.
The resolv.conf now includes "trust-ad", however the stub resolver
Package: systemd-resolved
Version: 252.5-2
Severity: important
systemd-resolved now replaces /etc/resolv.conf to point to the stub
resolver. This resolver is not equivalent to the existing external one
in terms of DNSSEC check.
The resolv.conf now includes "trust-ad", however the stub resolver
Control: affects -1 src:debian-cloud-images
This modification of global configuration breaks the building of cloud
images. We need a way to install the package, but no services will run
in the environment, nor is there a systemd-resolved in the same network
namespace.
The build does not exhibit
Control: affects -1 src:debian-cloud-images
This modification of global configuration breaks the building of cloud
images. We need a way to install the package, but no services will run
in the environment, nor is there a systemd-resolved in the same network
namespace.
The build does not exhibit
/changelog2023-03-19 11:54:54.0 +0100
@@ -1,3 +1,10 @@
+systemd (253-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove broken resolv.conf setup. (closes: #1032937)
+
+ -- Bastian Blank Sun, 19 Mar 2023 11:54:54 +0100
+
systemd (253-1) experimental; urgency=medium
/changelog2023-03-19 11:54:54.0 +0100
@@ -1,3 +1,10 @@
+systemd (253-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove broken resolv.conf setup. (closes: #1032937)
+
+ -- Bastian Blank Sun, 19 Mar 2023 11:54:54 +0100
+
systemd (253-1) experimental; urgency=medium
Control: severity -1 serious
Let's make this RC, as it breaks updates.
The systemd-resolved package modifies a global config file
/etc/resolv.conf. This breaks any name resolution if resolved is not
running. Especially if it can't run at all.
| root@debian-sid:~# ls -al /etc/resolv.conf
|
401 - 500 of 14587 matches
Mail list logo
