On Mon, 14 Jun 2021 at 00:03, Axel Beckert wrote:
> So the Breaks and Replaces headers (c.f. #982059) should likely be
> against "<< 4.9.3-4", not just against "<< 4.9.1-1".
>
It looks like both the psmisc and procps manpages came back from the dead.
They were removed in manpages-de 4.9.1-1 and
Hi smcv,
On Sun, Jun 13, 2021 at 6:43 PM Simon McVittie wrote:
>
> On Sun, 13 Jun 2021 at 22:18:42 +0200, Jochen Sprickerhof wrote:
> > * Olek Wojnar [2021-06-13 15:15]:
>
> some API designs make it
> really hard to keep backwards compatibility, because a lot of internal
> decisions get
Your message dated Mon, 14 Jun 2021 00:50:14 +
with message-id
and subject line Bug#946447: fixed in thefuck 3.29-0.2
has caused the Debian Bug report #946447,
regarding thefuck: does not start without python3-distutils installed
to be marked as done.
This means that you claim that the
(This is all for post-bullseye: the NMU seems like a good minimal change
to resolve this for bullseye.)
On Sun, 13 Jun 2021 at 22:18:42 +0200, Jochen Sprickerhof wrote:
> * Olek Wojnar [2021-06-13 15:15]:
> > As Simon's sponsor, I'd like to point out that his packaging was rather
> > reasonable
Processing commands for cont...@bugs.debian.org:
> tags 987936 + fixed
Bug #987936 {Done: Andrej Shadura } [src:libstorj]
libstorj: fails to build from the source
Added tag(s) fixed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
987936:
Processing commands for cont...@bugs.debian.org:
> tags 914315 - sid bookworm
Bug #914315 [libwebp-dev] libwebp-dev: New versions fix disclosed heap
use-after-free
Removed tag(s) bookworm and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
914315:
Your message dated Sun, 13 Jun 2021 20:26:11 +
with message-id
and subject line Bug#988909: fixed in lintian-brush 0.106
has caused the Debian Bug report #988909,
regarding lintian-brush: autopkgtest failure and FTBFS
to be marked as done.
This means that you claim that the problem has been
Hi Olek,
* Olek Wojnar [2021-06-13 15:15]:
Are you also planning to file an unblock bug or would you like Simon (or
me) to take care of that?
I'm happy to take care of it.
On Sat, Jun 12, 2021 at 3:27 PM wrote:
I'm sorry for messing this up, this is my first official debian package.
Your message dated Sun, 13 Jun 2021 19:44:49 +
with message-id
and subject line Fixed in newer versions
has caused the Debian Bug report #987772,
regarding ognibuild: autopkgtest regression: debcommit() got an unexpected
keyword argument 'reporter'
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> reassign 988156 brz-loom
Bug #988156 [src:breezy, src:breezy-loom] breezy breaks breezy-loom
autopkgtest: FAILED (failures=4)
Bug reassigned from package 'src:breezy, src:breezy-loom' to 'brz-loom'.
No longer marked as found in versions
Processing commands for cont...@bugs.debian.org:
> severity 988166 normal
Bug #988166 [src:breezy, src:check-manifest] breezy breaks check-manifest
autopkgtest: brz: ERROR: No module named 'dulwich'
Severity set to 'normal' from 'serious'
> tags 988166 +upstream
Bug #988166 [src:breezy,
severity 988166 normal
tags 988166 +upstream
thanks
I've moved Dulwich from Recommends to Depends for the moment. This will
at least work around the issue.
Ideally we'd keep dulwich as a recommends, but that will require some
investigation and fixes upstream.
Hi Jochen,
First of all, thank you very much for taking the time to fix those issues!
And an extra thank you for speaking with the release team already! I always
get very nervous with significant package changes this close to a release.
Are you also planning to file an unblock bug or would you
Processing control commands:
> severity -1 serious
Bug #981997 [gudev-sharp-1.0] Conflicting monodoc-gudev-manual binary built
also by Package: gudev-sharp-3.0
Severity set to 'serious' from 'normal'
--
981997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981997
Debian Bug Tracking System
Hello,
is there any progress on this [bug]?
I've just re-read all the bug log, and I acknowledge that the issue is
not easy to deal with.
But, whatever the decision, I think that the bug should be somehow
fixed, in the poppler packages, or in the other packages depending on
the library.
Please
i tested on 4th hw
4. asus m4n78 pro, phenom ii x4 905e, md raid1, 2x samsung 1TB 860evo,
lvm: problem does not appear
as i see, not all mb/chipset/sata pcie device affected
Thanks!
Package: psmisc
Version: 23.4-2
Severity: serious
A non-english speaking friend did a dist-upgrade of a laptop from buster
+ buster-backports to bullseye and it failed at psmisc as follows
(German locale):
dpkg: Fehler beim Bearbeiten des Archivs
Your message dated Sun, 13 Jun 2021 13:34:25 +
with message-id
and subject line Bug#989790: fixed in ogdi-dfsg 4.1.0+ds-4
has caused the Debian Bug report #989790,
regarding libogdi4.1: rename plugin files to include the SOVERSION
to be marked as done.
This means that you claim that the
On 2021-06-13 14:08:21 +0200, Sebastiaan Couwenberg wrote:
> On 6/13/21 12:02 PM, Sebastian Ramacher wrote:
> > On 2021-06-13 11:53:00 +0200, Sebastiaan Couwenberg wrote:
> >> On 6/13/21 11:36 AM, Sebastian Ramacher wrote:
> >>> "If your package contains files whose names do not change with each
>
On 6/13/21 12:02 PM, Sebastian Ramacher wrote:
> On 2021-06-13 11:53:00 +0200, Sebastiaan Couwenberg wrote:
>> On 6/13/21 11:36 AM, Sebastian Ramacher wrote:
>>> "If your package contains files whose names do not change with each
>>> change in the library shared object version, you must not put
Source: dqlite
Version: 1.6.0-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=dqlite=mips64el
...
lib_buffer/init/n_pages [ ERROR ]
Error: test/unit/lib/test_buffer.c:73: assertion failed: f->buffer.page_size ==
4096 (16384 ==
On 2021-06-13 11:53:00 +0200, Sebastiaan Couwenberg wrote:
> On 6/13/21 11:36 AM, Sebastian Ramacher wrote:
> > "If your package contains files whose names do not change with each
> > change in the library shared object version, you must not put them in
> > the shared library package."
>
> The
On 6/13/21 11:36 AM, Sebastian Ramacher wrote:
> "If your package contains files whose names do not change with each
> change in the library shared object version, you must not put them in
> the shared library package."
The files should no included in libogdi4.1:
"you must not put them in the
Package: libogdi4.1
Version: 4.1.0+ds-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Justification: Debian Policy 8.2
First sentence of 8.2:
"If your package contains files whose names do not change with each
change in the library shared object version, you must not put them in
the
Your message dated Sun, 13 Jun 2021 07:33:51 +
with message-id
and subject line Bug#982552: fixed in ruby-carrierwave 1.3.2-1
has caused the Debian Bug report #982552,
regarding ruby-carrierwave: CVE-2021-21288
to be marked as done.
This means that you claim that the problem has been dealt
Processing control commands:
> block -1 by 966653
Bug #989786 [ruby-spamcheck] ruby-spamcheck: cannot use ruby-grpc package
989786 was not blocked by any bugs.
989786 was not blocking any bugs.
Added blocking bug(s) of 989786: 966653
--
989786:
Package: ruby-spamcheck
Version: 0.1.0+git20210519.2084b44-2
Severity: grave
Control: block -1 by 966653
Since the only reverse dependency of ruby-spamcheck is gitlab and
gitlab does not work with debian's ruby-grpc package (see #966653),
dependency on ruby-grpc is removed. It will be added
27 matches
Mail list logo
