Bug#966338: tomcat9: overrriding JAVA_HOME in /e/d/tomcat9 has changed

Package: tomcat9 Version: 9.0.31-1~deb10u2 Severity: normal Tags: patch I'm reporting a change in behaviour from tomcat8 and I'm not sure what the correct fix is. While I'm reporting against the buster version, the issue still seems to exist in current git (1ac6d044 Update changelog). The gist

Bug#959219: davmail: minor backporting issues

Subject: davmail: minor backporting issues Package: davmail Version: 5.5.1.3299-2 Severity: wishlist Tags: patch I was trying to build this on buster and hit a couple of small issues. Not sure how many of these qualify as 'bugs' vs 'features' but thought I would report just in case some need

Bug#946126: lintian: Please complain about debian/NEWS.Debian

Package: lintian Version: 2.39.0 Severity: wishlist Dear Maintainer, unison (2.48.4-3) was released without an important note in the NEWS file. The note was in the package source, but not included in the binary package. See bug 946041. The reason for this appears to be longstanding, see bug

Bug#870448: hw-detect - stop using modprobe -l

On Wed, Aug 02, 2017 at 07:58:05PM +0100, Ben Hutchings wrote: > On Wed, 2017-08-02 at 12:26 +1000, Vincent McIntyre wrote: > > Package: hw-detect > > Version: 1.124 > > Severity: normal > > Tags: patch > > > > I keep seeing this in installer logs, back t

Bug#916663: libc6-udeb segfaults in buster alpha 4

Package: libc6-udeb Version: 2.28-2 Severity: important Trying to install with the netinst image from [1] The hardware is a Dell Optiplex with 64-bit Intel processor. There is an old install of jessie on the disk, which is two SSDs in software raid-1. One partition for /, the rest is LVM. I am

Bug#301953: retry mostly works now

Version: 1:1.3.4-2.1 nfs-common version 1:1.3.4-2.1 kernel linux-image-4.9.0-8-amd64 4.9.130-2 It takes a little longer than the advertised 60s. It tries 10 times and gives up. % /usr/bin/time -p sudo mount - -t nfs -o vers=3,retry=1 192.168.30.1:/blah /mnt mount.nfs:

Bug#756171: duplicate

This seems to be a duplicate of 756170 and should be merged or closed. Kind regards Vince --

Bug#857043: mountstats?

Hello Pere does # /usr/sbin/mountstats /path/to/mount do what you are looking for? the code does seem to have some reporting of timeouts if there are retries occurring. Kind regards Vince

Bug#860264: ifquery behaviour

# grep auto /etc/network/interfaces auto lo # grep hotplug /etc/network/interfaces allow-hotplug enp0s31f6 # ifquery --read-environment --list --exclude=lo # as in unit file # # ifquery --read-environment --list --exclude=lo --allow auto # # ifquery --read-environment --list --exclude=lo --allow

Bug#756170: mount option timeo - in deciseconds, or seconds?

I think this report is incorrect. If you agree, please close it. If not, please offer some evidence for your belief. My evidence is below. I looked in the upstream git of nfs-utils. The 'deciseconds' has been in there since the start of git history (2007, commit id

Bug#895384: fixed in git?

This seems to have been addressed by Laurent recently (thanks!) https://salsa.debian.org/debian/nfs-utils/commit/cd79aec324fe58a240b29d53445de33147eb166b Laurent, perhaps the changelog line could have (Closes: #895384) appended? I'm not sure what the protocol is here. Kind regards Vince

Bug#892654: duplicate of 857912?

Thanks for your report. It looks very like a duplicate of 857912. If you agree, could you close this bug or merge it? Kind regards Vince

Bug#868099: is this still an issue?

For rkhunter 1.4.2-6+deb9u1 % cat /var/lib/dpkg/info/rkhunter.conffiles /etc/apt/apt.conf.d/90rkhunter /etc/cron.daily/rkhunter /etc/cron.weekly/rkhunter /etc/logcheck/ignore.d.server/rkhunter /etc/logrotate.d/rkhunter /etc/rkhunter.conf % dpkg -S /etc/default/rkhunter dpkg-query: no path found

Bug#914256: lintian: conflict between no-template-description and untranslatable-debconf-templates

On Thu, Nov 22, 2018 at 12:24:19PM -0500, Chris Lamb wrote: > Hi Vincent, > > > E: hello source: not-using-po-debconf > > E: hello: no-template-description hello/all-languages > > E: hello: unknown-field-in-templates hello/all-languages _description > > > > So still the same problem. > > Sorry,

Bug#914308: ifenslave: typo in bonding example

Package: ifenslave Version: 2.9 Severity: normal Tags: patch (sorry for the mess Guus) diff --git a/debian/examples/two_hotplug_ethernet b/debian/examples/two_hotplug_ethernet index 4d7f75f..9012e15 100644 --- a/debian/examples/two_hotplug_ethernet +++ b/debian/examples/two_hotplug_ethernet @@

Bug#914256: lintian: conflict between no-template-description and untranslatable-debconf-templates

> Hm, I can't seem to reproduce this in the lintian testsuite. After adding: > > --- a/t/tests/legacy-debconf/debian/debian/debconf-test.templates > +++ b/t/tests/legacy-debconf/debian/debian/debconf-test.templates > @@ -99,3 +99,15 @@ Type: boolean >_Description: Decide, lintian >

Bug#914256: lintian: conflict between no-template-description and untranslatable-debconf-templates

On Wed, Nov 21, 2018 at 03:38:01AM -0500, Chris Lamb wrote: > Hi Vincent. > > > Version: 2.5.50.4 > […] > > I also had a look at the git repository and could not see recent > > work related to either of the tags involved here. > > Granted and will try and reproduce later but just an FYI that >

Bug#914256: lintian: conflict between no-template-description and untranslatable-debconf-templates

Package: lintian Version: 2.5.50.4 Severity: normal * What led up to the situation? (The issue is independent of the 'hello' package, I just used it to make reproduction easier.) $ apt-get source hello $ cd hello-2.10 $ cat > debian/templates Template: hello/all-languages Type: boolean

Bug#913207: mytop: depends on libconfig-inifiles-perl but package does not Depend on it

Package: mariadb-client-10.1 Version: 10.1.26-0+deb9u1 Severity: normal Dear Maintainer, * What led up to the situation? $ mytop Can't locate Config/IniFiles.pm in @INC (you may need to install the Config::IniFiles module) (@INC contains: /etc/perl

Bug#906904: a workaround

Installing the following file and rebooting allows the nvidia drivers to retain control of the console. % cat /etc/modprobe.d/i915.conf # This module conflicts with the nvidia drivers & blacklisting does not work install i915 /bin/true This workaround is probably only useful for similar

Bug#907837: suggested patch

Not quite sure about the wording, but a first try: diff --git a/en/install-methods/install-tftp.xml b/en/install-methods/install-tftp.xml index 868c70155..7236fa836 100644 --- a/en/install-methods/install-tftp.xml +++ b/en/install-methods/install-tftp.xml @@ -178,7 +178,10 @@ For PXE booting,

Bug#906903: nvidia-driver: broken(?) dependencies

On a system where I have been successfully mixing stable & backports I hit the same dependency problem. So I think this is a recent change. I tried to dig a bit further to see if I could flush out the cause. TL;DR libegl1-glvnd-nvidia, which I previously installed from backports, is only

Bug#906903: nvidia-driver: broken(?) dependencies

On Wed, Aug 22, 2018 at 03:57:51PM +0100, Luca Boccassi wrote: > > Because I suspect something on your system is causing some packages to > be picked from backports and some from stable. That's what's breaking. > So try and remove any custom configuration you have for apt and then it > should

Bug#906903: nvidia-driver: broken(?) dependencies

On Wed, Aug 22, 2018 at 11:04:19PM +0200, Andreas Beckmann wrote: > On 2018-08-22 04:31, Vincent McIntyre wrote: > > # apt-cache policy nvidia-driver > > nvidia-driver: > > Installed: (none) > > Candidate: 384.130-1 > > Version table: >

Bug#906903: nvidia-driver: broken(?) dependencies

On Wed, Aug 22, 2018 at 11:09:51AM +0100, Luca Boccassi wrote: > Control: tags -1 moreinfo > I tried to dig deeper into the source of the conflict. The crude script below tries to pull out any conflicts that the recursive dependencies of nvidia-egl-icd have and looks for overlap with the

Bug#906903: nvidia-driver: broken(?) dependencies

> > Are you sure? Your first email showed the priority of one pkg as "990" > rather than the default 500 I agree it is strange but apt-cache priority scores never make any sense to me. $ /bin/ls /etc/apt/preferences.d/ backports I tried the obvious experiment $ cat

Bug#906903: nvidia-driver: broken(?) dependencies

On Wed, Aug 22, 2018 at 11:09:51AM +0100, Luca Boccassi wrote: > Control: tags -1 moreinfo > > > Hi, > > From your logs, it seems you have a non-standard /etc/apt/preferences* > files. Can you please share them? # cat /etc/apt/preferences.d/backports Explanation: Low priority to avoid

Bug#906904: nvidia-driver: No tty display after nvidia-modeset

Package: nvidia-driver Version: 384.130-1 Severity: important * What led up to the situation? # apt-get install nvidia-driver nvidia-egl-icd * What exactly did you do (or not do) that was effective (or ineffective)? Rebooted system after driver installation, with the 'quiet'

Bug#906903: nvidia-driver: broken(?) dependencies

Package: nvidia-driver Version: 384.130-1 990 Severity: normal Dear Maintainer, * What led up to the situation? I had a working stretch system using nouveau. I wanted to try the nvidia drivers, since I had used them in jessie, on the same hardware. * What exactly did you do (or

Bug#580312: multipath-tools: multipathd segfaults when restarted

On Sat, Aug 11, 2018 at 05:09:58PM +0200, Chris Hofstaedtler wrote: > > Do you still see this in current versions? No, have not seen this occur again like this that I can recall; we would have followed up to this bug if we had. I think this bug can probably be closed, the code has improved

Bug#902565: autofs not migrated to salsa.d.o(?)

Package: autofs Severity: normal I was trying to find the autofs source on salsa and was unable to after a fair bit of rummaging around. The old alioth repo is archived at [1]. Is it possible to migrate it to salsa, from that tar ball? Kind regards Vince [1]

Bug#799781: ping

Hi just checking why this was still open - I see that the jessie tree now contains the patch 'libmultipath: use a shared lock to co-operate with udev' and is tagged 0.5.0-6+deb8u3. But it seems to have missed the 8.10 point release, and is not lurking in jessie-proposed-updates; 0.5.0-6+deb8u2 is

Bug#826570: possible fix

There is a possible resolution here https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=02628413ca99648e70e38406384be69e20a2a6ce which just takes out a workaround for a now-resolved bug. I have not tested this as I have only ever seen this issue on one host, quite some time ago. Vince

Bug#884423: web interface to git repo not working

Package: cron Severity: minor Problem statement: If I follow one of the links in the web interface to the git repo, e.g. https://anonscm.debian.org/gitweb/?p=pkg-cron/pkg-cron.git;a=commit;h=3a0e758b85d03dd2e8fca02d95f67dce1dcbc47f I get this error Bad object id: and the URL displayed in the

Bug#882766: Proposal: reinstate automated device selection, blacklisting d-i?

It would be good to make this change. Is there some reason to not include a build stamp in the installer initrd at, say, /build-stamp? This would be the same string as in boot-screens/f1.txt (e.g. 20170615+deb9u2). Regards --

Bug#879792: nvidia-detect: misses nvidia tesla p100 (GP100GL)

On Thu, Oct 26, 2017 at 11:47:00AM +0100, Luca Boccassi wrote: > > Hi, > > Is the Tesla series compatible with the Geforce series drivers that we > package? > > They are sorted separately on Nvidia's website at least: > > http://www.nvidia.co.uk/download/driverResults.aspx/124885/en-uk > > But

Bug#879792: nvidia-detect: misses nvidia tesla p100 (GP100GL)

Package: nvidia-detect Version: 375.82-6 Severity: normal Tags: patch thanks Also found in 375.82-1~deb9u1 375.82-4~bpo9+1 384.90-1 I have a system with a nvidia tesla p100 GPU: # lspci -v -s 04:00 04:00.0 3D controller: NVIDIA Corporation GP100GL (rev a1) Subsystem: NVIDIA Corporation

Bug#676472: cups: please suggest a compatible inet server (for lpd support)

> As of 2017, I tend to think that lpd support should disappear for Buster. Iff > we'd want to keep it, having cups-bsd get a > Suggests: inetutils-inetd | inet-superserver, update-inetd > _could_ make sense. > > I'm not going to investigate more than that; so if someone wants that in >

Bug#872890: [patch] initialise loop variable in rescan-scsi-bus.sh

Package: sg3-utils Version: 1.42-2 Severity: normal Tags: patch thanks Using rescan-scsi-bus.sh is scary enough at the best of times, but when it prints things like this it's even scarier /usr/bin/rescan-scsi-bus.sh: line 257: test: !=: unary operator expected That line reads 257 if

Bug#872524: git-buildpackage: documenting import from upstream git

Package: git-buildpackage Version: 0.8.18 Severity: minor Tags: patch thanks Hi, I was looking in the manual for information on starting from scratch with an upstream git and found it a little terse for newbies like me. Please would you consider applying the attached patches. The published

Bug#870574: lowmem: naming of main-menu.d item

Package: lowmem Version: 1.45 Severity: normal Poking around an install environment I looked in /lib/main-menu.d and found these files: 10rescue 5lowmem Then I found the original commit message: commit b9741a97a349f9ed4364b3411c3ab8afc590e385 Author: Joey Hess

Bug#870448: hw-detect - stop using modprobe -l

On Wed, Aug 02, 2017 at 07:58:05PM +0100, Ben Hutchings wrote: > > But this still prints error messages for missing modules. I think the > function should be implemented as: > > is_available () { > modprobe -qn "$1" > } > I agreee, much better!

Bug#870448: hw-detect - stop using modprobe -l

Package: hw-detect Version: 1.124 Severity: normal Tags: patch I keep seeing this in installer logs, back to jessie. Aug 2 01:52:11 main-menu[193]: (process:224): modprobe: invalid option -- 'l' I rated this normal rather than minor because the way it is working now the is_available()

Bug#759553: suggested patch

Tags: patch Thanks Can this be fixed please? I wasted an hour tracking this down while trying to resolve another issue. --- lib/auto-lvm.sh.org 2017-08-02 10:24:35.773321165 +1000 +++ lib/auto-lvm.sh 2017-08-02 10:24:49.709392154 +1000 @@ -302,7 +302,7 @@ defvgname="$RET"

Bug#820983: ok to close

this bug can be closed since the omission was addressed not long after. samba (2:4.2.10+dfsg-0+deb8u3) jessie-security; urgency=high ... [ Andrew Bartlett ] * Add back better NEWS item for 2:4.2.10+dfsg-0+deb8u1 ... -- Salvatore Bonaccorso Wed, 01 Jun 2016 17:05:31

Bug#866179: patch

Tags: patch thanks A bit of trawling turned up the d-d-a posts and the wiki pages. Please consider this for inclusion. Index: whats-new.dbk === --- whats-new.dbk (revision 11691) +++ whats-new.dbk (working copy) @@

Bug#866179: [stretch] old versions of gcc not available

Package: release-notes Severity: wishlist Hi it appears that, in contrast to previous releases, stretch does not come with the gcc available in the previous release. I think this should be noted in the release notes along with a pointer to any discussion about the reason for this. Can anyone

Bug#864857: [patch] avoid blhc warning about -fPIE

+1,20 @@ +Last Updated: 2017-06-16 +Author: Vincent McIntyre <vincent.mcint...@csiro.au> +Forwarded: no +Description: Avoid warning about -fPIE from blhc + +This is probably not entirely necessary since all modules are +compiled with -fPIE, but it avoids a warning. +Index: autofs-5.1.2/dae

Bug#864853: [patch] fix lintian warning about man/autofs.8

index 000..386015d --- /dev/null +++ b/debian/patches/fix-whatis.patch @@ -0,0 +1,18 @@ +Author: Vincent McIntyre <vincent.mcint...@csiro.au> +Forwarded: no +Description: Reinstate - separator in NAME section, to satisfy lintian + +Upstream presumably dropped reference to the init script +beca

Bug#864852: [patch] fix missing dependency on lsb-base

Package: autofs Severity: normal Version: 5.1.2-2 Tags: patch thanks Lintian marks this as an error, may as well fix it. Signed-off-by: mci156 --- debian/control | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/control b/debian/control

Bug#864849: [patch] fix watch file

Package: autofs Severity: normal Version: 5.1.2 Tags: patch thanks mate This patch makes uscan do something useful again. --- a/debian/watch +++ b/debian/watch @@ -1,2 +1,2 @@ version=3

Bug#864476: [patch] lintian appeasement

Package: multipath-tools Version: 0.6.4-5 Severity: wishlist Tags: patch This series quells some lintian warnings. I hope it is helpful. If not, just wontfix. Vincent McIntyre (4): Add more shlib-symlink overrides, following previous example Silence bogus warning about undefined macro

Bug#814363: update to uscan file

tags: patch thanks mate I noticed a new upstream version (0.7.1) so I thought I would try to make uscan notice as well. This seems to work reliably: --- debian/watch.orig 2017-06-06 16:48:45.205127553 +1000 +++ debian/watch2017-06-06 17:18:16.788922857 +1000 @@ -1,3 +1,4 @@ # format

Bug#864192: multipath-tools: Typo in README.Debian

Source: multipath-tools Version: Typo in README.Debian Severity: minor Bug 8217322 does not exist. @@ -5,7 +5,7 @@ I see a lot of "io_setup failed" message using the directio checker -Debian Bug #8217322 +Debian Bug #827322

Bug#751993: upload?

Hi there have been a couple of stable point releases (8.7,8.8) since this and #799781 were tagged as pending, but they haven't made it in. Could you check what's up please? Vince

Bug#767946: updated patch

Tags: patch Thanks The attached version of lshw-common.patch avoids those warnings. Kind regards Vince Added paths to look for device idsIndex: lshw-02.14/src/core/pci.cc === Index: lshw-02.18/lshw-B.02.18/src/core/pci.cc

Bug#860970: release-notes: MariaDB vs MySQL section 2.2.3 needs clarifying on how to perform the upgrade

Hi Paul If I understand correctly, you are suggesting this change: MariaDB is now the default MySQL variant in Debian, at version 10.1. The Stretch release introduces a new mechanism for switching the default variant, using metapackages created from the mysql-defaults source package.

Bug#855656: release-notes: update on mysql/mariadb for stretch

On Sun, Feb 26, 2017 at 05:58:08PM +0100, Baptiste Jammet wrote: > > I add an for the note about binary data file formats > not backwards compatible, and choose to add default-mysql-* next > to virtual-mysql-*. > Updated patch attached, for clarity. Good idea. I added a 'for example' to the

Bug#855656: release-notes: update on mysql/mariadb for stretch

On Tue, Feb 21, 2017 at 09:56:44AM +0100, Baptiste Jammet wrote: > Hello, > > Le 21/02/2017 01:09, Vincent McIntyre a écrit : > > >this is a start on the notes needed regarding mysql/mariadb. > >[...] > >Comments welcome. > Thanks for

Bug#855656: release-notes: update on mysql/mariadb for stretch

Package: release-notes Severity: normal Tags: patch Hello this is a start on the notes needed regarding mysql/mariadb. This has been developed in consultation with the mysql package maintainers. It is probably missing a few pieces that should go in other chapters, such as upgrading.dbk.

Bug#843953: multipath-tools: LVM on internal disks + multipath-toosl = no multipaths

On Fri, Nov 11, 2016 at 04:06:44PM +0530, Ritesh Raj Sarraf wrote: > > Related notes: > > > >    On some reboots the system log shows multipath timing out. Below is > > 'sdd'. > >    The timeout occurs 33 seconds after the disk was attached. > >    I was unable to determine the cause of this or

Bug#843953: multipath-tools: LVM on internal disks + multipath-toosl = no multipaths

Package: multipath-tools Version: 0.5.0-6+deb8u2 Severity: important * What led up to the situation? Upgrade working wheezy system to jessie Apply patch to fix multipath segfault, see #751993 The system boots off an internal physical disk That disk has one / partition and an LVM

Bug#799781: found the upstream commit

On Sun, 27 Sep 2015 20:04:06 +0530, Ritesh Raj Sarraf wrote: > I have a problem here. > > The fix, that you mentioned for the Shared Lock, does not seem to be > committed upstream. Neither master, nor Hannes's suse-fixes branch. It is there, please see

Bug#751993: another instance

On Wed, Nov 09, 2016 at 04:27:40PM +0530, Ritesh Raj Sarraf wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On Wed, 2016-11-09 at 09:15 +1100, Vincent McIntyre wrote: > > This is a problem because I need to blacklist DELL, > > multipath -l -v 3 gives me the

Bug#610282: partman-lvm/confirm boolean true does not suppress "Before the Logical Volume ..."

(we were discussing having a branch of manual for each stable release) This appears to have happened - thanks Samuel! https://anonscm.debian.org/viewvc/d-i/branches/manual/jessie/ I think it would be worth mentioning the existence of this in the trunk README - suggested patch below. Please let

Bug#838948: [patch] preseed appendix of d-i manual: use_autoconfig

Package: installation-guide Severity: minor Tags: d-i patch thanks (resending as a bug, my post to -boot didn't elicit any replies) For some years the disable_autoconfig preseed has been shown in the appendix on preseeding. However setting that just sets use_autoconfig appropriately. Yet

Bug#838946: [patch] preseed appendix of d-i manual: use_autoconfig

Package: debian-installer-manual Version: Head Severity: minor Tags: d-i patch thanks (resending as a bug, my post to -boot didn't elicit any replies) For some years the disable_autoconfig preseed has been shown in the appendix on preseeding. However setting that just sets use_autoconfig

Bug#837123: [anna] segfault in wheezy installer

On Wed, Sep 14, 2016 at 08:59:52AM +0200, Aurelien Jarno wrote: > > > More details. > > The target system is pxe booted and next-server takes it to a (debian) > > system running tftpd-hpa. The defaults.cfg has lots of boot targets > > but the one I have been testing with is the netboot image, in

Bug#837123: [anna] segfault in wheezy installer

On Wed, Sep 14, 2016 at 09:01:20AM +0200, Aurelien Jarno wrote: > > ... > > warning: Can't read pathname for load map: Input/output error. > > > > warning: Could not load shared library symbols for 4 libraries, e.g. > > /lib/libc.so.6. > > Use the "info sharedlibrary" command to see the complete

Bug#837123: [anna] segfault in wheezy installer

On Wed, Sep 14, 2016 at 09:29:18AM +1000, Vincent McIntyre wrote: > > Also you might want to use the console (alt+f2) to run wget by hand and > > see if the issue happen with all hosts or only some of them. > > I tried to wget pages from a few web sites from the alt+f2 consol

Bug#837123: [anna] segfault in wheezy installer

On Tue, Sep 13, 2016 at 11:03:19PM +0200, Aurelien Jarno wrote: ... > > If all of that makes no difference, what would be the next step? > > What would be interesting would be to try to reproduce the issue in > qemu or virtualbox, with as many things as possible close to your > system. > Just

Bug#775541: tests of new packages

On Mon, Sep 12, 2016 at 02:38:32PM +1000, Vincent McIntyre wrote: A brief note on the client side of things. At step 3, after installing your packages but before tweaking nfs-server.service, the critical chain for the client mount is usr-local.mount +1.145s └─remote-fs-pre.target @7.493s

Bug#775541: tests of new packages

On Fri, Sep 09, 2016 at 10:22:25AM +0200, Andreas Henriksson wrote: > Hello Vincent McIntyre. > > Thanks for your thurough testing and useful feedback. > > Let me start with a disclaimer: I'm not maintaining nfs (and I'm > not even using it myself so my knowledge is very

Bug#837123: [anna] segfault in wheezy installer

On Mon, Sep 12, 2016 at 12:28:55PM +1000, Vincent McIntyre wrote: > > > - make sure all ipv6 related options are disabled > >and no ipv6 DNS entries exist for the target host > >Didn't try it. The failure happens really early, before the >preseed file i

Bug#837123: [anna] segfault in wheezy installer

On Sat, Sep 10, 2016 at 11:30:32AM +1000, Vincent McIntyre wrote: > > You've given me a few things to try out > - tell DHCP to supply different DNS servers (running bind) Makes no difference. These servers are not configured for v6, while the first ones I used were. There

Bug#837123: [anna] segfault in wheezy installer

On Fri, Sep 09, 2016 at 03:59:17PM +0200, Aurelien Jarno wrote: > > I don't talk about the software running on your DNS servers, but > rather how they behave when they get queried. It might depends on > many other things, like if your network has IPv6 or not. > > Note that's only one

Bug#837123: [anna] segfault in wheezy installer

On Fri, Sep 09, 2016 at 11:46:30AM +0200, Aurelien Jarno wrote: > Hi, > > On 2016-09-09 10:27, Vincent McIntyre wrote: > > > > Package: libc6-udeb > > Version: 2.13-38+deb7u10 > > Severity: grave > > Justification: breaks installation entirely > &

Bug#775541: tests of new packages

I found one further issue which is related to #738063. I wanted to limit the exports to supporting version 2 and 3. I first set RPCMOUNTDOPTS="--manage-gids --no-nfs-version 4" as explained in /etc/default/nfs-kernel-server. But I found I also needed add the following to that file:

Bug#775541: tests of new packages

Thanks Andreas for those new packages. I did some testing of the 1.2.8-9.2 packages on a clean jessie install. They are pretty close but I found an issue with NFS exports in one case. I used the attached check.sh script to show the state of various targets as I changed things. The attached

Bug#837123: ([anna] segfault in wheezy installer)

I just realised this went to the libc maintainers; I was expecting it would go to the debian-installer team. This might be an issue in the way libc6-udeb is being used within debian-installer, rather than libc6-udeb itself. I don't know how to figure out if that is the case; if it is the case,

Bug#837123: [anna] segfault in wheezy installer

Package: libc6-udeb Version: 2.13-38+deb7u10 Severity: grave Justification: breaks installation entirely The wheezy installer fails with anna reporting a segfault: ... anna[5033]: DEBUG: retrieving libc6-udeb 2.13-38+deb7u10 anna[5033]: DEBUG: retrieving finish-install 2.41wheezy1 anna[5033]:

Bug#775541: NFS mounts fail at boot after Debian 8.5 upgrade

Hello Paul I read your feedback on this issue with interest. Could you provide a bit more information about the package versions on your system? dpkg -l rpcbind nfs-common nfs-kernel-server systemd Also I think the output of these commands would be helpful systemd-analyze critical-path

Bug#835067: libpam-passwdqc: improvements(?) to password prompting

Package: libpam-passwdqc Version: 1.3.0-1 Severity: minor Tags: patch I noticed some repeated text and somewhat tortured wording in the prompts for new passwords. Please consider the attached patch. It defines a couple of extra text slugs to make the prompt wording more consistent across the

Bug#831985: [patch] fix default for 'prio' in manpage

On Fri, Jul 22, 2016 at 10:20:54PM +0530, Ritesh Raj Sarraf wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Control: tag -1 +pending, fixed-upstream > > > Hello Vincent, > > THank you for your patch and care for ensuring documentation is > intact. > > With today's release of

Bug#831985: Acknowledgement ([patch] fix default for 'prio' in manpage)

I've found a couple of other nits that could be fixed, see attached patch. There was one item I was unsure about so I left it out of the patch. The manual page says the default is reassign_maps = yes but libmultipath/defaults.h says #define DEFAULT_REASSIGN_MAPS0 This gets used like

Bug#831985: [patch] fix default for 'prio' in manpage

Package: multipath-tools Version: 0.6.1-3 Priority: minor I noticed the manpage documents the wrong default for 'prio'. At least, it seems that way from this check: $ grep DEFAULT_PRIO libmultipath/prio.h #define DEFAULT_PRIO "const" #define DEFAULT_PRIO_ARGS "" Now that upstream ditched the

Bug#831875: linux-image-3.16.0-0.bpo.4-amd64: endless "NMI backtrace" loop

Package: src:linux Version: 3.16.7-ckt25-2+deb8u3~bpo70+1 Severity: normal The system is running the wheezy release. After some fibre channel multipathing issues, my system ended up endlessly printing messages like the one below for each of 32 cpus, every 3 sec. However the problem occurs in

Bug#810219: confirmation

We also hit this with Dell Optiplex 7040 desktops % cat /etc/debian_version 8.5 % uname -v #1 SMP Debian 3.16.7-ckt25-2+deb8u2 (2016-06-25) % lspci 00:00.0 Host bridge: Intel Corporation Device 191f (rev 07) 00:01.0 PCI bridge: Intel Corporation Device 1901 (rev 07) 00:02.0 VGA compatible

Bug#821811: samba: badlock patch breaks trust relationship

I can confirm that after downgrading these packages samba samba-common samba-common-bin libwbclient0 smbclient samba-tools to version 2:3.6.6-6+deb7u7 and then upgrading with apt-get -t santiago-wheezy install samba samba-common \ samba-common-bin libwbclient0 smbclient

Bug#823372: winbind: segfault on first login attempt

Package: winbind Version: 2:3.6.6-6+deb7u9 Severity: normal possibly-related bugs: 820981 We have not used winbind in our setup until the badlock patches came along (2:3.6.6-6+deb7u9). We follwed the recommendation in #820981. The environment is MS AD, we are running a "member server" serving a

Bug#784743: updated patch

Tags: patch The perl patching command given by Edmund results in this change: --- debian/patches/linker-specific-changes.orig 2011-11-19 16:45:51.0 +1100 +++ debian/patches/linker-specific-changes 2015-08-03 14:16:16.518331208 +1000 @@ -65,7 +65,7 @@ grtv00.o : $(DRVDIR)/imdef.h

Bug#789604: release-notes: 'halt' behaviour changed without notice

On Thu, Jun 25, 2015 at 11:38:58AM +0100, Justin B Rye wrote: Vincent McIntyre wrote: I'm submitting this patch on the advice of the systemd maintainers. Could this be applied to the jessie release notes? It's good, but I've got a couple of English usage nitpicks: And I'm happy to have

Bug#789652: v2 patch

On Thu, Jun 25, 2015 at 05:51:02PM +0100, Justin B Rye wrote: Vincent McIntyre wrote: Justin B Rye wrote: It's good, but I've got a couple of English usage nitpicks: And I'm happy to have you pick the nits off my contribution :) Would you care to peruse #789652, which is related

Bug#760923: tentative patch

On Wed, Jun 24, 2015 at 09:47:35PM +0200, Marco d'Itri wrote: On Jun 23, Martin Pitt mp...@debian.org wrote: This sounds confusing -- systemd has never changed the behaviour of halt; sysvinit misimplemented halt, so the change is between changing init systems, not upgrading any particular

Bug#789604: release-notes: 'halt' behaviour changed without notice

Package: release-notes Tags: patch thanks Hi, I'm submitting this patch on the advice of the systemd maintainers. Could this be applied to the jessie release notes? I sent a separate patch for the installation-guide, #789652 Cheers Vince Index: issues.dbk

Bug#789604: release-notes: 'halt' behaviour changed without notice

Control: tag 789604 patch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#760923: tentative patch

On Tue, Jun 23, 2015 at 02:24:10AM +0200, Marco d'Itri wrote: On Jun 23, Vincent McIntyre vincent.mcint...@csiro.au wrote: +systemd (221-1) UNRELEASED; urgency=medium This has not changed in 221: even if we really want to document this in NEWS.Debian then the message must not be displayed

Bug#760923: tentative patch

On Tue, Jun 23, 2015 at 09:58:28AM +0200, Martin Pitt wrote: This sounds confusing -- systemd has never changed the behaviour of halt; sysvinit misimplemented halt, so the change is between changing init systems, not upgrading any particular version. How about something like halt

Bug#760923: tentative patch

. +This command halts the machine but no longer turns off the power - +use shutdown -h or poweroff for that. +The old behaviour is regarded as a bug by upstream and won't be changed +in this package so as to maintain compatibility with other Linux distros. + + -- Vincent McIntyre

Bug#760923: tentative patch

Control: tag 760923 patch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

  1   2   3   4   >