On Thu, 11 Mar 2021 09:11:37 +0100 Paul Gevers wrote:
Is it possible that we get this uploaded soon? If you have the fix
ready, it would be good to have it sooner rather than later as we're in
the freeze, so it gets a bit of exposure.
I'd like to get some maintainer feedback on
Processing control commands:
> tag -1 pending
Bug #985467 [guix] guix: Risk of local privilege escalation via guix-daemon
Added tag(s) pending.
--
985467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #985467 in guix 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 fix at:
Hi,
I received an update from Leo Famulari:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=47229#25
When using a guix-daemon that does not include the fix [0] for the bug
reported here, it is still possible for rogue build scripts to escape
the build environment, even when protected
Your message dated Thu, 18 Mar 2021 23:05:48 +
with message-id
and subject line Bug#985437: fixed in texlive-extra 2020.20210202-2
has caused the Debian Bug report #985437,
regarding texlive-fonts-extra: broken font symlinks
to be marked as done.
This means that you claim that the problem
Control: tag -1 pending
Hello,
Bug #984539 in debian-security-support 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 fix at:
Hi Ivo,
On Fri, Mar 19, 2021 at 3:41 AM Ivo De Decker wrote:
> Note that this doesn't actually ensure that it doesn't fail. The 'else' case
> only happens when the if statement fails, so when the hook doesn't exist. But
> when the hook script fails for some reason, dpkg will still abort. I think
Processing control commands:
> tag -1 pending
Bug #984539 [debian-security-support] debian-security-support: dpkg hook should
never fail
Ignoring request to alter tags of bug #984539 to the same tags previously set
--
984539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984539
Debian Bug
Hi,
On Thu, Mar 18, 2021 at 08:57:17PM +, Utkarsh Gupta wrote:
> Bug #984539 in debian-security-support 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 fix at:
>
>
Your message dated Thu, 18 Mar 2021 22:03:59 +
with message-id
and subject line Bug#985436: fixed in starpu 1.3.7+dfsg-3
has caused the Debian Bug report #985436,
regarding libstarpu-dev: broken symlink:
/usr/lib/x86_64-linux-gnu/libstarpurm-1.3.so -> libstarpurm-1.3.so.1.0.1
to be marked as
Your message dated Thu, 18 Mar 2021 22:03:33 +
with message-id
and subject line Bug#985116: fixed in libgrokj2k 7.6.6-3
has caused the Debian Bug report #985116,
regarding libgrokj2k: FTBFS on i386
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Bernard,
Dennis,
> Indeed:
>
> ii libsoci-core4.0:amd64 4.0.1-5 ...
> ii libsoci-sqlite3-4.0:amd64 4.0.1-5 ...
>
> solved the problem: I now see the chat msgs history when I launch the
> app. I didn't have a chance to send a new msg yet, because it's the
> middle of the night
Processing commands for cont...@bugs.debian.org:
> tags 985436 + pending
Bug #985436 [libstarpu-dev] libstarpu-dev: broken symlink:
/usr/lib/x86_64-linux-gnu/libstarpurm-1.3.so -> libstarpurm-1.3.so.1.0.1
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need
Processing control commands:
> reassign -1 texlive-fonts-extra-links
Bug #985437 [texlive-fonts-extra] texlive-fonts-extra: broken font symlinks
Bug reassigned from package 'texlive-fonts-extra' to
'texlive-fonts-extra-links'.
No longer marked as found in versions texlive-extra/2020.20210202-1.
Control: reassign -1 texlive-fonts-extra-links
Am 18.03.2021 um 10:52 teilte Andreas Beckmann mit:
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
I didn't check whether there are missing Depends or Recommends
or the dependencies have changed
Processing commands for cont...@bugs.debian.org:
> severity 985468 normal
Bug #985468 [msmtp-mta] msmtp-mta: Please cherry-pick 7dcf from upstream
for bullseye
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
985468:
Control: tag -1 pending
Hello,
Bug #984539 in debian-security-support 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 fix at:
Processing control commands:
> tag -1 pending
Bug #984539 [debian-security-support] debian-security-support: dpkg hook should
never fail
Added tag(s) pending.
--
984539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing commands for cont...@bugs.debian.org:
> forwarded 985467 https://issues.guix.gnu.org/47229
Bug #985467 [guix] guix: Risk of local privilege escalation via guix-daemon
Set Bug forwarded-to-address to 'https://issues.guix.gnu.org/47229'.
> tags 985467 + upstream
Bug #985467 [guix] guix:
Your message dated Thu, 18 Mar 2021 20:19:14 +
with message-id
and subject line Bug#985440: fixed in pinball 0.3.20201218-2
has caused the Debian Bug report #985440,
regarding pinball-dev: depends on virtual libstdc++-dev with multiple providers
to be marked as done.
This means that you
Your message dated Thu, 18 Mar 2021 19:48:35 +
with message-id
and subject line Bug#983610: fixed in zint 2.9.1-1.1
has caused the Debian Bug report #983610,
regarding zint: CVE-2021-27799
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Processing commands for cont...@bugs.debian.org:
> retitle 985468 msmtp-mta: Please cherry-pick 7dcf from upstream for
> bullseye
Bug #985468 [msmtp-mta] Please cherry-pick 7dcf from upstream for bullseye
Changed Bug title to 'msmtp-mta: Please cherry-pick 7dcf from upstream for
Processing commands for cont...@bugs.debian.org:
> severity 985467 critical
Bug #985467 [guix] guix: Risk of local privilege escalation via guix-daemon
Severity set to 'critical' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
985467:
Package: msmtp-mta
Severity: serious
Justification: Does not work with Python's widely used smtplib
Hi,
For release with bullseye, please apply the attached patch from upstream
to version 1.8.11-2 in unstable. When patched, msmtpd also accepts SMTP
commands in lowercase.
Then, the program works
Hi again,
Am 18.03.21 um 06:53 schrieb Rene Engelhard:
> It would be helpful if you actually did your homework. There already was
> 985297 so you now caused a bogus addditional RC bug.
>
> That bug even was marked as blocked by the dpkg bug so being careful
> when reassigning RC bugs would
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package node-jsonld
> # 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
Processing control commands:
> tag -1 patch
Bug #985173 [pacemaker-resource-agents] pacemaker-resource-agents: missing
Breaks+Replaces: pacemaker (<< 2)
Added tag(s) patch.
--
985173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985173
Debian Bug Tracking System
Contact
Followup-For: Bug #985173
Control: tag -1 patch
See the attached patch for fixed B+R. I've verified that this fixes the
failing upgrade paths in my piuparts instance. I'm also offering to NMU
this to buster-pu.
Andreas
diff -Nru pacemaker-2.0.1/debian/changelog pacemaker-2.0.1/debian/changelog
Am 18.03.21 um 08:32 schrieb Andreas Beckmann:
> a clean minimal buster
>
> apt-get install libreoffice-writer # without --install-recommends enabled
>
> or
>
> apt-get install libreoffice-calc # happens both with and without
> --install-recommends enabled
>
Hrm. Indeed.
Regards,
Rene
Hi Jonas,
On mar 18 2021, at 12:05 pm, Jonas Smedegaard wrote:
> Quoting Marco Trevisan (2021-03-18 05:23:41)
> By "launching in a clean schroot" you probably imply that you install
> without respecting recommendations: Debian respects recommendations by
> default, but not when establishing
Processing control commands:
> affects -1 + python3-joblib
Bug #985455 [python3-pkg-resources] python3-pkg-resources: fails to upgrade
from 'buster': ValueError: not enough values to unpack (expected 4, got 3) in
/usr/bin/py3compile
Added indication that 985455 affects python3-joblib
--
Package: python3-pkg-resources
Version: 52.0.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + python3-joblib
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to
Processing control commands:
> affects -1 ibus
Bug #985453 [libclutter-imcontext-0.1-bin] libclutter-imcontext-0.1-bin: fails
to upgrade from 'buster': insufficient dependencies
Added indication that 985453 affects ibus
--
985453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985453
Debian
Package: libclutter-imcontext-0.1-bin
Version: 0.1.4-3.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 ibus
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to
On Thu, 11 Mar 2021 15:17:39 -0400 David Bremner wrote:
> David Bremner writes:
>
> >
> > As far as I can see, the problem is that the setup for elpa-magit and
> > git-el both call "emacs", but that does not exist until the
> > update-alternatives is called. So there seems to be a race condition
Followup-For: Bug #982334
debsums reports
debsums: missing file
/usr/src/linux-headers-5.10.0-4-amd64/include/generated/autoconf.h (from
linux-headers-5.10.0-4-amd64 package)
after installing dahdi-dkms and trying to build the module
Andreas
Quoting Marco Trevisan (2021-03-18 05:23:41)
> Hi Jonas,
>
> > eslint does not depend on but recommends node-text-table, and does so
> > because it is needed only in "all but unusual installations" as
> > covered by Debian Policy § 7.2:
>
> I'm a bit confused by this as launching in a clean
Your message dated Thu, 18 Mar 2021 11:33:28 +
with message-id
and subject line Bug#985443: fixed in puppet-module-rodjek-logrotate 1.1.1+ds1-4
has caused the Debian Bug report #985443,
regarding Module is unusable, and throws rotate must be an integer
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> severity 982991 serious
Bug #982991 [src:matrix-synapse] matrix-synapse: not suitable for inclusion
into bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
982991:
forwarding to the libcxxtools-dev bug, too
On 18/03/2021 12.03, Ansgar wrote to #985440 (pinball-dev):
[...]
Why is there an explicit dependency on libstdc++-dev at all? It should
be part of build-essential. We don't have all development packages
depend on libc-dev and similar either.
[...]>
Package: puppet-module-rodjek-logrotate
Version: 1.1.1+ds1-1
Severity: grave
When using the module without modification, puppet complains (I wrapped it,
so it's easier to read):
Error: Could not retrieve catalog from remote server:
Error 500 on SERVER: Server Error: Evaluation Error:
Error while
[ Also Cc'ed the boost bug. ]
On Thu, 18 Mar 2021 11:40:42 +0100 Andreas Beckmann wrote:
> pinball-dev depends on libstdc++6-4.4-dev | libstdc++-dev
[...]
> Please see https://bugs.debian.org/984838 in libboost1.74-dev for
> more details and a possible solution.
Why is there an explicit
Package: pinball-dev
Version: 0.3.20201218-1
Severity: serious
pinball-dev depends on libstdc++6-4.4-dev | libstdc++-dev, where
libstdc++6-4.4-dev is no longer available and libstdc++-dev is not a good
virtual package to depend upon, since it is provided by multiple packages:
bullseye# apt-get
Package: libcxxtools-dev
Version: 2.2.1-3
Severity: serious
libcxxtools-dev depends on libstdc++-5-dev | libstdc++-dev, where
libstdc++-5-dev is no longer available and libstdc++-dev is not a good
virtual package to depend upon, since it is provided by multiple packages:
bullseye# apt-get
Am 18.03.2021 um 10:52 teilte Andreas Beckmann mit:
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
From the attached log (scroll to the bottom...):
3m48.9s ERROR: FAIL: Broken symlinks:
Processing commands for cont...@bugs.debian.org:
> found 984931 1:2.31.0-1
Bug #984931 [git-el,elpa-magit] git-el,elpa-magit: fails to install:
/usr/lib/emacsen-common/packages/install/git emacs failed at
/usr/lib/emacsen-common/lib.pl line 19, line 7.
There is no source info for the package
Package: texlive-fonts-extra
Version: 2020.20210202-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
3m48.9s ERROR: FAIL: Broken
Package: libstarpu-dev
Version: 1.3.7+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m48.4s ERROR: FAIL: Broken symlinks:
Processing control commands:
> tag -1 - moreinfo unreproducible
Bug #985297 [libreoffice-common] libreoffice-common: do not use dir_to_symlink
for /usr/lib/libreoffice/share/registry
Removed tag(s) moreinfo and unreproducible.
--
985297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985297
Control: tag -1 - moreinfo unreproducible
On 17/03/2021 06.42, Rene Engelhard wrote:
- a clean buster debootstrap + apt install libreoffice-writer
a clean minimal buster
apt-get install libreoffice-writer # without --install-recommends enabled
or
apt-get install libreoffice-calc # happens
reassign 985401 dpkg
thanks
Hi Guillem,
Am 18.03.21 um 00:02 schrieb Guillem Jover:
> Control: reassign -1 libreoffice-common 1:7.0.4-3
It would be helpful if you actually did your homework. There already was
985297 so you now caused a bogus addditional RC bug.
That bug even was marked as
51 matches
Mail list logo
