There's an upstream commit (part of 5.12) that Vincent referenced that nicely
illustrates the difference between what I want to achieve with this bug report
and a possible solution applied in that commit (IIUC):
Package: parted
Version: 3.4-1
Severity: important
X-Debbugs-Cc: freedombox-disc...@alioth-lists.debian.net
I first noticed this when trying to make an improvement to
freedom-maker, hence FB-discuss in CC, while this issue didn't present
itself with the Raspberry Pi image specs project.
The
Here's the related freedom-maker issue I created about this:
https://salsa.debian.org/freedombox-team/freedom-maker/-/issues/196
Linking it for completeness; the bug report and script contained therein is
the result of further research into this, so it can easily be reproduced.
signature.asc
Package: qemu-user-static
Version: 1:5.2+dfsg-10
Severity: normal
File: /usr/bin/qemu-aarch64-static
X-Debbugs-Cc: pkg-raspi-maintain...@lists.alioth.debian.org
When trying to build an arm64 image for Raspberry Pi image specs
(https://salsa.debian.org/raspi-team/image-specs) I and others have
Control: fixed -1 1:6.0+dfsg-1~exp0
Control: tag -1 patch
Control: tag -1 upstream
Control: tag -1 bullseye
I've now done several runs spread over several days and they all succeeded, so
that alone would indicate that the issue is resolved with the 6.0 version.
On top of that, Bernhard Übelacker
Hi Chris,
On zaterdag 22 mei 2021 17:14:34 CEST Christopher Obbard wrote:
> We're facing the same (similar?) problem with Debos - in some cases
> the qemu-user process seems to segfault.
>
> Looks like a new version of qemu is in experimental - which has some
> changes to linux-user/mmap.c
>
>
On zaterdag 22 mei 2021 20:58:12 CEST Diederik de Haas wrote:
> On zaterdag 22 mei 2021 17:14:34 CEST Christopher Obbard wrote:
> > Looks like a new version of qemu is in experimental - which has some
> > changes to linux-user/mmap.c
> > Perhaps it would be a good idea to se
Hi Bernhard,
On zaterdag 22 mei 2021 00:11:22 CEST Bernhard Übelacker wrote:
> > Architecture: amd64 (x86_64)
>
> The subject on the email mentions "on arm64".
> From the Architecture line I assume this should read "on amd64"?
No.
While I build my images on an amd64 machine, the problem (so
Control: found -1 5.10.46
Control: tag -1 upstream patch
commit 44dd5e2106dc2fd01697b539085818d1d1c58df0 from 5.13
commit bbac8bd65f5402281cb7b0452c1c5f367387b459 from linux-next from 20210701
Those 2 patches make USB3 work on the Rock64 :)
signature.asc
Description: This is a digitally signed
Control: found -1 5.10.46-1
signature.asc
Description: This is a digitally signed message part.
001
From: Diederik de Haas
Date: Sun, 23 May 2021 23:53:22 +0200
Subject: [PATCH 4/4] Enable Power Management ICs for RK805 components.
https://www.cnx-software.com/pdf/Rockchip-Roadmap-2019-.11_mts.pdf
says on page 3 that RK805 is used for RK3328/RK3228 SOCs and
Pine64's Rock64 is a SBC that u
An upload for 'live-config' closed the wrong bug number, it should have been
990391, but 990390 was specified in live-config's upload, closing the wrong bug.
signature.asc
Description: This is a digitally signed message part.
On zondag 11 juli 2021 17:42:27 CEST Steve McIntyre wrote:
> >If an error is detected, a message like "Look at this wiki page for
> >possible solutions", with the solution you just provided me (among others),
> >would be really helpful.
> >I've made/attached screenshots which could be used for
On zondag 11 juli 2021 02:31:19 CEST Steve McIntyre wrote:
> Hi Diederik,
Hi Steve,
> On Sat, Jul 10, 2021 at 01:48:53AM +0200, Diederik de Haas wrote:
> >dpkg: error processing package shim-helpers-arm64-signed (--configure):
> > installed shim-helpers-arm64-signed package
On 2020-09-28 23:51:47 +0200 Sebastian Ramacher wrote:
> Source: alsa-plugins
> Version: 1.2.2-2
> Usertags: libavresample-removal
> Control: block 971318 by -1
>
> alsa-plugins currently Build-Depends or Depends on libavresample-dev.
> The ffmpeg developers consider libavresample as obsolete
Package: shim-helpers-arm64-signed
Version: 1+15.4+6
Severity: important
Running 'aptitude safe-upgrade' on my Bullseye/Sid/Experimental system
fails:
Unpacking shim-unsigned (15.4-6) over (15.4-5) ...
Preparing to unpack .../3-shim-helpers-arm64-signed_1+15.4+6_arm64.deb ...
Unpacking
I filed the following bug which may be related?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990867
Even though the (error) messages are/seem quite different, maybe
the 'Read-only file system' message is also kernel related?
I don't know the details anymore, but I've seen 'efivars' come by
On zondag 27 juni 2021 22:37:10 CEST Salvatore Bonaccorso wrote:
> Let's ask the release team instead. Here my arguments why: nfs-utils
> needs a major rehaul, this was not possible to finish in time for
> bullseye, so this means nfs-utils is generally in not a very good
> shape for
Source: linux
Version: 5.10.28-1
Severity: wishlist
https://github.com/torvalds/linux/commit/ddf3fa8b8a16e076f247c115a73356b4b0d83a33
is titled: "arm64: defconfig: Enable CONFIG_SND_AUDIO_GRAPH_CARD"
and the secondary commit msg is
"CONFIG_SND_AUDIO_GRAPH_CARD is needed to use HDMI sound with
On Wed, 21 Apr 2021 06:31:00 -0400 Braiam Peguero wrote:
> Package: python3-libtorrent
> Trying to move a torrent using deluge-console results in the following
> error:
>
> ArgumentError
> Python argument types in
> torrent_handle.move_storage(torrent_handle, str)
> did not match C++
On Thu, 22 Oct 2020 13:58:06 +0200 Kurt Roeckx wrote:
> Would it be possible to get chrony 4.0 in buster backports?
Buster backports now has 4.0-5~bpo10+1, so I guess this bug can be closed?
Control: found -1 5.10.13-1
signature.asc
Description: This is a digitally signed message part.
Control: forwarded -1
https://lists.infradead.org/pipermail/linux-rpi-kernel/2021-February/008002.html
signature.asc
Description: This is a digitally signed message part.
Package: libglib2.0-dev
Version: 2.66.6-1
Severity: normal
I just did an "apt-get build-dep linux" and noticed that both old
(pcre3) as new (pcre2) PCRE libs got installed.
Quering aptitude as to why, pointed both towards libglib2.0-dev.
That seems silly/weird to me, hence this bug report.
$
Control: found -1 5.10.12-1
Control: retitle -1 "linux-image-5.10.x: alsa audio output problems on RPi
since 5.10 kernel"
On zaterdag 23 januari 2021 20:16:45 CET you wrote:
> Version: 5.10.9-1
>
> Just played various tracks with this (new) kernel and they all play fine :)
> Don't know what the
Control: retitle -1 linux-image-5.10.x: alsa audio output problems on RPi since
5.10 kernel
signature.asc
Description: This is a digitally signed message part.
Control: retitle -1 linux-image-5.10.0-3-armmp: odroid u3 with Icom IC-7300
sound card (PCM2901) no output sound device
On dinsdag 9 februari 2021 22:04:50 CET Rusan Ioan wrote:
> Correction, sound card is By PCM2901 not PCM3901
Updating title accordingly.
signature.asc
Description: This is a
Control: tag -1 patch
Control: forwarded -1
https://salsa.debian.org/installer-team/libdebian-installer/-/merge_requests/2
signature.asc
Description: This is a digitally signed message part.
Control: found -1 20210315-2
Control: tags -1 moreinfo
Control: tag -1 affects kmail
The problem is caused by an incorrect modification of
https://salsa.debian.org/qt-kde-team/kde/messagelib/-/commits/master/debian/patches/series
Instead of adding (twice) a new/extra patch, it replaced the series.
Kind of like using '>' while you meant using '>>'.
Package: libkf5messagelist5abi1
Version: 4:20.08.3-3
Severity: important
Since upgrading of libkf5messagelist5abi1 KMail fails to load with the
following error message (I actually load it via Kontact):
"Cannot load part for Mail.
Cannot load library
Control: found -1 4.19.171-2
Control: fixed -1 4.19.181-1
Control: retitle -1 4.19.0-14-amd64: USB keyboard no longer reliably works,
requires restart
Package: subtitlecomposer
Version: 0.7.0-2
Severity: minor
Opening (22) srt files in subtitlecomposer caused the ~/.xsession-errors
file to grow from <1MB to 67MB.
Earlier (today) while trying to investigate an unrelated issue, I found
out that my ~/.xsession-errors file had grown to 950MB in
On dinsdag 9 maart 2021 15:17:01 CET Jan Huijsmans wrote:
> Updating from linux-image-5.9.0-4-arm64 to linux-image-5.10.0-3/4-arm64
> resulted in a non-booting system due to missing/incorrect USB support
> for the RPi4 8GB. (system has / on USB SSD)
>
> Only method to get the system booting again
Control: fixed -1 4.19.171-2
On zaterdag 20 maart 2021 19:10:27 CET pham...@bluewin.ch wrote:
> Bug solved with kernel 4.19.0-14-amd64
Marking as fixed with the proper version.
signature.asc
Description: This is a digitally signed message part.
Control: found -1 4.19.67-2
signature.asc
Description: This is a digitally signed message part.
On dinsdag 9 maart 2021 10:31:33 CET maximilian attems wrote:
> > I've received my new laptop with a Ryzen R7 5800U ...
> > The relevant files are amdgpu/green_sardine_*
>
> right, they only got pushed upstream in linux-firmware git on 11/2/2021
> after the latest 20210208 release, hence
On dinsdag 9 maart 2021 03:55:15 CET Ryutaroh Matsumoto wrote:
> bluez-firmware 1.2-4
>
> This seems fixed at
> https://github.com/RPi-Distro/firmware-nonfree/issues/8
The problem is that that repo is not upstream as far as the bluez-firmware
package is concerned.
The fix is included in
On dinsdag 2 maart 2021 10:24:41 CET you wrote:
> I have a 'server' with no keyboard or monitor attached. I want to
> boot into a 5.9 kernel instead of a 5.10 kernel to see whether there's a
> NFS problem with 5.10.
> But regardless what I specify as GRUB_DEFAULT in /etc/default/grub, it
> always
Package: grub-pc
Version: 2.04-15
Followup-For: Bug #827956
I have a 'server' with no keyboard or monitor attached. I want to
boot into a 5.9 kernel instead of a 5.10 kernel to see whether there's a
NFS problem with 5.10.
But regardless what I specify as GRUB_DEFAULT in /etc/default/grub, it
Package: libswresample3
Version: 7:4.3.2-0+deb11u1
Severity: minor
The long description has this line (part):
"This library provides performs highly optimized audio resampling..."
I guess it should be either 'provides' or 'performs', but both seems to
me to be a grammar error.
-- System
Control: fixed -1 1.14.0-1
On zondag 7 maart 2021 20:17:39 CET Adam Borowski wrote:
> > This patch is included in the version of f2fs-tools that's currently in
> > testing and unstable (and stable backports).
> > Can you confirm the issue is resolved?
>
> Aye, fsck no longer segfaults. Thanks!
On Wed, 15 Apr 2020 11:28:46 +0800 Chao Yu wrote:
> On 2020/4/10 7:32, Adam Borowski wrote:
> > I still get a segfault:
>
> Oops..
>
> > Program received signal SIGSEGV, Segmentation fault.
> > ...
>
> Fixed with
>
> [PATCH] fsck.f2fs: fix to avoid overflow during print_inode_info()
This
On Tue, 02 May 2017 07:52:47 +0200 Jerome Kieffer
wrote:
> Package: f2fs-tools
> Version: 1.7.0-1.1~bpo8+1
>
> I formated a complete SSD (Samsung 940evo, 250GB) interfaced in USB3 with
> F2FS on a debian stretch computer.
> 76GB of data were copied to it (mainly images and videos)
>
> After 4
On woensdag 7 april 2021 18:48:07 CEST Ernst Bammer wrote:
> upstream has lots of device tree overlays
FYI: technically, the RPF kernel is consider downstream
> As a side note, I manually downloaded all the overlays and put them into
> /boot/firmware/overlays, and then tried to enable them via
>
Package: iw
Version: 5.9-3
Severity: wishlist
X-Debbugs-Cc: debian-ker...@lists.debian.org
Earlier I filed bug #972994 to remove the Recommends on crda, which was
then fixed, thanks.
Today I got an update of network-manager which fixed bug #973241 for
which the request and fix was similar to
Control: notfound -1 5.8.14-1
Control: found -1 5.10.28-1
signature.asc
Description: This is a digitally signed message part.
Control: severity -1 grave
Control: notforwarded -1
I did not get any response to my bug report which I tagged with 'security', so
I'm upping the severity and believe the Debian documentation justifies it.
https://www.debian.org/Bugs/Developer#severities says:
"Most security bugs should also be
On woensdag 21 april 2021 11:11:43 CEST Holger Levsen wrote:
> whats the diff between /etc/default/raspi-firmware
> and /etc/default/raspi-extra-cmdline ?
The latter is similar to /boot/[firmware/]cmdline.txt on RPi systems which in
turn gets added to the kernel command line (/proc/cmdline).
I'm
Control: found -1 1:3.11.1-5
On Mon, 07 Jun 2004 04:46:15 -0500 Christopher Cashell wrote:
> I'd like to request that the dependency on libmysqlclient10 be changed
> to suggests or recommends. My experience is that most (all?) of the
> mailutils applications/tools can be used without MySQL (or
On Sat, 14 Nov 2020 23:14:12 +0100 Ulrike Uhlig wrote:
> I did not forget about this, but I'm waiting for 2.3 to be released, as
> there has been some huge refactoring which concerns the packaging of
> Onionshare, see https://github.com/micahflee/onionshare/pull/1208.
Version 2.3 has been
!= parted 100MiB, by creating a 101M image and then it did succeed.
Cheers,
Diederik
-- Forwarded Message --
Subject: Fwd: Inconsistent behavior creating partitions with 'Xmib' and 'X%'
(off-by-1 error?)
Date: zondag 22 augustus 2021, 20:39:40 CEST
From: Diederik de Haas
To: 21
Package: cpio
Version: 2.13+dfsg-6
Severity: grave
Tags: upstream
Justification: renders package unusable
Forwarded: https://lists.gnu.org/archive/html/bug-cpio/2021-08/msg5.html
The fix for bug #992098 introduced a new RC error. As bug #992098 is
technically fixed (and 'done'), here's a new
On zondag 15 augustus 2021 14:33:05 CEST Salvatore Bonaccorso wrote:
> On Sun, Aug 15, 2021 at 12:03:23PM +0200, Diederik de Haas wrote:
> > I don't know the best way to go about that though. Technically speaking,
> > the reported issue is resolved. But users got another RC bug f
On vrijdag 13 augustus 2021 13:42:33 CEST Aníbal Monsalve Salazar wrote:
> > Preface attempt 1:
> > Yesterday after downgrading to -4, I did a 'fakeroot debian/rules binary-
> > indep' and that succeeded successfully.
> >
> > Attempt 1:
> > After upgrading to -5, without running 'make clean' or
Looks very much like the same issue as mentioned here:
https://lists.gnu.org/archive/html/bug-cpio/2021-08/msg5.html
On Debian, the new problem is tracked at https://bugs.debian.org/992192 which
is a 'continuation' of https://bugs.debian.org/992098
signature.asc
Description: This is a
Control: tag -1 patch
Someone already submitted a MR to fix this issue at
https://salsa.debian.org/lechner/mdadm/-/merge_requests/3
signature.asc
Description: This is a digitally signed message part.
Control: merge -1 992845
On dinsdag 24 augustus 2021 11:13:12 CEST you wrote:
> Someone already submitted a MR to fix this issue at
> https://salsa.debian.org/lechner/mdadm/-/merge_requests/3
That same person also filed bug #992845, so merging these.
signature.asc
Description: This is a
Package: mdadm
Version: 4.2~rc2-3
Severity: important
At the end of today's updates, I got a warning/error msg wrt mdadm:
Processing triggers for initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.10.0-8-amd64
/usr/share/mdadm/mkconf: 98: SOURCE_DATE_EPOCH: parameter not
Thank you for updating vmdb2 to 0.24!
On donderdag 26 augustus 2021 18:57:07 CEST you wrote:
> afaict the qemu-debootstrap plugin is still available and doesn't alert
> the user of its deprecation.
> And I think it should, by at least outputting/logging a warning and
> possibly switching to
On zondag 22 augustus 2021 20:53:05 CEST you wrote:
> Control: forwarded -1 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21136
>
> I tried to forward this bug to the upstream bug-par...@gnu.org ML to get
> some progress and I've 'attached' that to this bug report.
With quite a bit delay, but
Package: kleopatra
Version: 4:21.08.0-1
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: Debian Security Team
I had previously 'improved' my gnupg configuration, but that is (now)
deprecated.
So I moved my ~/.gnupg directory to a backup location to start anew.
If I
Control: found -1 5.10.28-1
On Wed, 21 Apr 2021 11:01:48 +0200 dee...@gmx.net wrote:
> It is still reproducible
Updated metadata accordingly.
The primary reason I'm responding is that this bug seems to center around 3
components: kernel, apache and samba/cifs.
Yet, it seems to me that this bug
Control: tag -1 -a11y
On zondag 29 augustus 2021 13:42:40 CEST k_f wrote:
> the accessibility tag is wrong
signature.asc
Description: This is a digitally signed message part.
On 01 Feb 2019 11:34:07 -0700 Matthew Crews wrote:
> * URL : https://github.com/qml-box2d/qml-box2dh
URL is now (or should've been): https://github.com/qml-box2d/qml-box2d (-h)
signature.asc
Description: This is a digitally signed message part.
Control: fixed -1 upstream fixed-upstream
http://git.liw.fi/vmdb2/commit/?id=2d4bc72511ba16473a8e45e86fe05fbd7e35f793
is where it is correctly implemented, so updating the metadata accordingly.
It's not yet part of an upstream release/tag though.
signature.asc
Description: This is a digitally
Control: tag -1 upstream fixed-upstream
On donderdag 19 augustus 2021 13:39:08 CEST Debian Bug Tracking System wrote:
> Processing control commands:
> > fixed -1 upstream fixed-upstream
>
> Unknown command or malformed arguments to command.
signature.asc
Description: This is a digitally
Control: tag -1 upstream
On Thu, 1 Oct 2020 13:37:47 -0700 Josh Triplett wrote:
> That's not quite as trivial to parse, but you could look for lines that
> match `^\(/dev/[^:]*\): partition #\([0-9]*\) added$`, and construct the
> device name as match 1 + "p" + match 2.
I guess the best way to
Control: tag -1 upstream fixed-upstream
On dinsdag 27 juli 2021 00:06:59 CEST Diederik de Haas wrote:
> "deprecate qemu-debootstrap" is the primary commit message of:
> https://salsa.debian.org/qemu-team/qemu/-/commit/9899b1723119e57354c5d8e6f68
> f15ed762bd570 And
Control: tag -1 upstream
Control: forwarded -1 https://gitlab.com/larswirzenius/vmdb2/-/issues/2
On Sun, 14 Jun 2020 12:14:37 -0500 Gunnar Wolf wrote:
> Florian La Roche dijo [Sun, Jun 14, 2020 at 02:29:50PM +0200]:
> > it would be good to add configuration possibiities to toggle a partition
> >
Hi Ryutaroh Matsumoto,
On 18 Nov 2020 12:57:40 +0900 Ryutaroh Matsumoto
wrote:
> Package: vmdb2
> Version: 0.19-1
> ...
> ii qemu-utils 1:5.1+dfsg-4+b1
Can you check whether this issue is still reproducible with version 0.22-1?
What qemu version are you using?
If it's 5.1, I'd like to
On 15 Aug 2021 20:25:59 +0200 Sebastian Ramacher wrote:
> Dear maintainer,
>
> as I intend to upload ffmpeg without libavresample-dev soon, I've
> prepared an NMU for alsa-plugins (versioned as 1.2.2-2.1) and uploaded
> it to DELAYED/7. Please feel free to tell me if I should delay it
> longer.
On zaterdag 21 augustus 2021 17:38:51 CEST Kobus van Schoor wrote:
> Enabling/disabling it however has no effect
It was worth a shot ;-)
> (it was set to "Bad" anyway).
I don't expect much from it, but you could set them all to "Bad". If that
still doesn't make a difference, then you can fully
On zaterdag 21 augustus 2021 16:42:21 CEST Kobus van Schoor wrote:
> - My battery lasts significantly longer after upgrading to bullseye
> (around 2 hours extra I would guess). I'm not sure if there is now
> extra power saving features present in the kernel which might be
> interfering with my USB
Control: retitle -1 Too aggressive energy savings on kernel 5.10 cause some
devices to malfunction
On zaterdag 21 augustus 2021 18:48:31 CEST Kobus van Schoor wrote:
> Thanks Diederik, that did the trick!
> After setting "Runtime PM for PCI Device Intel Corporation Sunrise
> Point-LP CSME HECI
Control: retitle -1 Too aggressive energy savings on kernel 5.10 cause some USB
devices to malfunction
signature.asc
Description: This is a digitally signed message part.
On vrijdag 13 augustus 2021 13:42:33 CEST Aníbal Monsalve Salazar wrote:
> The Debian bug report is at:
> https://bugs.debian.org/992098
The bug is marked as fixed in 2.13+dfsg-6 and done and thereby the block for a
transition to testing is lifted. I think it should be kept out of testing and
Source: linux
Version: 5.13.9-1~exp2
Severity: wishlist
Currently there are some LED triggers builtin and some as modules:
$ grep 'CONFIG_LEDS_TRIGGER' /boot/config-5.13.0-trunk-arm64
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_ONESHOT=m
CONFIG_LEDS_TRIGGER_DISK=y
On Thu, 19 Aug 2021 20:40:19 +0200 Paul Gevers wrote:
> With a recent upload of cpio the autopkgtest of perl fails in testing
> when that autopkgtest is run with the binary packages of cpio from
> unstable. It passes when run with only packages from testing.
Maybe it's the same bug as
Package: kmail
Version: 4:21.08.0-2
Severity: normal
Recently I received a signed email from Debian Developer joostvb@d.o.
I imported his public key to my keyring as follows:
gpg --keyserver keyring.debian.org --recv-keys
0xB8FAC2E250475B8CE940A91957930DAB0B86B067
When selecting that mail,
On donderdag 2 september 2021 23:15:47 CEST Diederik de Haas wrote:
> KMail reports (after I signed it)
The signing part is irrelevant for reproducing the bug.
I experienced the exact same problem before I signed it.
signature.asc
Description: This is a digitally signed message part.
On dinsdag 7 september 2021 14:58:59 CEST Elena ``of Valhalla'' Grandi wrote:
> On 2021-09-06 at 22:58:54 +0200, Diederik de Haas wrote:
> > I wanted to print the Debian Social Contract, which turned out to be WAY
> > more difficult then I expected and then it should be.
> >
On donderdag 9 september 2021 05:56:17 CEST Paul Wise wrote:
> On Wed, Sep 8, 2021 at 1:11 PM Diederik de Haas wrote:
> > But then the question becomes: what is the authoritative version?
>
> The other copies of it (in doc-debian and the doc directory of the
> Debian apt archi
Hoi,
On zondag 12 september 2021 19:57:17 CEST Sandro Knauß wrote:
> I'm quite sure, that this is not the issue of Kmail, as Kmail is using the
> GPGME to talk to gpg. So it will be an issue of libqgpgme7.
Ok. I noticed the issue in KMail, so I reported it against that package.
Feel free to
Control: tag -1 upstream fixed-upstream
On 11 Dec 2018 11:08:15 -0500 Scott Kitterman wrote:
> forwarded 806500 https://bugs.quassel-irc.org/issues/1505
According to that upstream bug, the issue has been fixed.
I did take a look at https://github.com/quassel/quassel/commits/master but
there
Control: found -1 5.14.3-1~exp1
Control: tag -1 patch
On 15 Aug 2021 13:06:48 +0200 Diederik de Haas wrote:
> Most are in arch arm*, but also in arc/powerpc/microblaze/mips.
At https://salsa.debian.org/kernel-team/linux/-/merge_requests/390 I submitted
a MR which makes this trigger buil
Hi,
On maandag 8 februari 2021 19:01:21 CEST Simon McVittie wrote:
> Control: tags -1 + upstream wontfix
> Control: forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/issues/1085
It looks like that is/was an excellent forward :-)
> If this is ever solved, it will have to be solved upstream.
On zondag 12 september 2021 19:57:17 CEST Sandro Knauß wrote:
> But first make sue, that you are really have an valid bug. Please verify the
> signature in a konsole via gpg --verify. I expect, that it will fail with
> the same error.
Thanks for your assistance. I've save the signature as
Package: doc-debian
Version: 6.5
Followup-For: Bug #273323
X-Debbugs-Cc: debian-proj...@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I wanted to print the Debian Social Contract, which turned out to be WAY
more difficult then I expected and then it should be.
So I went to
On woensdag 8 september 2021 09:22:11 CEST Gard Spreemann wrote:
> there should perhaps be an authoritative version of the text,
> from which PDF, whatever-printable, HTML, etc. can be generated
I think that's a good idea.
But then the question becomes: what is the authoritative version?
I get
On donderdag 16 september 2021 12:53:16 CEST Diederik de Haas wrote:
> Control: retitle -1 GPGMe does not take additional keyring into account to
> find keys.
I retitled the bug as Sandro suggested, but I'm having second thoughts as to
whether it's an (entirely) accurate description.
Adding pkg-xen-de...@lists.alioth.debian.org into the loop.
Chuck Zmudzinski replied to the bug and later replied to his own reply.
To give full context, I've added the original reply in full and Chuck's reply
to that (as it only quoted part of the context there).
On zondag 19 september 2021
Package: pulseaudio
Version: 15.0+dfsg1-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I have several customizations in /etc/pulse/system.pa and the latest
upgrade of pulseaudio therefor prompted me what to do with it.
The new last lines of /etc/pulse/system.pa are as
Package: fwupd-amd64-signed
Version: 1.5.7+4
Followup-For: Bug #973715
X-Debbugs-Cc: 93...@debian.org mario.limoncie...@dell.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
According to 'buildd' version 1.5.7-4+b1 has been built 28 days ago,
but because this issue is still present, fwupd
Control: reassign -1 libqgpgme7 1.16.0-1
Control: retitle -1 GPGMe does not take additional keyring into account to find
keys.
Control: affects -1 kmail
On woensdag 15 september 2021 10:56:59 CEST Sandro Knauß wrote:
> > Thanks for your assistance. I've save the signature as 'signature.asc' and
On dinsdag 7 september 2021 11:26:15 CEST Gard Spreemann wrote:
> Diederik de Haas writes:
> > I wanted to print the Debian Social Contract, which turned out to be WAY
> > more difficult then I expected and then it should be.
> > ...
>
> Are any of these helpful? I'm
On dinsdag 7 september 2021 11:32:28 CEST Peter Green wrote:
> > Version: 4:21.08.0-1
>
> You filed this against the version in sid?
I run Sid as my daily driver, so yes. That's what I (almost?) always do.
> have you investigated whether earlier versions are also affected?
No, I did not.
On Mon, 01 Mar 2021 14:08:41 +0100 Diederik de Haas
wrote:
> The mentioned patch was first included in Debian's 1.10.0-1; f2fs-tools is at
> version 1.14.0-2 in testing/unstable, while Stable has version 1.11.0-1.1.
>
> Can you confirm this issue is resolved?
I saw the above re
On Sat, 21 Jul 2018 16:24:29 -0400 "Theodore Y. Ts'o" wrote:
> On Fri, Jul 20, 2018 at 09:35:53PM +0200, Alexander Dahl wrote:
> > I can confirm that behaviour for Raspbian GNU/Linux 9 (stretch), quote
> > from syslog:
> >
> > Jul 20 17:17:04 darcy systemd-fsck[96]: fsck.f2fs: invalid option --
601 - 700 of 1660 matches
Mail list logo
