Paul Gevers wrote:
> Minimal system upgrade
> +
> +
> +
> +If you upgrade remotely, be aware of linkend="ssh-not-available"/>.
> +
> +
Yes, this looks good. The link text appears as "Section x.y.z, *No
new SSH connections possible during upgrade*", right?
Package: release-notes
Severity: normal
Tags: patch
Hi,
On IRC I was trigger that we may want to add a warning at the start of
the paragraph 4.4.4 (minimal upgrade).
I prepared the attached patch.
Paul
>From 36acbddbf23c96a9ba141ac2a06e17789e3e45a9 Mon Sep 17 00:00:00 2001
From: Paul Gevers
On Sat, 7 Aug 2021, Sven Geuer wrote:
I tried to reproduce your observation using tightvncserver 1:1.3.10-3
but didn't encounter any key mapping issues.
Can you provide me with instuctions how to verify this bugs still
persists?
I've been continuing with TigerVNC for the nearly 5 years since
On Sun, 8 Aug 2021 10:17:06 -0500 Brian Thompson wrote:
> I like that proposal and think it makes a lot of sense. `gh` does seem
> too short, and while easy to identify for current gh users, maybe it
> will be more difficult to find in apt for new users. Also, as you
> mentioned, a namespace
Package: extrepo
Version: 0.8
Severity: normal
If I install a package using a supported external repo:
extrepo enable brave_release
apt update
apt install brave-browser
the current Brave signing key will automatically be fetched and placed in
/var/lib/extrepo/keys/.
However, when Brave
On Fri, Aug 13, 2021 at 03:07:46PM -0600, Ross Vandegrift wrote:
> [ Checklist ]
> [X] *all* changes are documented in the d/changelog
> [X] I reviewed all changes and I approve them
> [X] attach debdiff against the package in (old)stable
Apologies - reportbug -r seems to have missed the
> [ Tests ]
>
> The upstream fix adds a unit test for this issue. This and the other tests
> pass during package build.
Also note that the patch is included upstream with 21.2-1, which is
currently in unstable and has been tested.
noah
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: rvandegr...@debian.org, debian-cl...@lists.debian.org
[ Reason ]
The version of sudo in bullseye introduces a new syntax for includes,
"@includedir". This is
Dear Maintainer,
I confirm this issue. After upgrade to Debian 10.10 (including a new
version shim-signed), Secure Boot no longer works.
I proceeded as usual :
- I added my key via command
# mokutil --import my-key.der
- I rebooted
- I obtained shim screen to propose enroll my
Hello,
On Fri 13 Aug 2021 at 12:36PM -07, Felix Lechner wrote:
> How do you know that people actually bring their packages up to the
> latest policy revision before they update the Standards-Version field?
There is a "must" requirement not to do that in Policy, and I trust DDs
to follow those.
Hi Sean,
On Fri, Aug 13, 2021 at 11:08 AM Sean Whitton wrote:
>
> It is useful metadata about the state of a package for when NMUers or
> those outside of Debian want to work with it.
How do you know that people actually bring their packages up to the
latest policy revision before they update
Hello Sam,
On Thu 12 Aug 2021 at 05:35PM -06, Sam Hartman wrote:
> I thought I provided such an argument.
> (you trimmed that part of my message when replying).
> My argument was roughly that things like build systems, use of dh,
> debian/rules interfaces etc might well need to apply to source
Hello Sam,
On Thu 12 Aug 2021 at 05:35PM -06, Sam Hartman wrote:
> I thought I provided such an argument.
> (you trimmed that part of my message when replying).
> My argument was roughly that things like build systems, use of dh,
> debian/rules interfaces etc might well need to apply to source
Hello,
On Fri 13 Aug 2021 at 08:10AM -07, Felix Lechner wrote:
> Hi,
>
> On Fri, Aug 13, 2021 at 12:57 AM Bill Allombert wrote:
>>
>> Is there some new external factor that make any unaddressed lintian
>> warnings problematic ?
>
> That may go beyond the scope of the present discussion, but
Hello Felix,
On Thu 12 Aug 2021 at 06:17PM -07, Felix Lechner wrote:
> Would you please point to the argument for why d-i micro debs are
> exempt from policy, or from a documented Standards-Version, or both?
As has been noted by Phil Hands, one of the points of having udebs is to
be able to
Package: udisks2
Version: 2.9.2-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
udisks2 currently Recommends exfat-utils which Conflicts with exfatprogs. Since
the Linux kernel 5 shipping with Bullseye includes native exFAT support,
exfatprogs is the preferred utility
Hi Roland,
> > So it appears to me that different code is activated for regular users
> > and root.
In addition to the filesystem device difference (discussed below), the
other highly relevant difference is that processes run as root are
terminated by the OOM killer with a slower priority.
This
Package: src:firwmare-sof
Severity: important
Version: 1.7-1
I just upgraded a notebook to a fresh Debian 11 system (I started the
system with Debian testing +/- a year ago).
The notebook device is a Lenovo Thinkpad 13S. A year ago, I turned the
dsp_driver on to work-around the
Hi,
On Fri, Aug 13, 2021 at 9:12 AM Bill Allombert wrote:
>
> Then I would suggest that a new lintian category is designed to catter
> for such usage, so that tools might chose not to display such warnings
> as they do with 'P: pedantic' currently.
I am not sure that helps. The tag
On Fri, Aug 13, 2021 at 08:10:57AM -0700, Felix Lechner wrote:
> Hi,
>
> On Fri, Aug 13, 2021 at 12:57 AM Bill Allombert wrote:
> >
> > Is there some new external factor that make any unaddressed lintian
> > warnings problematic ?
>
> That may go beyond the scope of the present discussion, but
On Thu, Aug 12, 2021 at 04:09:15PM -0500, William 'jawn-smith' Wilson wrote:
> Due to an incompatible function prototype in the openbsd-compat tests,
> this package FTBFS with glibc >= 2.34. There is already an upstream
> commit to fix it, so I have pulled that in to this version of the
> package.
Hi,
On Fri, Aug 13, 2021 at 12:57 AM Bill Allombert wrote:
>
> Is there some new external factor that make any unaddressed lintian
> warnings problematic ?
That may go beyond the scope of the present discussion, but yes:
First, Lintian packaging hints are always viewed as imperfections;
Package: mailman3-web
Version: 0+20180916-8
Severity: important
Dear Maintainer,
I recently installed mailman3-full to make the switch from mailman 2.x before
it's being discontinued. While the installation was quite a hassle since both
mailman3 and mailman3-web had severe issues talking to
Package: firefox
Version: 57.0.0
Severity: serious
Tags: upstream
Justification: Policy 4.13
Forwarded: https://bugzilla.mozilla.org/show_bug.cgi?id=1420286
X-Debbugs-Cc: pkg-javascript-de...@lists.alioth.debian.org
Control: tags -1 + security
Hi,
By default firefox does not allow symlink in
On Thu, 12 Aug 2021 21:51:09 -0400 Andres Salomon
wrote:
> So this only affects users who do or do not have the ssh metapackage
> installed?
I'm pretty sure it effects both.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
forwarded 982122 https://github.com/redis/redis/issues/9369
thanks
Hi Julien,
> https://people.debian.org/~jcristau/redis_6.2.5-2_s390x-2021-08-11T16:17:34Z
This was very useful and, in conjunction with your suggestion of
potentially reproducing it on a porterbox, I have been able to
reproduce
Hi,
I have attached a more complete patch which fixes some more encoding
errors.
Cheers,
--
Guinness
From c26f38014c2ce51bd28648273b4d8c07d94dbd07 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?R=C3=A9mi=20Oudin?=
Date: Fri, 13 Aug 2021 14:16:58 +0200
Subject: [PATCH] Fix mail encoding errors
---
Okay, so I tried to build all binary packages from one source package.
Not sure if it's the good way.
It builds those binary packages:
awf-gtk2 - A widget factory is a theme preview application for GTK
awf-gtk3 - A widget factory is a theme preview application for GTK
awf-gtk4 - A widget
On vrijdag 13 augustus 2021 13:42:33 CEST Aníbal Monsalve Salazar wrote:
> > Preface attempt 1:
> > Yesterday after downgrading to -4, I did a 'fakeroot debian/rules binary-
> > indep' and that succeeded successfully.
> >
> > Attempt 1:
> > After upgrading to -5, without running 'make clean' or
On 13.8.2021 13.52, Simon McVittie wrote:
Package: xwayland
Version: 2:1.20.11-1
Severity: important
Forwarded: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1209
Tags: fixed-upstream
Control: found -1 2:1.20.13-1
When setting display modes with Xrandr, the recommended pattern seems
to
> It built fine but there are flaky test issues. I'm working with
> upstream to either address or disable those tests. That doesn't change
> the fact that it was uploaded.
Thanks for uploading this version of package, it seems that some
"origin" (without debian/) files in git VCS (in Debian
[ add bug-c...@gnu.org ]
[ add Salvatore Bonaccorso ]
On Fri, 2021-08-13 12:13:18 +0200, Diederik de Haas wrote:
> Adding Salvatore in this loop as he is FAR more knowledgeable wrt kernel
> compilation then I am to rule out mistakes I made (I'm a noob).
>
> On vrijdag 13 augustus 2021 10:51:09
Package: auto-apt-proxy
Version: 13.3
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu impish ubuntu-patch
X-Debbugs-Cc: j...@debian.org
In Ubuntu, the attached patch was applied to achieve the following:
* Pass -o Acquire::Retries=0 to apt-helper,
Package: xwayland
Version: 2:1.20.11-1
Severity: important
Forwarded: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1209
Tags: fixed-upstream
Control: found -1 2:1.20.13-1
When setting display modes with Xrandr, the recommended pattern seems
to be to disable the CRTC with
Hi,
On Tue, Jun 05, 2018 at 02:42:50PM +0200, Julien Muchembled wrote:
> Le 06/05/18 à 14:20, Guido Günther a écrit :
> > Does this work as you'd expect it:
> >
> > $ gbp clone g...@salsa.debian.org:python-team/modules/zc-lockfile.git
> > $ gbp pq import
> > $ git co debian/master
> > $ gbp
Package: src:apitrace
Version: 9.0+repack-1
Severity: important
Tags: sid bookworm
Forwarded: https://github.com/apitrace/apitrace/issues/756
See the upstream report for the details. The upstream version 10.0 doesn't
address this yet.
Package: firefox
Severity: important
Control: tags -1 + security
Dear Maintainer,
It will be really nice to document in README.Source the reason and why some
library are embeded.
It was done in the past, so it could be done
BTW https://salsa.debian.org/security-tracker-team/security-
On Thu, 2021-08-12 16:18:02 +0200, Diederik de Haas wrote:
> Control: tag -1 fixed-upstream patch
>
> I ran into this problem too at the exact same step of a kernel build.
> Upstream author responded with
> "Thanks. Fixed in dfc801c44a93bed7b3951905b188823d6a0432c8"
>
On Wed, 2021-08-11 16:25:01 +0200, Salvatore Bonaccorso wrote:
> Source: cpio
> Version: 2.13+dfsg-5
> Severity: serious
> Tags: upstream
> Justification: regression, has influences to other programs, partially FTBFS
> of packages, and other impact
> X-Debbugs-Cc: car...@debian.org
>
> Hi
>
>
Package: actor-framework
Version: 0.17.6-2
Followup-For: Bug #983959
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu impish ubuntu-patch
X-Debbugs-Cc: sl...@ubuntu.com
Control: tags -1 patch
Dear Maintainer,
actor-framework fails to build with GCC-11 due to a missing:
#include
This
With motion_4.3.2-1_arm64.deb I also get the error message on installation.
The project seems active on Github [1], maybe it is worthwhile to raise an
issue there?
[1] https://github.com/Motion-Project/motion
On Thu, Aug 12, 2021 at 06:17:18PM -0700, Felix Lechner wrote:
> Finally, please allow me to add some powerful statistics to the
> record. The tag 'out-of-date-standards-version' currently occurs in
> 10,813 source packages in the archive (out of about 33,000). [7] It is
> an incident ratio of
Source: bamtools
Version: 2.5.1+dfsg-9
X-Debbugs-CC: debian...@lists.debian.org
Severity: important
User: debian...@lists.debian.org
Usertags: fails-always timeout
Dear maintainers,
Recently, you fixed bug #987023 and I enabled bamtools again on all
architectures in unstable and testing. It
This has been reported as
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/582.
And it has already been fixed, but not yet released.
The patch reverts a workaround for a bug in usbguard<0.7.7.
44 matches
Mail list logo
