Package: wireplumber
Version: 0.4.14-3
Severity: grave
Hi!
In version 0.4.14-3, you added a hard dependency on a specific session
model of dbus, rather than the virtual package defined by the Policy
(dbus-session-bus). This makes it non-installable on any box where a
dependency of that package
On Wed, 14 Jun 2023 16:00:12 +0900 Hideki Yamane wrote:
[...]
> As I wrote in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036388,
> please describe your environment and reproducible way step by step.
Hello,
I am another user of Sylpheed (in Debian).
Personally, I can reproduce the
Package: golang-1.21-go
Version: 1.21~rc2-2
Severity: grave
Tags: security
Go 1.21 provides the `GOTOOLCHAIN` environment variable and associated
functionality[0]. As part of this code, if go.mod indicates that a
newer version of Go is required than the current toolchain supports, it
proceeds by
Processing commands for cont...@bugs.debian.org:
> # r-cran-pammtools took "ownership"
> reassign 1039510 src:r-cran-pammtools 0.5.8-1
Bug #1039510 {Done: Andreas Tille } [src:mvtnorm,
src:r-cran-pammtools] mvtnorm breaks r-cran-pammtools autopkgtest: missing
Breaks and/or versioned (test)
Package: multipath-tools
Version: 0.9.4-3+deb12u1
Severity: critical
Tags: upstream
Justification: breaks unrelated software
X-Debbugs-Cc:t...@security.debian.org
Hallo Chris,
if the device has _one_ partition Version: 0.9.4-3+deb12u1 solve the
problem, but if it has multiple partitions the
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:kjs
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Source: qt6-virtualkeyboard
Version: 6.4.2+dfsg-2
Severity: serious
Tags: ftbfs
qt6-virtualkeyboard fails to build from source in unstable when passing
DEB_BUILD_OPTIONS=parallel=1. A build ends as follows:
| [110/301] cd /<>/obj-x86_64-linux-gnu/src/components &&
/usr/bin/cmake -E
Processing commands for cont...@bugs.debian.org:
> reassign 1037467 src:ruby-gollum-lib
Bug #1037467 [ruby-gollum-lib] ruby-gollum-lib not compatible with ruby-rouge
4.1
Bug reassigned from package 'ruby-gollum-lib' to 'src:ruby-gollum-lib'.
No longer marked as found in versions
Your message dated Thu, 06 Jul 2023 17:19:34 +
with message-id
and subject line Bug#1039920: fixed in ruby-browser 5.3.1-3
has caused the Debian Bug report #1039920,
regarding ruby-browser: autopkgtest regression: No such file or directory @
rb_sysopen -
Processing commands for cont...@bugs.debian.org:
> forcemerge 1040405 1037467
Bug #1040405 [src:ruby-gollum-lib] ruby-gollum-lib: incompatible with newer
ruby-rouge
Unable to merge bugs because:
package of #1037467 is 'ruby-gollum-lib' not 'src:ruby-gollum-lib'
Failed to forcibly merge 1040405:
Processing commands for cont...@bugs.debian.org:
> tags 1026433 + sid trixie
Bug #1026433 [src:mercurial-buildpackage] RM: mercurial-buildpackage -- RoQA;
no users left
Added tag(s) trixie and sid.
> tags 1038641 + sid trixie
Bug #1038641 [src:ganv] RM: ganv -- RoQA; depends on gtk2
Added tag(s)
Processing control commands:
> severity 1035382 grave
Bug #1035382 [debian-live] Bookworm amd64 live install ISO RC1 and RC2 install
pointless raspi-firmware package
Ignoring request to change severity of Bug 1035382 to the same value.
--
1035382:
Control: severity 1035382 grave
On Thu, Jul 06, 2023 at 06:29:49PM +0200, Magnus Wallin wrote:
>
>Hi Magnus, and thanks for the heads-up
>
>[ . . . ]
>
>Just because the raspi-firmware package is included on the d-i
>installation media, it shouldn't necessarily be installed on an
Processing control commands:
> severity 1035382 grave
Bug #1035382 [debian-live] Bookworm amd64 live install ISO RC1 and RC2 install
pointless raspi-firmware package
Severity set to 'grave' from 'normal'
--
1032071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032071
1035382:
Your message dated Thu, 06 Jul 2023 16:04:21 +
with message-id
and subject line Bug#1040438: fixed in libmail-dkim-perl 1.20230212-2
has caused the Debian Bug report #1040438,
regarding libmail-dkim-perl: missing dependency on
libgetopt-long-descriptive-perl
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> found 1040438 1.20220520-1
Bug #1040438 [libmail-dkim-perl] libmail-dkim-perl: missing dependency on
libgetopt-long-descriptive-perl
Marked as found in versions libmail-dkim-perl/1.20220520-1.
> thanks
Stopping processing here.
Please contact
I'd be very interested in knowing what this self-conflict is supposed to
achieve.
It is common upstream for there to be multiple semver-incompatible versions
of each rust crate in use at a given time. Incompatibilities can range from
minor corner cases that are easily patched away to complete
Your message dated Thu, 6 Jul 2023 17:29:33 +0200
with message-id
and subject line Re: schleuder: incompatible with newer ruby-mail
has caused the Debian Bug report #1040451,
regarding schleuder: incompatible with newer ruby-mail
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 06 Jul 2023 15:19:57 +
with message-id
and subject line Bug#1039510: fixed in r-cran-pammtools 0.5.91-3
has caused the Debian Bug report #1039510,
regarding mvtnorm breaks r-cran-pammtools autopkgtest: missing Breaks and/or
versioned (test) Depends?
to be marked as
[Petter Reinholdtsen]
It is unclear to me why you believe this should work. Can you tell me
where you got the idea to run the shared library like this?
1. /usr/bin/ssr-glinject from simplescreenrecorder package sets
LD_PRELOAD=/usr/$LIB/simplescreenrecorder/libssr-glinject.so
which
Your message dated Thu, 06 Jul 2023 14:42:51 +
with message-id
and subject line Bug#1039649: fixed in r-cran-ggridges 0.5.4-2
has caused the Debian Bug report #1039649,
regarding r-cran-ggridges: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that
Your message dated Thu, 06 Jul 2023 14:42:59 +
with message-id
and subject line Bug#1039652: fixed in r-cran-gridtext 0.1.5-2
has caused the Debian Bug report #1039652,
regarding r-cran-gridtext: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that
Your message dated Thu, 06 Jul 2023 14:42:36 +
with message-id
and subject line Bug#1039647: fixed in r-cran-ggplot2 3.4.2+dfsg-2
has caused the Debian Bug report #1039647,
regarding r-cran-ggplot2: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim
Your message dated Thu, 06 Jul 2023 14:42:43 +
with message-id
and subject line Bug#1039648: fixed in r-cran-ggrepel 0.9.3-2
has caused the Debian Bug report #1039648,
regarding r-cran-ggrepel: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the
Your message dated Thu, 06 Jul 2023 14:42:23 +
with message-id
and subject line Bug#1039646: fixed in r-cran-ggally 2.1.2-2
has caused the Debian Bug report #1039646,
regarding r-cran-ggally: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the
Hi,
Quoting Helmut Grohne (2023-07-06 13:27:19)
> librust-syn-1-dev has (among other things) the following metadata:
>
> Provides: librust-syn-1.0.109-dev
> Breaks: librust-syn-1.0.109-dev
> Multi-Arch: same
this looks very bad.
> If apt and dose were refusing this situation this were a normal
Your message dated Thu, 6 Jul 2023 15:18:52 +0200
with message-id
<5vjrplofrou22bgl4qs52mdxaksebrs26q6lgrsb2lqc56a4ss@dybruzgdwdxg>
and subject line 1040478: devices from extern FC-Raid only map if the have no
partitions
has caused the Debian Bug report #1040478,
regarding multipath-tools:
Your message dated Thu, 06 Jul 2023 13:20:03 +
with message-id
and subject line Bug#1039655: fixed in r-cran-knitr 1.43+dfsg-2
has caused the Debian Bug report #1039655,
regarding r-cran-knitr: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the
Your message dated Thu, 6 Jul 2023 15:18:52 +0200
with message-id
<5vjrplofrou22bgl4qs52mdxaksebrs26q6lgrsb2lqc56a4ss@dybruzgdwdxg>
and subject line 1040478: devices from extern FC-Raid only map if the have no
partitions
has caused the Debian Bug report #1040478,
regarding multipath-tools:
Your message dated Thu, 06 Jul 2023 13:20:19 +
with message-id
and subject line Bug#1039657: fixed in r-cran-pammtools 0.5.91-2
has caused the Debian Bug report #1039657,
regarding r-cran-pammtools: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim
Your message dated Thu, 06 Jul 2023 13:20:11 +
with message-id
and subject line Bug#1039656: fixed in r-cran-ncdfgeom 1.1.5+dfsg-2
has caused the Debian Bug report #1039656,
regarding r-cran-ncdfgeom: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim
Your message dated Thu, 06 Jul 2023 13:19:09 +
with message-id
and subject line Bug#1039481: fixed in gupnp-igd 1.6.0-2
has caused the Debian Bug report #1039481,
regarding libgupnp-igd-doc: missing Breaks+Replaces: libgupnp-igd-1.0-doc (<<
1.6)
to be marked as done.
This means that you
On 2023-07-05 18:58:13 +0200, Johannes Christ wrote:
> Is there another way to reproduce this issue?
I'm wondering whether there is a race condition in the test:
# use at command to schedule a job.
echo "echo `date` > ${WORKDIR}/${TMPFILE}" | at now + 1 minute
So the file is expected to be
Processing commands for cont...@bugs.debian.org:
> forcemerge 1040478 1040479
Bug #1040478 [multipath-tools] multipath-tools: devices from extern FC-Raid
only map if the have no partitions
Bug #1040479 [multipath-tools] multipath-tools: devices from extern FC-Raid
only map if the have no
Your message dated Thu, 06 Jul 2023 13:07:22 +
with message-id
and subject line Bug#1039659: fixed in r-cran-pkgdown 2.0.7-2
has caused the Debian Bug report #1039659,
regarding r-cran-pkgdown: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the
Your message dated Thu, 06 Jul 2023 13:07:46 +
with message-id
and subject line Bug#1039688: fixed in r-cran-projpred 2.6.0+dfsg-2
has caused the Debian Bug report #1039688,
regarding r-cran-projpred: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim
Your message dated Thu, 06 Jul 2023 13:07:38 +
with message-id
and subject line Bug#1039660: fixed in r-cran-proc 1.18.2-2
has caused the Debian Bug report #1039660,
regarding r-cran-proc: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the
Your message dated Thu, 06 Jul 2023 13:07:30 +
with message-id
and subject line Bug#1039675: fixed in r-cran-posterior 1.4.1+dfsg-2
has caused the Debian Bug report #1039675,
regarding r-cran-posterior: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim
Your message dated Thu, 06 Jul 2023 13:07:13 +
with message-id
and subject line Bug#1039658: fixed in r-cran-patchwork 1.1.2-2
has caused the Debian Bug report #1039658,
regarding r-cran-patchwork: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that
Package: raspi-firmware
Severity: serious
Justification: 6
X-Debbugs-Cc: okgomdjgbm...@gmail.com
Dear Maintainer,
I tried to upgrade the kernel today( bookworm amd64), and it failed because of
raspi-firmware scripts. I had to rm manually files and purge raspi-firmware so
that the kernel can
Processing commands for cont...@bugs.debian.org:
> severity 1038139 normal
Bug #1038139 [debci] debci-worker: Process leaks authentication data via
amqp-tools
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1038139:
Processing commands for cont...@bugs.debian.org:
> fixed 1039664 r-cran-tikzdevice/0.12.4-3
Bug #1039664 {Done: Andreas Tille } [src:r-cran-tikzdevice]
r-cran-tikzdevice: autopkgtest failure with r-base (4.3.1-1)
Marked as fixed in versions r-cran-tikzdevice/0.12.4-3.
> fixed 1039661
Your message dated Thu, 06 Jul 2023 12:20:03 +
with message-id
and subject line Bug#1039663: fixed in r-cran-stars 0.6-1-1
has caused the Debian Bug report #1039663,
regarding r-cran-stars: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the
Package: multipath-tools
Version:0.9.4-3
Severity: critical
Tags: upstream
Justification: breaks unrelated software
X-Debbugs-Cc:t...@security.debian.org
Ohh sorry, the version failed is stable0.9.4 the version below is the working
on from oldstable.
Am 06.07.23 um 13:47 schrieb Andreas
Package: multipath-tools
Version: 0.8.5-2+deb11u1
Severity: critical
Tags: upstream
Justification: breaks unrelated software
X-Debbugs-Cc: t...@security.debian.org
-- Package-specific info:
Contents of /etc/multipath.conf:
defaults {
polling_interval 10
max_fds 8192
}
[B]
> * What led up to the situation?
> Trying to "Record OpenGL" in simplescreenrecorder.
> * What exactly did you do (or not do) that was effective (or ineffective)?
> LD_PRELOAD=/usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so
> /usr/bin/true
It is unclear to me why you
Package: librust-syn-1-dev
Version: 1.0.109-2
Severity: serious
Justification: fails to (co)install
Control: affects -1 + src:rust-fd-find
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
X-Debbugs-Cc: de...@lists.debian.org
librust-syn-1-dev has (among other things) the following metadata:
Processing control commands:
> affects -1 + src:rust-fd-find
Bug #1040477 [librust-syn-1-dev] librust-syn-1-dev fails to coinstall
Added indication that 1040477 affects src:rust-fd-find
--
1040477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040477
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> reassign 1040199 xtrx-dkms
Bug #1040199 [src:linux] linux-image-6.3.0-1-amd64: kernel panic during boot
Bug reassigned from package 'src:linux' to 'xtrx-dkms'.
No longer marked as found in versions linux/6.3.7-1.
Ignoring request to alter fixed
Source: python-click
Version: 8.1.3-2
Severity: serious
Hello, after new pytest went in sid (or some other python updates), the package
started FTBFS
I: Logging to /home/pbuilder/sid_result/python-click_8.1.3-2_amd64.build
D: cmdline: build --distribution sid --buildresult
On Wed, 5 Jul 2023 16:44:31 +0200 Gianfranco Costamagna
wrote:
> Can you please have a look?
We no longer need ruby-gollum-lib for gitaly, so requested removal of
ruby-gollum-lib in #1040461.
Your message dated Thu, 06 Jul 2023 09:57:19 +
with message-id
and subject line Bug#1039677: fixed in r-cran-sftime 0.2-0-6
has caused the Debian Bug report #1039677,
regarding r-cran-sftime: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the
Your message dated Thu, 06 Jul 2023 09:23:05 +
with message-id
and subject line Bug#1039662: fixed in r-cran-sjmisc 2.8.9-2
has caused the Debian Bug report #1039662,
regarding r-cran-sjmisc: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the
Your message dated Thu, 06 Jul 2023 09:05:28 +
with message-id
and subject line Bug#1039671: fixed in r-cran-thematic 0.1.2.1-4
has caused the Debian Bug report #1039671,
regarding r-cran-thematic: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that
Your message dated Thu, 06 Jul 2023 09:05:53 +
with message-id
and subject line Bug#1039670: fixed in r-cran-unitizer 1.4.19-2
has caused the Debian Bug report #1039670,
regarding r-cran-unitizer: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that
Your message dated Thu, 06 Jul 2023 09:05:44 +
with message-id
and subject line Bug#1039665: fixed in r-cran-treespace 1.1.4.2+dfsg-2
has caused the Debian Bug report #1039665,
regarding r-cran-treespace: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you
sudo apt build-dep simplescreenrecorder
sudo apt install git mesa-utils simplescreenrecorder
git clone --depth=1https://github.com/MaartenBaert/ssr
cd ssr
sudo --reset-timestamp
ENABLE_32BIT_GLINJECT=FALSE ./simple-build-and-install
# press Ctrl+C when it asks password
On Wed, 05 Jul 2023 at 22:44:40 +0200, Bastian Venthur wrote:
> Start-Date: 2023-07-03 09:06:13
Unfortunately this upgrade was sufficiently large that it's hard to
spot which package might have triggered this. Nothing jumps out at me
as a particularly likely trigger. Maaaybe glibc, or the
On Thu, 6 Jul 2023 at 09:42, Bastian Blank wrote:
>
> 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
Your message dated Thu, 06 Jul 2023 08:41:53 +
with message-id
and subject line Bug#1039674: fixed in r-cran-uwot 0.1.16-2
has caused the Debian Bug report #1039674,
regarding r-cran-uwot: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the
Your message dated Thu, 06 Jul 2023 08:42:32 +
with message-id
and subject line Bug#1039667: fixed in r-cran-xopen 1.0.0+dfsg-1
has caused the Debian Bug report #1039667,
regarding r-cran-xopen: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that
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.
Processing control commands:
> affects -1 + src:ruby-gollum-lib
Bug #1040461 [ftp.debian.org] RM: ruby-gollum-lib -- ROM; incompatible with
newer ruby-rouge
Added indication that 1040461 affects src:ruby-gollum-lib
> block 1040405 by -1
Bug #1040405 [src:ruby-gollum-lib] ruby-gollum-lib:
Andreas Tille wrote:
Done in 0.12.4-3
This does not mark the bug as fixed in that version.
Use a version header at the top of your email:
Version: 0.12.4-3
Or use the control commands:
https://www.debian.org/Bugs/server-control#fixed
Kind Regards,
Bas
--
GPG Key ID:
Your message dated Thu, 06 Jul 2023 08:39:41 +
with message-id
and subject line Bug#1039881: fixed in r-cran-rsample 1.1.1+dfsg-2
has caused the Debian Bug report #1039881,
regarding r-cran-rsample: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim
Your message dated Thu, 06 Jul 2023 08:39:01 +
with message-id
and subject line Bug#1039880: fixed in r-cran-plotly 4.10.2+dfsg-2
has caused the Debian Bug report #1039880,
regarding r-cran-plotly: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that
Your message dated Thu, 06 Jul 2023 08:38:40 +
with message-id
and subject line Bug#1039676: fixed in r-cran-forecast 8.21-2
has caused the Debian Bug report #1039676,
regarding r-cran-forecast: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that
On Thu, 6 Jul 2023 at 09:14, Bastian Blank wrote:
>
> 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
Your message dated Thu, 6 Jul 2023 10:32:36 +0200
with message-id
and subject line Re: Bug#1039661: r-cran-ragg: autopkgtest failure with r-base
(4.3.1-1)
has caused the Debian Bug report #1039661,
regarding r-cran-ragg: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> forwarded 1040256 https://github.com/jcelaya/hdrmerge/pull/217
Bug #1040256 [src:hdrmerge] hdrmerge FTBFS with libraw 0.21.1
Set Bug forwarded-to-address to 'https://github.com/jcelaya/hdrmerge/pull/217'.
> tags 1040256 + upstream fixed-upstream
Your message dated Thu, 6 Jul 2023 10:24:51 +0200
with message-id
and subject line Re: Bug#1039672: r-cran-svglite: autopkgtest failure with
r-base (4.3.1-1)
has caused the Debian Bug report #1039672,
regarding r-cran-svglite: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This
Your message dated Thu, 6 Jul 2023 10:23:56 +0200
with message-id
and subject line Re: Bug#1039664: r-cran-tikzdevice: autopkgtest failure with
r-base (4.3.1-1)
has caused the Debian Bug report #1039664,
regarding r-cran-tikzdevice: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
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
--
This is now fixed :)
Den tis 4 juli 2023 kl 21:27 skrev Eli Schwartz :
>
> This bug seems to have been caused by
> https://salsa.debian.org/cpython-team/python3-defaults/-/commit/8e243207fee371a7335674fc77db63044b62cb29
>
> It migrated from imp to importlib, but importlib doesn't imply
>
On Sunday, May 14, 2023 3:20:39 PM CEST Andreas Metzler wrote:
> Something like attached patch.
https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/1425
/Sune
--
I didn’t stop pretending when I became an adult, it’s just that when I was a
kid I was pretending that I fit into the
Your message dated Thu, 06 Jul 2023 07:50:22 +
with message-id
and subject line Bug#1039882: fixed in r-cran-sf 1.0-13+dfsg-2
has caused the Debian Bug report #1039882,
regarding r-cran-sf: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the
Hi,
On 06/07/2023 06:33, Vasyl Gello wrote:
Yes I definitely see the bug. However, Kodi extensively uses pcrecpp and
the only replacement I see for pcre2 is jpcre2 [1]
There is an ITP bug about it since 2017 but no package.
Matthew, from your experience, is jpcre2 the only C++ wrapper for
Your message dated Thu, 06 Jul 2023 07:34:39 +
with message-id
and subject line Bug#1039884: fixed in r-cran-tibble 3.2.1+dfsg-2
has caused the Debian Bug report #1039884,
regarding r-cran-tibble: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that
Your message dated Thu, 06 Jul 2023 07:19:00 +
with message-id
and subject line Bug#1039886: fixed in r-cran-truncnorm 1.0-9-2
has caused the Debian Bug report #1039886,
regarding r-cran-truncnorm: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that
Your message dated Thu, 06 Jul 2023 07:18:54 +
with message-id
and subject line Bug#1039885: fixed in r-cran-tidytext 0.4.1-2
has caused the Debian Bug report #1039885,
regarding r-cran-tidytext: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that
80 matches
Mail list logo
