On Thu, Dec 05, 2019 at 09:50:32AM -0800, Felix Lechner wrote:
>Implemented for NEWS, which was your primary concern:
>
>
> https://salsa.debian.org/lintian/lintian/commit/ae38f4d7301ba8a6064025b86984d49843d61355
>
Looks awesome. I was working on a hack but this is much better.
One question
On Thu, Dec 05, 2019 at 03:13:09PM -0800, Felix Lechner wrote:
>Hi Vincent,
>
>On Thu, Dec 5, 2019 at 2:32 PM McIntyre, Vincent (CASS, Marsfield)
> wrote:
>>
>> +} elsif ($basename =~
>> m/^(?:.*\.)?(?:changelog|NEWS|TODO).[dD]ebian$/o) {
>
>M
Hello
lintian is now checking for this case (NEWS|TODO), see #946126.
Regards
Vince
That would appear to be #429510.
This seems like a job for lintian. #946126.
Package: libgdk-pixbuf2.0-0
Version: 2.31.1-2+deb8u8
Severity: normal
Dear LTS Maintainer,
I noticed this and thought I should report it.
...
The following packages will be upgraded:
libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need
Forgot to add this
$ ldd
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-tiff.so
linux-vdso.so.1 (0x7fff12fb5000)
libtiff.so.5 => /usr/lib/x86_64-linux-gnu/libtiff.so.5
(0x7f2c236e5000)
libgdk_pixbuf-2.0.so.0 =>
On Tue, Dec 03, 2019 at 08:38:55PM -0800, Felix Lechner wrote:
>Hi Vincent,
>
>
>> There may already be a similar check for debian/[README|TODO].Debian
>
>Which tag are you referring to, please?
>
I'm sorry, I don't know of one. I was just speculating that lintian
may have a check like this.
Hello
Not sure quite where to direct this.
This recent DLA
https://www.debian.org/lts/security/2020/dla-2123
references the wrong debian bug, 925666.
The correct number is 952666.
Kind regards
Vince
The issue I reported is fixed in upstream's 1.43.
Package: libapache2-mod-jk
Version: 1:1.2.46-1
Tags: patch
Followup-For: Bug #928813
I am seeing this too. I worked around like this
# cd /etc/apache2/mods-available
# ln -s httpd-jk.conf jk.conf
# a2enmod jk
Enabling config file jk.conf.
To activate the new configuration,
On Sun, May 17, 2020 at 02:34:47PM +0200, Holger Wansing wrote:
>Hi,
>
> wrote:
>> Package: installation-guide
>> Version: 20180930
>> Severity: wishlist
>> Tags: patch
>>
>> Hi
>>
>> recently I was learning about presseding UEFI installs and
>> I think the install guide could use a small addition
Hi
I thought this would have been fixed by this commit
https://salsa.debian.org/installer-team/partman-auto/-/commit/79bea1c75d2fd9fbd6eb01c1bea6de2914d24d22
which will be available in the 'daily' build of the installer.
I don't know what the prospects are for having this applied to
the
On Fri, May 29, 2020 at 11:29:17PM +0200, Holger Wansing wrote:
>Hi,
>
>"McIntyre, Vincent (CASS, Marsfield)" wrote:
>> diff --git a/en/appendix/preseed.xml b/en/appendix/preseed.xml
>> index d7570d6b3..817749bb9 100644
>> --- a/en/appendix/preseed
Fixed: 0.22.11
I think this bug can be closed.
$ apt-show-versions apt-show-versions
apt-show-versions:all/buster 0.22.11 uptodate
$ sudo apt-mark hold linux-image-amd64
$ apt-show-versions | grep upgradeable
linux-image-4.19.0-8-amd64:amd64/buster 4.19.98-1 upgradeable to
4.19.98-1+deb10u1
ah yes, the attachment...
diff --git a/apt-show-versions b/apt-show-versions
index fd0dab4..9bfa3b0 100755
--- a/apt-show-versions
+++ b/apt-show-versions
@@ -36,6 +36,7 @@ use Storable qw(nstore retrieve);
my $apackagescachefile="/var/cache/apt-show-versions/apackages-multiarch";
my
Package: apt-show-versions
Version: 0.22.11
Severity: normal
Tags: patch
Dear Maintainer,
when root has a restrictive umask, the files it writes in
/var/cache/apt-show-versions end up not being readable by
normal users, which is somewhat irritating.
The attached patch addresses this. It was
please close this duplicate of 973268. apologies for the resend.
Package: openjdk-11-jdk-headless
Version: 11.0.9+11-1~deb10u1
Severity: minor
This was a suprise, but perhaps it's intended behaviour.
Please close if so.
* What led up to the situation?
These packages were waiting for upgrade
openjdk-11-jre 11.0.8+10-1~deb10u1 ->
Package: openjdk-11-jdk-headless
Version: 11.0.9+11-1~deb10u1
Severity: minor
This was a suprise but perhaps intended. Please close if so.
* What led up to the situation?
These packages were waiting for upgrade
openjdk-11-jre 11.0.8+10-1~deb10u1 -> 11.0.9+11-1~deb10u1
I'm wondering if the error gcc is throwing is really a valid error.
These mismatches are coming because an INGEGER*8 is being passed
via %VAL() so this is actually passing by value (instead of the
usual fortran pass-by-reference).
For the first error at line 248,
- PIXMAP is initialised by a
Package: wsclean
Version: 2.9-2
Severity: minor
I was trying to build this version on buster and got build failures.
I tried in a sid schroot and got the same failure, so reporting.
I was building with 'debian/rules binary'.
Also tried 'debian/rules build; debian/rules binary', as per [1].
Source: collectd
Version: [patch] update debian/watch
Severity: minor
Tags: patch
The naming scheme for github tags seems to differ from collectd.org.
diff --git a/debian/watch b/debian/watch
index 5ba76a4..a07f606 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,2 +1,2 @@
version=3
Package: partman-efi
Version: 84
Severity: minor
If find the partman-efi/non_efi_system question somewhat confusing.
If one sets it to 'false' that means the installer will configure
the system for BIOS mode booting, even if the installer is running
in EFI mode.
If one sets it 'true', then even
On Mon, Jun 01, 2020 at 02:34:40PM +1000, Vincent McIntyre wrote:
>
>Revised patch below. I'll test it on amd64 and let you know
>if it works.
This has now been tested on a number of installs and works ok.
I think it's good to go now.
The partman-efi/non_efi_system question is somewhat
Package: isync
Version: 1.3.0-2
Severity: wishlist
Dear Maintainer,
there seems to be a new upstream version (mid-2019) but for some reason
the PTS is not noticing that. Updating looks relatively straightforward,
though obviously more involved than my simple test below.
Kind regards
Vince
%
Tags: patch
This (tested) patch works around the FTBFS in a sid amd64 schroot.
@@ -68,9 +68,9 @@ build-stamp: $(64-BIT_BUILD_STAMP)
cd $(bdir); $(curdir)/makemake $(curdir) linux g77_gcc
# changeperl no longer necessary - upstream uses /usr/bin/perl now
# perl debian/changeperl
- cd
I think these issues should be fixed by upstream now
https://github.com/karelzak/util-linux/commit/4b447adf50c61125c57922cc01ec3e6792cc48af#diff-ebbebd514b5c6a5308506642a9de143627256373989a032476e00fb44ec2a27a
--
Package: debootstrap
Severity: wishlist
Tags: patch
Thanks
Hello
please consider applying this small patch to the manpage.
Kind regards
Vince
From 1e15507bacfb2547e1c2bace7c3781dd3ab2f45c Mon Sep 17 00:00:00 2001
From: Vincent McIntyre
Date: Mon, 7 Jun 2021 20:29:08 +1000
Subject: [PATCH]
On Sun, Mar 21, 2021 at 11:33:38AM +, Justin B Rye wrote:
>Paul Gevers wrote:
>>> I'd forgotten the *Buster* release notes *do* mention usrmerge:
>>>
>>> https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-new.html#merged-usr
>>>
>>> but we've taken that part out now. Could we
Package: nis
Version: 3.17.1-3+b1
Severity: important
This is a very irritating bug.
It may not be worth fixing but it should be recorded.
Between stretch and buster, something subtle changed in makedbm.
A map produced by the makedbm in stretch starts with the byte 0xCE.
A map produced by the
On Fri, Mar 05, 2021 at 09:51:34AM +0100, Francesco P. Lovergine wrote:
Thank you for the quick reply.
I agree with all your points and that there's little to be done but
document the issue. I'm happy for this to be closed.
If both buster & bullseye link with libgdbm6 then I agree
it's unlikely
31 matches
Mail list logo
