On Thu, Jun 24, 2021 at 12:20:45AM +0200, Kurt Roeckx wrote:
>
> From the manpage:
>Random State Options
>
>Prior to OpenSSL 1.1.1, it was common for applications to store
>information about the state of the random-number generator in a
>file that was loaded at startup and rewritt
On Wed, Jun 23, 2021 at 09:05:03PM +0200, Sebastian Andrzej Siewior wrote:
> On 2021-06-23 14:46:37 [+0200], Andreas Beckmann wrote:
> > Writing new private key to '/etc/ssl/private/ssl-cert-snakeoil.key'
> > -
> > Warning: No -copy_extensions given; ignoring any extensions in the request
Your message dated Wed, 23 Jun 2021 21:18:24 +
with message-id
and subject line Bug#989596: fixed in nautilus-admin 1.1.9-3.1
has caused the Debian Bug report #989596,
regarding ImportError when used with python3.9
to be marked as done.
This means that you claim that the problem has been deal
Processing control commands:
> tags 989596 + pending
Bug #989596 [nautilus-admin] ImportError when used with python3.9
Added tag(s) pending.
--
989596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags 989596 + pending
Dear maintainer,
I've prepared an NMU for nautilus-admin (versioned as 1.1.9-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru nautilus-admin-1.1.9/debian/changelog nautilus-admin-1.
Processing control commands:
> tags -1 patch
Bug #988267 [src:micropython] micropython ftbfs on at least arm64 where it
built before
Added tag(s) patch.
--
988267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: micropython
Version: 1.14+ds-1
Followup-For: Bug #988267
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu impish ubuntu-patch
Control: tags -1 patch
Dear Maintainer,
* Micropython FTBFS on multiple architectures
* Fixed by pulling in upstream change of variable type
***
Processing control commands:
> tags 989886 + patch
Bug #989886 [src:libyang] libyang: autopkgtest regression
Added tag(s) patch.
> tags 989886 + pending
Bug #989886 [src:libyang] libyang: autopkgtest regression
Added tag(s) pending.
--
989886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=98
Control: tags 989886 + patch
Control: tags 989886 + pending
Dear maintainer,
I've prepared an NMU for libyang (versioned as 1.0.225-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru libyang-1.0.225/debian/changelog
On 2021-05-21 21:37:32 +0200, Moritz Muehlenhoff wrote:
> Source: rust-http
> Severity: grave
> Tags: security
> X-Debbugs-Cc: Debian Security Team
>
> CVE-2019-25009:
> https://rustsec.org/advisories/RUSTSEC-2019-0034.html
> https://github.com/hyperium/http/commit/82d53dbdfdb1ffbeb0323200a0bbd30
Processing commands for cont...@bugs.debian.org:
> fixed 989873 5.3.1-1
Bug #989873 {Done: Nathan Scott } [src:pcp] pcp: FTBFS:
pcp-export-pcp2xlsx is missing files
Marked as fixed in versions pcp/5.3.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
989873: h
Package: clisp
Version: 1:2.49.20180218+really2.49.92-3+b4
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the
past)
Dear Maintainer,
Building clisp package in an OBS instance FTBFS because of the following
test failure:
https://salsa.
On 2021-06-23 14:46:37 [+0200], Andreas Beckmann wrote:
> Writing new private key to '/etc/ssl/private/ssl-cert-snakeoil.key'
> -
> Warning: No -copy_extensions given; ignoring any extensions in the request
> Cannot write random bytes:
> 8022CB35777F:error:127A:random number g
Your message dated Wed, 23 Jun 2021 19:17:07 +
with message-id
and subject line Bug#990158: fixed in shim 15.4-6~deb10u1
has caused the Debian Bug report #990158,
regarding shim-signed-common: No UEFI boot with error "Could not create
MokListXRT"
to be marked as done.
This means that you cla
Your message dated Wed, 23 Jun 2021 19:17:07 +
with message-id
and subject line Bug#990082: fixed in shim 15.4-6~deb10u1
has caused the Debian Bug report #990082,
regarding High chance of boot problems with buster's version of arm64 shim
to be marked as done.
This means that you claim that th
Processing commands for cont...@bugs.debian.org:
> reassign 990240 src:soapyosmo 0.2.5-3
Bug #990240 [sdrangelove] soapyosmo: does not link with boost chrono
Bug reassigned from package 'sdrangelove' to 'src:soapyosmo'.
No longer marked as found in versions sdrangelove/0.0.1.20150707-5.
Ignoring r
Processing control commands:
> reassign -1 src:soapyosmo/0.2.5-3
Unknown command or malformed arguments to command.
> retitle -1 soapyosmo: does not link with boost chrono
Bug #990240 [sdrangelove] sdrangelove: SoapySDR missing DL symbol from boost
library
Changed Bug title to 'soapyosmo: does n
Control: reassign -1 src:soapyosmo/0.2.5-3
Control: retitle -1 soapyosmo: does not link with boost chrono
Control: affects -1 sdrangelove/0.0.1.20150707-5
On 2021-06-23 20:26:40 +0200, Radoslaw Biernacki wrote:
> Package: sdrangelove
> Version: 0.0.1.20150707-5
> Severity: grave
> Justification: r
Package: sdrangelove
Version: 0.0.1.20150707-5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: radoslaw.bierna...@gmail.com
Dear Maintainer,
sdrangelove is unusable due to missing/colision symbol from boost
library required by SoapySDR lib. Right after fresh system installat
Your message dated Wed, 23 Jun 2021 18:18:51 +
with message-id
and subject line Bug#990158: fixed in shim 15.4-6
has caused the Debian Bug report #990158,
regarding shim-signed-common: No UEFI boot with error "Could not create
MokListXRT"
to be marked as done.
This means that you claim that
Your message dated Wed, 23 Jun 2021 18:18:51 +
with message-id
and subject line Bug#990082: fixed in shim 15.4-6
has caused the Debian Bug report #990082,
regarding High chance of boot problems with buster's version of arm64 shim
to be marked as done.
This means that you claim that the proble
Hi Paul,
I just did an apt upgrade, error is history now.
Thank you, the QA team, the kernel team and all the people at Debian for
their hard, efficient and professional work behind the curtains now, in
the past and in the future - I respect and appreciate very much.
Wich you all the best, chee
On Tue, Jun 22, 2021 at 07:57:13AM +0900, Hideki Yamane wrote:
> > Any concerns if I drop the Breaks before the upload?
>
> None, please go ahead for bullseye :)
Upload:
https://tracker.debian.org/news/1243344/accepted-uimaj-2102-4-source-into-unstable/
Unblock bug:
https://bugs.debian.org/cgi-
On Wed, Jun 23, 2021 at 04:10:46PM +0200, Ayke Halder wrote:
>The new build also works on a T5600, thanks a lot!
>
>
>What I did:
>
>1. Upgrade: shim-signed:amd64 (1.33+15+1533136590.3beb971-7,
>1.36~1+deb10u2+15.4-5~deb10u1), shim-signed-common:amd64
>(1.33+15+1533136590.3beb971-7, 1.36~1+deb10u2+
The new build also works on a T5600, thanks a lot!
What I did:
1. Upgrade: shim-signed:amd64 (1.33+15+1533136590.3beb971-7,
1.36~1+deb10u2+15.4-5~deb10u1), shim-signed-common:amd64
(1.33+15+1533136590.3beb971-7, 1.36~1+deb10u2+15.4-5~deb10u1)
--> System does not boot - as expected.
2. Repl
Your message dated Wed, 23 Jun 2021 15:49:40 +0200
with message-id <4870279.aDxsXBin3N@tuxin>
and subject line Re: Bug#989438: CVE-2021-31855
has caused the Debian Bug report #989438,
regarding CVE-2021-31855
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 23 Jun 2021 13:48:26 +
with message-id
and subject line Bug#990226: fixed in keyman-config 14.0.276-2
has caused the Debian Bug report #990226,
regarding keyman: fails to install: keyman.postinst: line 9:
glib-compile-schemas: command not found
to be marked as done.
T
Hi!
I've just prepared a NMU that drops the faulty .service, as proposed.
There's no replacement yet, but window managers that implement some
sort of session persistency will autostart redshift just fine; others
might need manual start.
If full autostart is wanted, it should be implemented using X
On Wed, Jun 23, 2021 at 01:00:51PM +0200, Grzegorz Szymaszek wrote:
>On Tue, Jun 22, 2021 at 10:36:48PM +0100, Steve McIntyre wrote:
>> Could you please verify if this new build fixes the problem you're
>> seeing on your hardware? […] It may still complain about resource
>> failures and "import_mok
Package: openssl
Version: 3.0.0~~alpha16-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package causes other package
to fail installation/upgrading.
>From the attached log (scroll to the bottom...):
...
Setting up openssl
Package: kyotocabinet-utils,libkyotocabinet-dev
Version: 1.2.76-5~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. Th
Package: keyman
Version: 14.0.276-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the a
Package: lazarus-src-2.0
Version: 2.0.12+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to remove some
diversions after upgrading from sid to experimental and removing the package
afterwards.
>From the att
Package: pcp-zeroconf
Version: 5.3.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files
On Tue, Jun 22, 2021 at 10:36:48PM +0100, Steve McIntyre wrote:
> Could you please verify if this new build fixes the problem you're
> seeing on your hardware? […] It may still complain about resource
> failures and "import_mok_state() failed", but should then boot anyway in
> non-secure mode.
It
Package: libprotocol-acme-perl
Version: 1.01-3
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430
ACMEv1 is no longer working with Let's Encrypt, so this
Your message dated Wed, 23 Jun 2021 08:17:05 +
with message-id
and subject line Bug#990204: fixed in skimage 0.18.1-2
has caused the Debian Bug report #990204,
regarding Failing autopkgtest with pillow 8.1.2+dfsg-0.2/ pillow 8.2
to be marked as done.
This means that you claim that the problem
37 matches
Mail list logo
