Source: linux
Version: 5.10.46-3
Severity: wishlist
Tags: patch
At
https://salsa.debian.org/raspi-team/image-specs/-/issues/7#note_206349
it was reported that CPU frequency scaling was enabled for armhf and
arm64, but not for armel. I (and others) have been able to confirm that.
So I build my
On vrijdag 6 augustus 2021 16:07:18 CEST Diederik de Haas wrote:
> > > -CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
> > > +# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
> > > -# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
> > > +CO
On donderdag 5 augustus 2021 19:26:09 CEST Diederik de Haas wrote:
> I 'heard' that the schedutil governor is good for big.little CPUs, but
On my amd64 machine (with Ryzen 1800X CPU) 'schedutil' is enabled and set as
default, so the above statement is a bit too simplistic.
> the RPi
Control: tag -1 fixed-upstream patch
I ran into this problem too at the exact same step of a kernel build.
Upstream author responded with
"Thanks. Fixed in dfc801c44a93bed7b3951905b188823d6a0432c8"
https://lists.gnu.org/archive/html/bug-cpio/2021-08/msg3.html
On vrijdag 30 juli 2021 17:22:06 CEST Jan Huijsmans wrote:
> ** Command line:
> ... root=/dev/sda1
I'm assuming you're the same person as in #984873, but iirc my mail to you wrt
that bug report bounced and hasn't received an answer.
Given that you're now booting from USB (again), it may be
On vrijdag 30 juli 2021 21:28:54 CEST Diederik de Haas wrote:
> On vrijdag 30 juli 2021 17:22:06 CEST Jan Huijsmans wrote:
> I'm assuming you're the same person as in #984873, but iirc my mail to you
> wrt that bug report bounced and hasn't received an answer.
And that mail bounced as
Hi,
On vrijdag 6 augustus 2021 15:14:26 CEST Uwe Kleine-König wrote:
> On Thu, Aug 05, 2021 at 05:26:09PM +0000, Diederik de Haas wrote:
> > https://salsa.debian.org/raspi-team/image-specs/-/issues/7#note_206349
> >
> > So I build my own kernel wit
On Wed, 25 Aug 2021 13:45:03 +0300 Michael Tokarev wrote:
> Yes I want to push this to -stable. However I also want to include
> fixes for one or two other security issues found recently.
> Hopefully I'll manage to do this today.
On donderdag 16 september 2021 20:27:18 CEST Adam D. Barratt
Control: tag -1 -newcomer
Control: tag -1 -upstream
On woensdag 22 september 2021 21:50:16 CEST Chuck Zmudzinski wrote:
> Finally, I tag the bug newcomer simply because there is a known solution but
That's what the 'patch' tag is for. 'newcomer' is similar to 'good first
issue',
which this is
Control: affects -1 - apt-listbugs
On 01 Oct 2021 21:05:09 +0200 Diederik de Haas wrote:
> Control: affects -1 apt-listbugs
>
> When I do an 'aptitude safe-upgrade' on my Sid machine, apt-listbugs wants
> to retrieve (RC) bug information about the packages to be upgraded.
My issu
Control: tag -1 patch
On Friday, 8 October 2021 10:43:14 CEST Diederik de Haas wrote:
> In kernel 5.13 on my Rock64, `pactl list cards` correctly identified my
> AVR (SC-1224) and had various multichannel audio profiles I could choose
> from. Since kernel 5.14, `paclt list cards`
Control: forwarded -1 https://lore.kernel.org/all/4974503.Y8KB3sNASq@bagend/
signature.asc
Description: This is a digitally signed message part.
On Saturday, 9 October 2021 21:28:19 CEST Diederik de Haas wrote:
> I'll try later whether I can reliably reproduce it with hibernate mode.
That appears to be the case. Hibernated my PC yesterday and started it up
today. After some time, I got the msgs again, this time also in dmesg:
# dm
Package: src:linux
Version: 5.14.9-2
Followup-For: Bug #955407
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I had seen this issue before too and actually had a knuckle and assumed
it was a one-time thing. But I've had 2 more in the last 2 days.
It *may* be related to hibernation as I usually
On Thursday, 21 October 2021 12:41:34 CEST Salvatore Bonaccorso wrote:
> On Thu, Oct 21, 2021 at 09:38:00AM +, Daniel Black wrote:
> > Package: src:linux
> > Version: 5.14.12-1
> > The good news is I've validated that the linux mainline 5.14.14 build
> > from
On 7 Oct 2021 18:35:18 +0200 Francesco Poli wrote:
> This seems to be exactly the same issue that was reported in #995448,
> which is marked as affecting package apt-listbugs.
>
> However, I see that you are using oldstable: I don't know whether a
> fixed version of ruby-httpclient will ever be
Control: affects -1 libaudit-dev
On 24 Feb 2021 17:09:48 -0300 Antonio Terceiro wrote:
> Package: libcap-ng-dev
> Tags: patch
>
> libcap-ng-dev is missing the `Multi-Arch: same` field. This makes it
> impossible to co-install libcap-ng-dev from two architectures.
And as libcap-ng-dev is a
Source: linux
Version: 5.14-1~exp1
Severity: normal
Tags: upstream
In kernel 5.13 on my Rock64, `pactl list cards` correctly identified my
AVR (SC-1224) and had various multichannel audio profiles I could choose from.
Since kernel 5.14, `paclt list cards` no longer identifies my AVR and I
only
On Monday, 27 September 2021 19:13:04 CEST Andy Smith wrote:
> I think the "auto" directory is a pretty good and simple interface,
> so how about using it for save/shutdown as well? So, instead of just
> enumerating all running domids, enumerate all files in
> /etc/xen/auto/ in REVERSE order,
Hi,
On vrijdag 6 augustus 2021 16:07:18 CEST Diederik de Haas wrote:
> On vrijdag 6 augustus 2021 15:14:26 CEST Uwe Kleine-König wrote:
> > On Thu, Aug 05, 2021 at 05:26:09PM +, Diederik de Haas wrote:
> > > https://salsa.debian.org/raspi-team/image-specs/-/is
Hi Andy,
On Wednesday, 29 September 2021 00:02:46 CEST Andy Smith wrote:
> On Tue, Sep 28, 2021 at 11:39:49PM +0200, Diederik de Haas wrote:
> The idea of the domid controlling/influencing order of shutdown
It was just an idea that popped in my head. All in all I've likely spen
Hi Andy,
On Tuesday, 28 September 2021 13:41:57 CEST Andy Smith wrote:
> > If that's correct, then I find it more logical to do *everything* in
> > reverse. The VM that was started first, should be saved/shutdown last and
> > IIUC your proposal would not do that.
>
> No, that's what I am
On Wed, 06 Oct 2021 14:14:28 + Antonio Terceiro
wrote:
>
> Add patch to use the system certificate store
>
> Closes: #995448
>
You can add
On dinsdag 21 september 2021 01:15:15 CEST Elliott Mitchell wrote:
> Merely having the path is a sufficiently strong indicator for me to
> simply wave it past. I though would suggest Debian should instead
> cherry-pick commit 0f089bbf43ecce6f27576cb548ba4341d0ec46a8.
>
> This is available as a
Control: affects -1 apt-listbugs
When I do an 'aptitude safe-upgrade' on my Sid machine, apt-listbugs wants to
retrieve (RC) bug information about the packages to be upgraded.
But that now fails:
# aptitude safe-upgrade
The following packages will be upgraded:
libpam-systemd
On Saturday, 2 October 2021 15:56:33 CEST Chuck Zmudzinski wrote:
> I agree package maintainers must have a say. and as far as I can tell the
> Release Team has the final say on what goes into the stable release.
The reason I responded at all was that AFAIK the RT indeed has the right to
make
On Monday, 4 October 2021 11:46:54 CEST Hans van Kranenburg wrote:
> The 4th one is not explicitly tagged with Fixes: 1c4aa69ca1e1, but I
> agree with Diederik that we should keep them all together.
Context: Those 4 are part of 1 patch-set posted here:
On Monday, 4 October 2021 17:27:22 CEST Chuck Zmudzinski wrote:
> I can confirm these 4 fix the bug on my hardware.
\o/
Thanks for testing and reporting back :-)
Cheers,
Diederik
signature.asc
Description: This is a digitally signed message part.
On Fri, 1 Oct 2021 15:19:48 -0300 Antonio Terceiro
wrote:
> On Fri, Oct 01, 2021 at 07:43:35PM +0200, Michael Biebl wrote:
> > Am 01.10.21 um 19:27 schrieb Antonio Terceiro:
> > > I tracked this down to an issue between apt-listbugs (or ruby-soap4r, or
> > > something else below that) and
On Tuesday, 5 October 2021 18:45:39 CEST Francesco Poli wrote:
> > I ran 'reportbug apt-listbugs' and so I found this bug. It also shows
> > 995432. (I usually use the web interface to see whether 'my' issue has
> > already been found, but it doesn't show up there)
>
> For the record, this bug
Control: tag -1 pending
On 14 Sep 2021 02:16:18 +0200 Diederik de Haas wrote:
> At https://salsa.debian.org/kernel-team/linux/-/merge_requests/390
> I submitted a MR which makes this trigger builtin on arm* platforms.
That MR got merged into the 'master' branch with:
https://salsa.debi
On donderdag 23 september 2021 21:54:49 CEST Chuck Zmudzinski wrote:
> While I did respond point by point privately to the author
Don't do that. Any discussion relevant to the bug should be sent to the bug
itself so that everyone has all the relevant information.
I actually learned myself how
Hi Elliott,
On zondag 26 september 2021 05:27:07 CEST Elliott Mitchell wrote:
> I checked out the Debian Xen source via git. I got the current
> "master" branch which is presently the candidate 4.14.3-1 version,
> which includes urgent fixes. The hash is:
>
Package: bash-completion
Version: 1:2.11-3
Severity: normal
Tags: patch upstream fixed-upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I wanted to invoke `pyvenv` on my Sid system with Python 3.9, but that
didn't work. The `ls` command told me why:
$ ls -l
Hi Ryutaroh,
On zondag 22 augustus 2021 06:02:57 CEST Ryutaroh Matsumoto wrote:
> I redid vmdb run and again got errors as attached.
> qemu-user-static are from bullseye and sid.
> Both trial failed.
Thanks for your tests, it does look like a different problem then.
Hopefully things are better
Hi Release Team,
I want to make sure that you're aware of what I consider HIGHLY inappropriate
behavior by Chuck where he is trying to sidestep/override the Xen maintainers
by filing this bug directly to the release.debian.org pseudo package.
This only appeared on the Debian Xen maintainers'
Hi Dean,
On Mon, 21 Nov 2016 10:58:25 +1100 Dean Hamstead wrote:
> Package: vagrant-lxc
> Version: 1.2.1-2
>
> When vagrant-lxc places its authorized_keys file in to a new centos7 vm's
> ~vagrant/.ssh directory, it does so with too permissive ownership.
> As a result, the centos7 vm's ssh wont
Control: tag -1 upstream fixed-upstream
On 14 Oct 2021 20:57:27 -0300 Antonio Terceiro wrote:
> Source: vagrant
> Version: 2.2.14+dfsg-1
> Severity: serious
> Justification: FTBFS
> Usertags: ruby3.0
https://github.com/hashicorp/vagrant/pull/12427 is titled "Updates for Ruby
3.0" and is part
Source: linux
Version: 5.10.1-1_exp1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
In commit aa87da1f902dba04f3b15680e178ad336e985f4f titled "Enable all
Industrial I/O ADC" various IIO ADC drivers which were enabled for armhf
and arm64 got disabled, while a whole bunch of
Control: forwarded -1
https://lists.01.org/hyperkitty/list/i...@lists.01.org/thread/ZP5J2JEPF4YPOMH6XG6VUV2GYNAHCPXF/
On Friday, 24 December 2021 16:48:57 CET Jonas Smedegaard wrote:
> I agree that it would be helpful if the iwd package included a
> system-wide default config file, even if
Package: iwd
Version: 1.20-3
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I needed the "EnableNetworkConfiguration=true" setting, which IIUC
should be done in /etc/iwd/main.conf, but I noticed that that file
and directory didn't exist. I resolved it by using mkdir and creating
On Sun, 16 May 2021 15:46:55 +0200 Nicolas Évrard wrote:
> Package: foot
> Version: 1.6.4-1
> Severity: wishlist
The current latest version is 1.10.3 and it would be great if made available:
https://codeberg.org/dnkl/foot/releases/tag/1.10.3
Cheers,
Diederik
signature.asc
Description: This
Package: python3-serial-asyncio
Version: 0.5-2
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2021-10-01 version v0.6 has been released, so hereby the request to
package that for Debian.
Thanks in advance :-)
Diederik
- -- System Information:
Debian Release:
Hi Jonas,
On Monday, 27 December 2021 19:27:29 CET Diederik de Haas wrote:
> Control: forwarded -1
> https://lists.01.org/hyperkitty/list/i...@lists.01.org/thread/ZP5J2JEPF4YPOM
> H6XG6VUV2GYNAHCPXF/
> On Friday, 24 December 2021 16:48:57 CET Jonas Smedegaard wrote:
> > I a
Hi Paul,
On Thursday, 11 November 2021 14:56:29 CET Paul Gevers wrote:
> Nice screenshot. For the record, that hint wasn't there on my system.
> The other settings are the same, minus I have "OpenGL 2.0" as "Rendering
> backend".
It was my assumption that you (and others) didn't get that hint,
I put "*ERROR* Failed to wait for idle; VT'd may hang" into a search engine
and found the following:
Second result was https://bugs.archlinux.org/task/65362 which said:
"The change to CONFIG_INTEL_IOMMU_DEFAULT_ON=yes on 5.5.1.arch1-1 causes
random system freezes" and a possible workaround is:
On Sun, 07 Nov 2021 23:25:11 +0100 Christoph Anton Mitterer
wrote:
> Package: busybox
> Version: 1:1.30.1-7+b1
>
> Unlike mandated by POSIX:
> https://pubs.opengroup.org/onlinepubs/9699919799/utilities/tr.html
>
> busybox' tr in Debian doesn't seem to understand any of the character
>
Package: busybox
Version: 1:1.30.1-7+b1
Severity: important
Tags: security upstream fixed-upstream
X-Debbugs-Cc: Debian Security Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
https://security-tracker.debian.org/tracker/source-package/busybox
already shows them. I learned it through
On Fri, 5 Nov 2021 05:55:52 +0100 Florian Schlichting wrote:
> Hi Ryan (and Max please see below):
>
> please, for now, delete or comment out the pid_file line
I'm responding to this bug as commenting out the pid_file line was the solution
for me too, but my 'symptoms' are (a bit) different.
On Wed, 28 Jul 2021 16:52:47 +0200 Pim wrote:
> This issue looks similar:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991453
Indeed, the symptoms sound very familiar.
According to the other bug report, it was a kernel issue which got fixed with
5.10.46-3, so the most likely case is
On Sun, 17 Oct 2021 13:10:19 -0400 Andres Salomon wrote:
> Package: firmware-brcm80211
> Version: 20210315-3
> Severity: normal
>
> This bug is mostly for documentation purposes.
>
> When running a raspberry pi 4b as an access point, after a random
> period of time the on-chip firmware will
On Sat, 04 Sep 2021 19:50:56 +0100 Rob wrote:
> OK so I think I've got to the bottom of it.
>
> If you:
> - purge all deluge packages (i.e. rm -R /var/lib/deluged)
> - reinstall all the packages
> - then patch the log.py as mentioned previously
>
> It then seems to be in a working state, so I
Control: affects -1 + tldr
Got the same error msg when running tldr. Downgrading to the testing version
fixed it (aptitude install libcmark0.30.1=0.30.1-2).
signature.asc
Description: This is a digitally signed message part.
On Thu, 28 Oct 2021 14:15:56 +0200 Jonas Smedegaard wrote:
> Quoting Peter Keel (2021-10-28 11:05:19)
> > It may be that this is fixed in the package, but packages depending
> > on libcmark0.30.1 providing 0.30.1 and not 0.30.2 are now broken:
> >
> > mkvtoolnix-gui: error while loading shared
Package: lxc
Version: 1:4.0.10-1
Severity: normal
Tags: upstream fixed-upstream patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Earlier today I ran lxc-checkconfig and then I got this:
$ lxc-checkconfig
LXC version 4.0.10
Kernel configuration not found at /proc/config.gz; searching...
Hi,
On Sunday, 7 November 2021 13:08:38 CET Matthew Vernon wrote:
> On 24/12/2020 11:56, Diederik de Haas wrote:
> > On my system I have the 8/16/32 bit versions of the pcre2 library
> > installed.
> > The discription only tells me that this is the 8-bit runtime version.
&
Package: libreoffice
Version: 1:7.2.2-1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I encountered this issue first with version 1:7.2.2-1, so I changed the
Version field, but the problem is still present with 1:7.3.0~alpha1-3.
I was/am creating a document and I wanted to
Package: libreoffice
Version: 1:7.3.0~alpha1-3
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I wanted to file another bug (wishlist/normal), but then reportbug
mentioned/recommended to try the latest version (from experimental), so
I did
Control: tag -1 upstream fixed-upstream
On Sat, 23 Oct 2021 21:50:07 +0200 Lucas Nussbaum wrote:
> Source: pelican
> Version: 4.0.1+dfsg-1.1
> Severity: serious
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> Exception
On Sunday, 31 October 2021 23:42:13 CET shirish शिरीष wrote:
> I am running yakuake on Debian-mate. But it seems that in the
> notification area for some reason yakuake is not seen :( . Sharing a
> screenshot of the notification area.
I'm running fully KDE and I don't have a notification entry
On Monday, 1 November 2021 11:57:52 CET shirish शिरीष wrote:
> Because there is no notification, it is difficult to know when Yakuake
> has started or not.
AFAIK it's always started as soon as you log in.
I would actually find an item in the notification area/systray a regression/bug
as it's
Control: Forwarded -1
https://lore.kernel.org/linux-block/cabvffennj8jkp7etuutqi+vkjdbfu37w1uxe4q3cb7-ixxh...@mail.gmail.com/
On Saturday, 23 October 2021 23:29:21 CEST Daniel Black wrote:
> https://marc.info/?l=linux-block=163489378723217=2
Looked up your upstream message on lore.k.o and set
On Sun, 28 Mar 2021 21:11:49 +0200 Gianfranco Costamagna
wrote:
> control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27659
> control: affects -1 src:binutils
https://sourceware.org/bugzilla/show_bug.cgi?id=27659#c17 seems to indicate
that the issue should be resolved (in
Package: xen-tools
Version: 4.9-1
Severity: normal
I have recently created a Jessie VM and noticed that there was (quite) a
difference between the kernel I expected and the one that I had.
I just learned that those are uploaded to security.debian.org, so I
enabled the security repo lines in
Hi Axel,
On Sunday, 24 October 2021 02:08:46 CEST Axel Beckert wrote:
> Diederik de Haas wrote:
> > enabled the security repo lines in /etc/apt/sources.list. But when doing
> > 'aptitude update', it reported that it couldn't find the repo.
> > Turns out that it uses 'j
Control: fixed -1 1:4.0.10-1
On Tue, 07 Sep 2021 20:21:12 -0400 Kyle wrote:
> Package: lxc
> Version: 1:4.0.6-2
>
> lxc-create fails with the following error message caused by
> sks-keyservers.net going offline, The lxc package currently in testing
> includes a patch that fixes the issue by
Control: tag -1 fix-upstream
The mentioned commit is fixed in upstream version 1.33.1 and 1.34.0.
signature.asc
Description: This is a digitally signed message part.
Hi James,
On Sat, 7 Oct 2017 22:41:41 +0100 James Clarke wrote:
> Forwarded: http://lists.busybox.net/pipermail/busybox/2017-October/
085870.html
>
> Currently busybox FTBFS on the Hurd and GNU/kFreeBSD. I have submitted
> the above patch series upstream to fix this.
Of the 7 patches you
Control: tag -1 -pending
On Sun, 29 Jul 2018 08:36:41 + Nobuhiro Iwamatsu
wrote:
> Control: tag -1 pending
>
> Bug #896902 in busybox reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below, and you can check the diff of the
On zaterdag 25 juli 2020 17:12:54 CEST Michael Tokarev wrote:
> The goal is to remove `qemu' binary metapackage
https://tracker.debian.org/pkg/qtemu shows that qtemu was removed from
testing/unstable/experimental on 22/23 December *2016* and only oldstable has
the package.
So I don't know what
lid-until=no]
https://snapshot.debian.org/archive/debian/20210529T204006Z/ sid main
Installed linux-image-5.10.0-7-amd64 and rebooted into that ...
On zaterdag 24 juli 2021 14:22:38 CEST Diederik de Haas wrote:
> On zaterdag 24 juli 2021 01:29:55 CEST piorunz wrote:
> > GPU core works at
Control: tags -1 confirmed
On zaterdag 24 juli 2021 01:29:55 CEST piorunz wrote:
> GPU core works at 100% usage at all times, even at idle.
>
> $ cat /sys/class/drm/card0/device/gpu_busy_percent
> 99
>
> $ sensors
> (...)
> amdgpu-pci-0900
> Adapter: PCI adapter
> vddgfx:1.14 V
> fan1:
On zaterdag 24 juli 2021 22:03:23 CEST Diederik de Haas wrote:
> > It's already backported to 5.10, just after 5.10.46 was released:
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h
> > =l inux-5.10.y=fea853aca3210c21dfcf07bb82d501b7fd1900a7
&
On zondag 25 juli 2021 00:48:41 CEST Davide Beatrici wrote:
> Package: linux-image-5.10.0-8-amd64
> Version: 5.10.46-2
>
> As soon as the screen resolution changes, all LEDs (GPUTach) on the side of
> my Vega 56 light up and never turn off again, indicating a constant 100%
> utilization.
>
> The
Package: vmdb2
Version: 0.22-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: pkg-raspi-maintain...@lists.alioth.debian.org
"deprecate qemu-debootstrap" is the primary commit message of:
https://salsa.debian.org/qemu-team/qemu/-/commit/9899b1723119e57354c5d8e6f68f15ed762bd570
And it change the
On Sunday, 9 January 2022 21:24:50 CET Jonas Smedegaard wrote:
> > Got a reply on that list [1] that the following commit was added:
> > https://git.kernel.org/pub/scm/network/wireless/iwd.git/commit/?id=04fccea
> > 63bd42b0b72587df9edee72d677b6ca7d
> >
> > And then the following question which
On Friday, 7 January 2022 09:38:46 CET Dominique Dumont wrote:
> Error! Bad return status for module build on kernel: 3.16.0-6-amd64 (x86_64)
> Consult /var/lib/dkms/open-vm-tools/2012.05.21/build/make.log for more
> information.
> ...
> Turns out that the compilation failure happens because dkms
On Monday, 10 January 2022 01:24:59 CET Ben Hutchings wrote:
> You'll be pleased to hear that in master, zstd with compression level 9
> is now the default.
Shouldn't the Recommends be on libzstd1 instead of on zstd?
Because the zstd package also supports and depends on liblz4-1, liblzma5 and
On Monday, 10 January 2022 11:10:52 CET Diederik de Haas wrote:
> On Monday, 10 January 2022 01:24:59 CET Ben Hutchings wrote:
> > You'll be pleased to hear that in master, zstd with compression level 9
> > is now the default.
>
> Shouldn't the Recommends be on libzst
Package: iwd
Version: 1.21-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
When version 1.21-1 was uploaded, the buildd failed for all the release
architecures. Looking into several of them, I found that they failed on
the same test:
"test-dpp: unit/test-dpp.c:114:
On 05 Feb 2021 12:37:04 +0100 Michele Cane wrote:
> Package: network-manager
>
> Reading on the previous echanges tehre was a mention of NM not developing/
> maintaining iwd backend but I see that they have recent commits (Nov 2020)
>
> It would be great if we could reconsider this discussion,
On Monday, 10 January 2022 18:05:51 CET Michael Biebl wrote:
> On 10.01.22 17:36, Diederik de Haas wrote:
>
> > On 05 Feb 2021 12:37:04 +0100 Michele Cane
> > wrote:
> >
> >> Package: network-manager
> >>
> >> Reading on the previous ech
On 11 January 2022 19:17:56 CET Jonas Smedegaard wrote:
> Quoting Diederik de Haas (2022-01-11 16:39:47)
> > One of the upstream maintainers ran a build and reported that 22 tests
> > ran and they all succeeded. On buildd 1 test out of *20* failed.
>
> The Debian package
On Thu, 21 Oct 2021 05:11:36 +0200 Cyril Brulebois wrote:
> Package: raspi-firmware
>
> Looking at #980536, and if I'm reading between the lines correctly, the
> whole Pi 4 family should have no cma= setting, and we should be skipping
> it on the Compute Module 4 the same way we do on the Pi 4.
Package: raspi-firmware
Version: 1.20220120+ds-1
Severity: grave
Hi,
This is a 'dummy' RC bug to prevent version 1.20220120+ds-1 from transitioning
to testing. Just now on IRC we identified a bug which I don't consider RC in
itself, but the upstream issue tracker indicate various issue with
On Wednesday, 16 February 2022 00:08:39 CET Cyril Brulebois wrote:
> By the way, I still have a branch somewhere with relevant commits for the Pi
> 4:
> https://salsa.debian.org/debian/raspi-firmware/-/commit/e8b64797f3852e5a133
> d839407e36f6e9c839399
>
Hi Antti,
On Friday, 4 March 2022 16:46:23 CET Antti Kultanen wrote:
> > I see the following in /etc/nfs.conf in the [nfsd] section:
> > # vers2=n
> > vers3 and higher all have '=y', so maybe it's only disabled by default?
>
> Hi Diederik, unfortunately NFSv2 has been removed in the upstream.
>
Hi Damien,
On Sunday, 6 March 2022 23:26:03 CET Diederik de Haas wrote:
> Upstream commit 68dbbe7d5b4fde736d104cbbc9a2fce875562012 [1]
> seems potentially relevant (included in 5.16-rc1), but given ...
>
> On Saturday, 5 March 2022 17:59:50 CET Petra R.-P. wrote:
> > The "
On Monday, 21 February 2022 17:25:33 CET Petra Rübe-Pugliese wrote:
> > if yes, can you remote if from the kernel command line and see
> > if you get more information on the screen?
>
> How would that be done?
If you do "cat /proc/cmdline" and see the word 'quiet' in there, then it's not
as
Hi Petra,
On Saturday, 5 March 2022 21:12:12 CET Petra R.-P. wrote:
> On Sat 05 Mar 2022 at 18:23:52 +0100 Diederik de Haas
> wrote:
> > On Monday, 21 February 2022 17:25:33 CET Petra Rübe-Pugliese wrote:
> [...]
>
> > So if you remove the 'quiet' word the
Control: forwarded -1
https://lists.xenproject.org/archives/html/xen-devel/2022-03/msg00864.html
On Friday, 11 March 2022 06:19:58 CET Chuck Zmudzinski wrote:
> So I was able to propose this patch to the xen-devel mailing list.
I've set that mail as the forwarded address. If you think that's
On Friday, 11 March 2022 15:18:09 CET Chuck Zmudzinski wrote:
> > Normally it is used when the maintainer needs more info from the submitter
> > to make progress on resolving the bug. And is therefor set by the
> > maintainer, not by the submitter, ie you.
> > See
Package: mplayer
Version: 2:1.4+ds1-3+b1
Followup-For: Bug #920485
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
When I first read the bug title, I played an .ogg music file and that
went fine. After reading the bug report, I learned it was with ogv
file(s), i.e. ogg video files.
I DL-ed the
Control: retitle -1 mplayer gets signal 6 when playing ogg video files (.ogv)
signature.asc
Description: This is a digitally signed message part.
On 16 Feb 2022 23:25:00 +0100 Sebastian Ramacher wrote:
> Source: mplayer
> Version: 2:1.4+ds1-3
> Severity: serious
> Tags: sid bookworm
>
> I think we should not include mplayer in bookworm.
> mpv is a worthy replacement for mplayer.
I do use mpv to play ~ all my video files, but I also
Control: forwarded -1 https://github.com/raspberrypi/firmware/issues/1705
On Tue, 15 Mar 2022 10:49:10 -0600 Gunnar Wolf wrote:
> Package: raspi-firmware
> Version: 1.20220120+ds-1
> Severity: important
> Tags: upstream
As the issue has already been reported upstream, I'm linking that here in
On 28 Oct 2021 23:11:22 +0200 Diederik de Haas wrote:
> Package: lxc
> Version: 1:4.0.10-1
> Tags: upstream fixed-upstream patch
>
> This was easy to fix, so I submitted the following PRs upstream:
> https://github.com/lxc/lxc/pull/4019
> https://github.com/lxc/lxc/pull/
Package: nodejs
Version: 12.22.10~dfsg-1
Severity: serious
Justification: Policy 7.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm not entirely sure, but I _think_ this issue should be fixed with
some Breaks+Replaces relation and a quick search showed para 7.3.
Got an update to the above
On 14 Mar 2022 17:15:18 +0100 Diederik de Haas wrote:
> Package: nodejs
> Version: 12.22.10~dfsg-1
> Severity: serious
> Justification: Policy 7.3
>
> I'm not entirely sure, but I _think_ this issue should be fixed with
> some Breaks+Replaces relation and a quick search show
On 10 Mar 2020 08:40:49 +0100 Gian Piero Carrubba wrote:
> While upgrading samba-common-bin from 2:4.11.5+dfsg-1 to 2:4.11.5+dfsg-1+b1:
>
> ---
> Performing actions...
> Setting up samba-common-bin (2:4.11.5+dfsg-1+b1) ...
> Checking smb.conf with testparm
> Load smb config files from
701 - 800 of 1660 matches
Mail list logo
