On Thu, Jul 11, 2019 at 06:25:56PM -0300, Chris Lamb wrote:
> > > I guess in theory but if I recall the details correctly, I don't
> > > /think/ this was going to be a trivial patch to Archive::Zip and my
> > > Perl-fu is/was a bit weak. Would pkg-perl apply and upload a patch
> > > anyway?
> […]
>
On 2019-07-15 08:12, Gürkan Myczko wrote:
only if you are in a hurry otherwise just wait.
Not really, only if cloudcompare not being rebuilt for the pdal mini
transition turns out to be blocker for the testing migration of pdal.
prefer team over nmu though
Will keep that in mind.
Let's w
only if you are in a hurry otherwise just wait.
prefer team over nmu though
> On Jul 15, 2019, at 07:54, Bas Couwenberg wrote:
>
> On 2019-07-15 07:47, Gürkan Myczko wrote:
>> thanks for the patch, can do it in 2 weeks... am abroad without computer.
>
> Shall I do an NMU or team upload in the
On 2019-07-15 07:47, Gürkan Myczko wrote:
thanks for the patch, can do it in 2 weeks... am abroad without
computer.
Shall I do an NMU or team upload in the mean time then?
Kind Regards,
Bas
thanks for the patch, can do it in 2 weeks... am abroad without computer.
best,
> On Jul 14, 2019, at 21:30, Sebastiaan Couwenberg wrote:
>
Control: affects -1 + src:policycoreutils
On Sun, Jul 14, 2019 at 05:59:00PM +, Niels Thykier wrote:
> Of the two issues spotted:
Please also look into policycoreutils.
Helmut
Processing control commands:
> affects -1 + src:policycoreutils
Bug #932073 [debhelper] dh_installinit fails with "--name=foo option specified,
but init script not found"
Added indication that 932073 affects src:policycoreutils
--
932073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932073
Thanks to some people on the IRC channel, we were able to pinpoint the
cause of the problem.
When installing firmware-amd-graphics, the initramfs is not rebuilt, which
makes it impossible for the device to be used.
Running `update-initramfs -u -k all` and rebooting fixed the problem.
Regarding m
On maandag 15 juli 2019 00:33:31 CEST Colin Watson wrote:
> > In the not too distant future, I'll remove that old drive (with WinXP on
> > it) from my system and my guess is that I then will have a problem.
>
> That shouldn't be the case: we store the installation device using a
> /dev/disk/by-id/
On Sun, Jul 14, 2019 at 11:56:39PM +0200, Diederik de Haas wrote:
> On zaterdag 13 juli 2019 09:05:44 CEST Sven Joachim wrote:
> > What I finally figured out after getting my system to boot again, is
> > that grub was still configured to install its core image to /dev/sda,
> > the old hard disk. T
Thanks for your reply, it was very helpful :)
On zaterdag 13 juli 2019 09:05:44 CEST Sven Joachim wrote:
> Most likely you had grub configured to install to the wrong disk, this
> is what happened to me. When I installed an SSD into my old PC back in
> December 2016, I copied all files from the a
On Sun, Jul 14, 2019 at 01:27:23PM -0700, Slava Kryvel wrote:
> After upgrade from Debian 9.9 to Debian 10 I have got unbootable system.
>
> I'm using Xen hypervisor, which was also upgraded from 4.8 to 4.11
> during OS upgrade.
> UEFI is enabled.
>
> After upgrade was finished, I was unable to b
Hi,
On zondag 14 juli 2019 21:38:14 CEST Hillel Lubman wrote:
> 20190502-1 is already outdated, since amdgpu firmware had some updates
> upstream:
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> /log/amdgpu
>
> Does this problem still occur if you use latest upstre
Package: grub-common
Version: 2.02+dfsg1-20
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
After upgrade from Debian 9.9 to Debian 10 I have got unbootable system.
I'm using Xen hypervisor, which was also upgraded from 4.8 to 4.11
during OS upgrade.
UEFI is enabled.
Package: sssd
Version: 2.2.0-3
Severity: grave
Justification: renders package unusable
After upgrading to 2.2.0-3, sssd will not start (automatically).
There are two failure modes, both likely related to #886483 I
reported over a year ago.
First failure mode happens if any services are listed i
Hi.
20190502-1 is already outdated, since amdgpu firmware had some updates upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/amdgpu
Does this problem still occur if you use latest upstream firmware?
By the way, it works well for me (Ryzen 7 2700X / Vega 56
On 7/14/19 8:59 AM, Bas Couwenberg wrote:
> liblas will be removed from Debian, it's dead upstream, has outstanding
> security issues, and FTBFS with GDAL 3.
>
> Please drop the build dependencies from your package as per the attached
> patch.
>
> Those build dependencies seems to be unused any w
Helmut Grohne:
> Package: debhelper
> Version: 12.2
> Severity: serious
> Tags: ftbfs
> Control: affects -1 + src:openssh src:util-linux
> User: helm...@debian.org
> Usertags: rebootstrap
>
> debhelper 12.2 fixes #462389 and makes dh_installinit fail when the
> --name'd init script does not exist.
Processing control commands:
> affects -1 + src:openssh src:util-linux
Bug #932073 [debhelper] dh_installinit fails with "--name=foo option specified,
but init script not found"
Added indication that 932073 affects src:openssh and src:util-linux
--
932073: https://bugs.debian.org/cgi-bin/bugrep
Package: debhelper
Version: 12.2
Severity: serious
Tags: ftbfs
Control: affects -1 + src:openssh src:util-linux
User: helm...@debian.org
Usertags: rebootstrap
debhelper 12.2 fixes #462389 and makes dh_installinit fail when the
--name'd init script does not exist. This behaviour change makes at
lea
Your message dated Sun, 14 Jul 2019 13:52:05 +
with message-id
and subject line Bug#931971: fixed in python-xarray 0.12.1-2
has caused the Debian Bug report #931971,
regarding python-xarray: needs source-only upload
to be marked as done.
This means that you claim that the problem has been dea
Source: knot-resolver
Version: 3.2.1-3
Severity: grave
Tags: security upstream
Hi,
The following vulnerabilities were published for knot-resolver.
CVE-2019-10190[0]:
do not pass bogus negative answer to client
CVE-2019-10191[1]:
do not cache negative answer with forged QNAME+QTYPE
[2] contains
Processing commands for cont...@bugs.debian.org:
> tags 931081 + stretch bullseye
Bug #931081 {Done: Nicolas Braud-Santoni } [libyubikey-udev]
libyubikey-udev: missing Breaks+Replaces: libykpers-1-1 (<< 1.19.3)
Added tag(s) stretch and bullseye.
> thanks
Stopping processing here.
Please contact
Processing commands for cont...@bugs.debian.org:
> tags 931081 - stretch + buster
Bug #931081 {Done: Nicolas Braud-Santoni } [libyubikey-udev]
libyubikey-udev: missing Breaks+Replaces: libykpers-1-1 (<< 1.19.3)
Removed tag(s) stretch.
Bug #931081 {Done: Nicolas Braud-Santoni } [libyubikey-udev]
Processing commands for cont...@bugs.debian.org:
> found 932020 cloudcompare/2.10.1-2
Bug #932020 [src:cloudcompare] cloudcompare: Don't build depend on liblas, will
be removed from Debian
Marked as found in versions cloudcompare/2.10.1-2.
> thanks
Stopping processing here.
Please contact me if
Processing control commands:
> block -1 by 932020
Bug #932021 [ftp.debian.org] RM: liblas -- ROM; Dead upstream, outstanding
security issues, FTBFS with GDAL 3
932021 was not blocked by any bugs.
932021 was not blocking any bugs.
Added blocking bug(s) of 932021: 932020
--
932021: https://bugs.d
Source: cloudcompare
Version: 2.10.3-1
Severity: serious
Tags: patch
Justification: makes the package in question unusable or mostly so
Dear Maintainer,
liblas will be removed from Debian, it's dead upstream, has outstanding
security issues, and FTBFS with GDAL 3.
Please drop the build dependenc
27 matches
Mail list logo
