Bug#910251:

Alastair, Thanks for the quick update. I see that I upgraded to libpsm2-2 11.2.78-1 on 01 Oct 2018, so the timing fits. Thanks, Ron -- James Ronald Lovell Huntsville, AL, USA

Bug#910251: libopenmpi3 3.1.2-5 Introduces 15s Delay and hfi_wait_for_device Messages

Package: libopenmpi3 Version: 3.1.2-5 Severity: normal Dear Maintainer, I updated Open MPI and libpmix2 on my Sid X86_64 system this afternoon: Open MPI 3.1.2-5 libpmix2 3.0.2-2 My simple MPI tests run to completion and give correct results, but there is an abnormal delay in startup and new

Bug#908799: Confirmation of Fix

New packages libcoarrays-openmpi-dev and libcaf-openmpi-3 2.2.0-3 do resolve the issue on my system. I'm proceeding on the assumption that cafrun(1) (from old package open-coarrays-bin) might never return to Debian, so I'm switching to mpiexec(1) on all my Linux VMs (the others being Fedora

Bug#908799: libcaf-openmpi-3: Package libcaf-openmpi-3 Should Probably Install in lib Subdir

Package: libcaf-openmpi-3 Version: 2.2.0-2 Severity: important Dear Maintainer, I just updated to the new OpenCoarrays packaging on my x86_64 Sid system. While updating my meson.build files, I found that the caf-openmpi.pc pkg-config file installed by package libcoarrays-openmpi-dev assumes the

Bug#908120: gnome-terminal: confirmation of fix

libgtk-3-0_3.24.0-2_amd64 does fix the issue on my system. Great work, guys!

Bug#908120: gnome-terminal: Cursor disappears when changing or moving windows

I just noticed that none of our messages mention that this is an issue only for Wayland GNOME sessions. So starting an Xorg GNOME session is a temporary workaround. -- James Ronald Lovell Huntsville, AL, USA

Bug#908120: gnome-terminal: Cursor disappears when changing or moving window

Yeah, me too. Issue appeared evening of 05 Sep 2018 in Sid after a number of possibly relevant updates: GLib 2.58.0-2 GTK 3.24.0 GNOME Shell 3.30 Wayland libs 1.16.0 Mutter 3.30 -- James Ronald Lovell Huntsville, AL, USA

Bug#900938: blueman: Blueman-manager should not automatically reconnect when manually disconnected

On 06/09/2018 03:12 PM, Ron Murray wrote: > On Fri, 8 Jun 2018 07:48:30 +0200 Christopher Schramm wrote: > > Hi Ron, > > > > there should not be any such auto-connect feature in blueman. You can > > easily confirm that by stopping blueman-applet and check if it sti

Bug#903945: munge startup fails with timeout

package change for my purposes. Thanks again Chris for the very useful reply. Best regards, Ron -- James Ronald Lovell Huntsville, AL, USA

Bug#903945: munge startup fails with timeout

I reinstalled the 4.16 kernel to confirm that munged starts normally under 4.16 with the default systemd timeout. It does. But now I'm no longer able to reproduce the problem when running the 4.17 kernel. I dunno. Has anyone else seen the munged timeout failures? I'll update as I learn more.

Bug#903945: munge startup fails with timeout

. Severity rating "important" is based on Slurm batch system being useless without Munge service. Best regards, Ron - System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-1-amd64 (SMP w/2 CPU cor

Bug#902408: dictd start needs to be ordered after network configuration

, and then everything works as expected. Cheers, Ron diff --git a/debian/dictd.init b/debian/dictd.init index fd9ae2b..65592a6 100644 --- a/debian/dictd.init +++ b/debian/dictd.init @@ -2,8 +2,8 @@ # vim:ts=4:et:sts=4 ### BEGIN INIT INFO # Provides: dictd -# Required-Start:$remote_fs $syslog

Bug#900938: blueman: Blueman-manager should not automatically reconnect when manually disconnected

On Fri, 8 Jun 2018 07:48:30 +0200 Christopher Schramm wrote: > Hi Ron, > > there should not be any such auto-connect feature in blueman. You can > easily confirm that by stopping blueman-applet and check if it still > happens (you can use bluetoothctl to disconnect if that's nec

Bug#900938: One day I'll learn to proofread ...

After "and then right-clicking on the appropriate device.", I should have written "then select 'Disconnect'". Apologies for the error. .Ron -- Ron Murray PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761

Bug#900938: blueman: Blueman-manager should not automatically reconnect when manually disconnected

Package: blueman Version: 2.0.5-1+b1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, I have a set of Bluetooth headphones which I use on multiple computers. I also have a Bluetooth keyboard attached to my Linux box. If I have the headphones connected to the

Bug#898690: CELT PLC broken

1.3 release if nothing extra shakes out of it. Thanks for digging into this and reporting it. Cheers, Ron

Bug#897065: make: please use implicit rules for phony targets

ter, but having seen the discussion on IRC (since it was reported here) - it seems pretty obvious to me that your makefile was just buggy and this is not a bug in make, so IMO it can be closed here. HTH, Ron

Bug#895827: Confirm Fix in Open MPI 3.0.1-5 Build

The issue is resolved for my system by the 3.0.1-5 build. I tested interactively and as part of a Slurm batch job where I let Slurm provide the task count to mpiexec(1). (No -np option.) I also confirmed that installation of libpmix2 is not required. Great work! -- James Ronald Lovell

Bug#895327: Confirm Fix in Open MPI 3.0.1-5 Build

The issue is resolved for my system by the 3.0.1-5 build. I tested interactively and as part of a Slurm batch job where I let Slurm provide the task count to mpiexec(1). (No -np option.) I also confirmed that installation of libpmix2 is not required. Great work! -- James Ronald Lovell

Bug#895827: libopenmpi-dev: broken symlink: libpmix.so, and not installed libpmix.so.2.1.1

I've had the same issue since the upgrade to Open MPI 3.0.1. ompi_info(1) also shows the problem. The libpmix.so.2.1.11 library can be provided by the libpmix2 package. I just updated to libpmix-dev and libpmix2 2.1.1~rc1-2 with the fix for Bug 895772. The reference to libpmix.so.2 gets resolved

Bug#894158: libogg: new upstream release 1.3.3

On Tue, Mar 27, 2018 at 11:09:51AM +0100, Simon McVittie wrote: > On Tue, 27 Mar 2018 at 18:25:59 +1030, Ron wrote: > > On Mon, Mar 26, 2018 at 10:55:04PM +0100, Simon McVittie wrote: > > > lose the -dbg package, > > > > This would mean people wanting a backpor

Bug#894158: libogg: new upstream release 1.3.3

On Mon, Mar 26, 2018 at 10:55:04PM +0100, Simon McVittie wrote: > On Tue, 27 Mar 2018 at 07:45:27 +1030, Ron wrote: > > There's actually some more interesting fixes after the 1.3.3 tag, so I > > should probably nudge upstream toward a 1.3.4 tag sometime soon and pull > > in

Bug#894158: libogg: new upstream release 1.3.3

ly get a poke directly from *upstream* if there is something important in these which we are missing - and what is in git is usually more interesting than what is in a tarball on the download site. But thanks for the poke to review this again and note the current status where people who aren't following git might see it. Cheers, Ron

Bug#860538: wavesurfer: Text and window sizes are too small for high-resolution displays

ply that to the libtk8.6 packages we are shipping? Leonardo, could you confirm if changing that does indeed fix this for you with the wavesurfer 1.8.8p5-1 package I've just pushed out and tk8.6? Cheers, Ron

Bug#893209: wavesurfer: depends on deprecated Tcl/Tk 8.5

ch are significant for this. Thanks for testing that, there's a package on its way to incoming which should let you proceed with dropping tk 8.5. Cheers, Ron

Bug#893175: EDE: Can't re-open a project after closing and re-opening emacs

Package: emacs25-common Version: 25.2+1-6 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was

Bug#891489: gcc-8: attribute no_sanitize does not accept multiple options as documented

error: wrong number of arguments specified for ‘no_sanitize’ attribute f () { /* Do something. */; } ^ It would be really nice if that did work as documented, to avoid having to special case this in user code even more than we already do. Cheers, Ron

Bug#890844: Fwd: python3-keyrings.alt 2.2-2 module.__file__ is None, causing regrtest.py to fail

-- Forwarded message -- From: Ron Lovell <ron163...@gmail.com> Date: Mon, Feb 19, 2018 at 8:45 PM Subject: python3-keyrings.alt 2.2-2 module.__file__ is None, causing regrtest.py to fail To: 890...@bugs.debian.org, 890...@bugs.debian.org If I'm following correctly, it a

Bug#890621: python3-keyrings.alt 2.2-2 module.__file__ is None, causing regrtest.py to fail

beta 1. But to simplify and to handle future cases, I think you will want to modify the 3.7 regression tests setup.py as well. Thanks all for the great work on this. Ron -- James Ronald Lovell <ron163...@gmail.com> Huntsville, AL, USA

Bug#890621: python3-keyrings.alt 2.2-2 module.__file__ is None, causing regrtest.py to fail

Package: python3-keyrings.alt Version: 2.2-2 Severity: important Dear Maintainer, When package 'keyrings' from python3-keyrings.alt is imported under python3.6, the module object has a __file__ attribute with a value None. This causes early failure of the Python 3.6 regression tests from

Bug#820770: Bug#889640: lintian: init.d-script-possible-missing-stop misfire on rcS scripts

On Tue, Feb 06, 2018 at 05:50:28PM +1030, Ron wrote: > On Tue, Feb 06, 2018 at 03:32:55AM +0530, Chris Lamb wrote: > > tags 820770 + moreinfo > > thanks > > > > > > Hi Ron and Felipe, > > > > Hm, are #820770 and #889640 the same issue? If so, we sho

Bug#889640: lintian: init.d-script-possible-missing-stop misfire on rcS scripts

On Tue, Feb 06, 2018 at 03:32:55AM +0530, Chris Lamb wrote: > tags 820770 + moreinfo > thanks > > > Hi Ron and Felipe, > > Hm, are #820770 and #889640 the same issue? If so, we should either > close them both or reopen both of them. Yes, that was exactly my line of t

Bug#889640: lintian: init.d-script-possible-missing-stop misfire on rcS scripts

On Mon, Feb 05, 2018 at 08:48:57PM +0530, Chris Lamb wrote: > tags 889640 + moreinfo > thanks > > Hi Ron, > > > # Default-Start: S > > # Default-Stop: 0 6 > > > > Will cause lintian to complain about it not being stopped in runlevel 1,

Bug#869547: lintian: udev-rule-missing-subsystem false positive

On Mon, Feb 05, 2018 at 09:06:35PM +0530, Chris Lamb wrote: > forcemerge 869547 889639 > thanks > > Hi Ron, > > This appears to be same issue as #869547 ("udev-rule-missing-subsystem > false-positive when rules file uses a GOTO"). Ah, indeed. Sorry about

Bug#889638: lintian: please downgrade build-depends-on-obsolete-package dh-systemd to warning

ffending package this would check for completely, rather than simply deprecating it. Is there something in between that still which we need to cater for? Cheers. Ron

Bug#889640: lintian: init.d-script-possible-missing-stop misfire on rcS scripts

in 2-5, but that doesn't really apply for things which can be shut down in an orderly way but shouldn't be just because you're switching to or entering runlevel 1. Cheers, Ron

Bug#889639: lintian: udev-rule-missing-subsystem false positive

uot;, GOTO="bb_end" ... LABEL="bb_end" because all the rules in it are inapplicable for non-USB devices. Cheers, Ron

Bug#889638: lintian: please downgrade build-depends-on-obsolete-package dh-systemd to warning

cle. Especially since all bets are off in later dh compat versions where the systemd support has changed completely again - it would be nice to not make it harder than needed for backports, and have an easy canary for how many packages still need the older systemd support for that. Cheers, Ron

Bug#888050: Fwd: [Pkg-utopia-maintainers] Bug#888050: network-manager: Debian Unstable network-manager 1.10.2-3 does not complete processing

-- Forwarded message -- From: Ron Lovell <ron163...@gmail.com> Date: Mon, Jan 22, 2018 at 5:11 PM Subject: Re: [Pkg-utopia-maintainers] Bug#888050: network-manager: Debian Unstable network-manager 1.10.2-3 does not complete processing To: Michael Biebl <bi...@debian.o

Bug#888050: network-manager: Debian Unstable network-manager 1.10.2-3 does not complete processing

Package: network-manager Version: 1.10.2-3 Severity: important Dear Maintainer, The update of network-manager fails to complete. I noticed before applying the update that several packages would be removed, including libnm-gtk0, libnm-utils2, and libnm-glib4. The dependencies appeared to revolve

Bug#887755: open-vm-tools-desktop: Debian Unstable per-session user-owned vmtoolsd segfaults afer upgrade to 2:10.2.0-1

Package: open-vm-tools-desktop Version: 2:10.2.0-1 Severity: important Dear Maintainer, After upgrade to open-vm-tools[-desktop] 2:10.2.0-1 in Sid, the per-session user-owned vmtoolsd process segfaults in libgdk while logging into a Wayland GNOME session. The problem does not occur for an Xorg

Bug#870608: CVE-2017-11548

op here today). Below is what I'm currently seeing on Stretch when running the example given. Cheers, Ron $ gdb mpg321 (gdb) r libao_1.2.0_memory_corruption.mp3 Starting program: /usr/bin/mpg321 libao_1.2.0_memory_corruption.mp3 [Thread debugging using libthread_db enabled] Using host

Bug#883909: ifupdown: networking.service is sequenced too late (aka too early during shutdown)

, but that was two that stood out while I looked to see if this was already reported. Thanks for picking up the maintenance of this package! Best, Ron

Bug#882825: RM: libmp3splt -- ROM; manual decruft needed

- and there's nothing else depending on the src:libmp3splt package, it really is old cruft we should drop now. Cheers, Ron

Bug#882455: pcmanfm: hangs system when startx is used to initiate joes window manager

Package: pcmanfm Version: 1.2.5-3 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome

Bug#880308: CLA Diet is the end of obesity sR6X

I have not received this product On Nov 10, 2017 1:52 PM, "CLA Diet" wrote: > > > > > >

Bug#878956: Some corrections

logins from :0, but there weren’t, apparently because of this bug. (I am not usually in the habit of repeatedly rebooting a machine just to watch it come up). Thanks, .Ron -- Ron Murray <r...@rjmx.net> PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761

Bug#878956: sddm doesn't update utmp or wtmp

Package: sddm Version: 0.15.0-1 Severity: normal Dear Maintainer, sddm doesn't seem to update /run/utmp or /var/log/wtmp. Logging in with it, the 'w' command gives me: > ron@khufu:~$ w > 21:09:47 up 36 min, 0 users, load average: 0.10, 0.08, 0.20 > USER TTY FROM

Bug#876780: libvorbis: CVE-2017-14160

the current distro packages are based on) vorbis_psy.c isn't one of the exported files. So it's there in git, but it's not in the Debian source, and I'd be surprised if anyone is building binaries with it enabled anywhere. Cheers, Ron

Bug#557765: libfishsound1-dev: The -dev package should be named libfishsound-dev

dn't actually CC the control server with that. So if you just want to get this off the triage radar, that seems like the better option to me - unless I'm missing something like there being an actual ABI change about to happen. Cheers, Ron

Bug#846173: libvirt-daemon: Fails to locate existing usb device

you get your notification event too"). Please do keep me in the CC for any discussion of this, I am very interested in us ultimately Getting This Right as a supported thing. I'd planned to open some discussion on improving this a while ago (http://bitbabbler.org/blog.html#vm_hotplug), but this bug has now made it a more urgent thing to deal with than it previously was. Cheers, Ron

Bug#863532: Bug#867813: xserver-xorg-input-wacom: Delay between boot and login present on Stretch, but not Jessie.

Hi Charles, You're probably being hit by this bug: https://bugs.debian.org/863532 Where a change in Xorg means that timeout values which used to be interpreted as microseconds are now being taken as milliseconds ... so things are waiting 1000x as long as they should. The tablet devices aren't

Bug#856294: Adopting mp3splt

will be automatically closed now. Cheers, Ron

Bug#854988: wacom: On screen rotate touch input orientation is correct but stylus input is not

s might fix this for you - but my first guess would be that it probably doesn't. So it would be good to know if we really can close this, or if it's an issue that upstream still isn't aware of yet. Cheers, Ron

Bug#863532: xf86-input-wacom: Serial device detection takes over 4 minutes

bb754f4 is newer than the latest xorg upload, it's unlikely to already be included, so rather than close this one, I'm reassigning it to the xorg maintainers. Cheers, Ron

Bug#865471: Correction to Bug Report

. :^) * Ron

Bug#865471: libopenmpi2: Missing Symlinks to Open MPI Libraries

Package: libopenmpi2 Version: 2.1.1-4 Severity: important Tags: newcomer Dear Maintainer, After upgrade to libopenmpi2_2.1.1-4_amd64, libopenmpi-dev_2.1.1-4_amd64 etc. my programs failed to compile because the compiler and linker (using mpicc and mpifort provided by libopenmpi-dev) could not

Bug#852582: bit-babbler: Update udevadm path

On Tue, Jun 20, 2017 at 06:10:05PM +0200, Michael Biebl wrote: > Hi Ron > > Am 20.06.2017 um 17:12 schrieb Ron: > > On Tue, Jun 20, 2017 at 02:48:02PM +0200, Michael Biebl wrote: > > >> If you are worried about backports: /bin/udevadm is already available in &g

Bug#852582: bit-babbler: Update udevadm path

elling people they'll need to hand hack the path themselves ... ... and then those people will say "why don't you just search for it if you know that it moved?" ... Which seems like a reasonable question to not make them ask :) Users shouldn't need to be on the pointy end of fallout from letting this change propagate down the chain of who needs to deal with it. Cheers, Ron

Bug#863402: isc-dhcp-client: fails to configure rfc3442 classless routes on kFreeBSD

as two arguments. So either I'm tired and missing something, or route does some 'interesting' parsing of its command line arguments. We might want to drop the quotes around those, or pass that as in a slightly different way. Cheers, Ron

Bug#861298: Location of sample ogg file

On Fri, May 19, 2017 at 10:04:20PM +0200, Petter Reinholdtsen wrote: > > [Georges Racinet] > > I don't really have insight on the best place to put a sample ogg file ; > > in the meanwhile, that one is now in python-pygame-doc, and the attached > > patch fixes the FTBFS for me. Hoping this

Bug#861298: oggvideotools: FTBFS: can not open file for reading

t would be expected rather than that it just doesn't completely explode in flames trying. And won't need to B-D on odd packages just for a data file in them. Cheers, Ron

Bug#856429: open-vm-tools: vgauth.service Unit File is Missing VGAuthService Option -s

Package: open-vm-tools Version: 2:10.1.5-5055683-1 Severity: normal Tags: newcomer Dear Maintainer, * What led up to the situation? After a recent update added the vgauth.service unit file, I checked the status of vgauthd.service. While it apparently starts, I noticed there

Bug#856082: libao: Please drop the (build-)dependency against esound

l have an easy path through unstable if anything urgent does need updating in this - but you can put this one on your easy list for the Buster cycle. Cheers, Ron

Bug#851612: CVE-2017-0381

On Mon, Feb 06, 2017 at 08:45:01PM +0100, Julien Cristau wrote: > On Tue, Jan 31, 2017 at 15:32:13 +1030, Ron wrote: > > > I've CC'd -release, to see what they'd prefer we do for Jessie. > > It might be that the best option here is to just put something later > >

Bug#771441: tftpd: don't use AI_ADDRCONFIG to resolve addresses to bind(2)

On Sat, Feb 04, 2017 at 11:28:08PM +0100, Uwe Kleine-König wrote: > On Sat, Feb 04, 2017 at 03:46:46PM +1030, Ron wrote: > > > [...] > > That would seem to be a pretty good summation of how we're failing to > > converge here ... > > I mixed too many things that IMHO

Bug#771441: tftpd-hpa fails to start properly if network is unavailable

pport was actually added. But that predates my involvement here, so I can't say for sure. That said, it also doesn't seem entirely unreasonable for anyone configuring a service like this to know that 0.0.0.0 is an IPv4 address ... which might be related to how it got overlooked ... > If Ron will

Bug#771441: [syslinux] Bug#771441: [PATCH tftpd-hpa] tftpd: don't use AI_CANONNAME and AI_ADDRCONFIG to resolve addresses for bind

On Thu, Feb 02, 2017 at 02:22:47PM +0100, Uwe Kleine-König wrote: > On Thu, Feb 02, 2017 at 04:08:49PM +1030, Ron via Syslinux wrote: > > > The use of AI_PASSIVE here is a placebo. That flag has no effect unless > > address was NULL, and if that was true, neither of th

Bug#771441: [PATCH tftpd-hpa] tftpd: don't use AI_CANONNAME and AI_ADDRCONFIG to resolve addresses for bind

a Good Thing in this particular case than just "Dropping that flag hides a real bug in NetworkManager". Because it could hide or introduce real problems in other cases too, and if the bug in NM is fixed, then the only reason I'm so far aware of for you proposing this patch (based on the discussion on #d-d) also goes away too ... Assuming that at some point the NM bug will be fixed, why would we still want to make this change in this code? Cheers, Ron

Bug#852582: bit-babbler: Update udevadm path

ates for Stretch at this stage, but I'll get something in for the next release after that. Cheers, Ron

Bug#851612: CVE-2017-0381

readable memory. > > > > So while the bug definitely needed to be fixed -- and was fixed back in > > July -- we don't consider it to be a severe security issue. If you > > disagree with our analysis, could you point out what we missed? > > Apologies for the long de

Bug#692754: how to get the username in the plugin?

On Thu, Jan 05, 2017 at 10:10:13AM +0100, Johannes Berg wrote: > On Thu, 2017-01-05 at 13:21 +1030, Ron wrote: > > > > Or worst case, we could make one, and let people do something like: > > > > > >  antispam_log_prefix = %u > > Interesting, yes, that woul

Bug#692754: how to get the username in the plugin?

On Thu, Jan 05, 2017 at 12:47:07PM +1030, Ron wrote: > On Thu, Jan 05, 2017 at 08:34:04AM +1100, martin f krafft wrote: > > also sprach Johannes Berg <johan...@sipsolutions.net> [2017-01-05 01:11 > > +1100]: > > > I'm not even sure how to get the username? Is it

Bug#692754: how to get the username in the plugin?

logging to the same place ... But all of this kind of sets my XY problem overkill alarm off in a variety of ways, so I think we ought to actually start at the top: Martin, what _actual_ problem did you have to make you want this? That might be something we can (also?) fix better and simpler? Ron

Bug#838172: Apparently fixed

I've just checked, and the problem doesn't happen here any longer either (using xfce4). Thanks, .Ron -- Ron Murray <r...@rjmx.net> PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761 signature.asc Description: OpenPGP digital signature

Bug#841294: Overrule maitainer of "global" to package a new upstream version

On Fri, Dec 09, 2016 at 04:00:04PM -0500, Sam Hartman wrote: > > First, upgrading to new upstream is presumed good, not always good. > My concern with Ron's position is mostly that he wants the people > requesting a new upstream to justify that rather than wanting the htags > users to justify

Bug#841294: Overrule maitainer of "global" to package a new upstream version

t package in 1999, you can grab it from the Vcs-Git URL in the sid package. I'm not going to go Full Bruce and rage delete it, but eventually I should decruft alioth and remove it from there, so if you want it you should probably clone it somewhere that works for you. Good luck! Ron

Bug#841294: Overrule maitainer of "global" to package a new upstream version

On Fri, Dec 09, 2016 at 05:13:48PM +0100, Didier 'OdyX' Raboud wrote: > > What I see as fundamental difference here was your use of #196762 as a single > point of contact for the problem you were facing with groff 1.19, in which > you > explained, commented and followed up on what the problem

Bug#841294: Overrule maitainer of "global" to package a new upstream version

On Fri, Dec 09, 2016 at 11:58:02AM +0100, Didier 'OdyX' Raboud wrote: > Le vendredi, 9 décembre 2016, 04.55:20 h CET Ron a écrit : > > > If you haven't yet, I urge you to use our standard interface to report > > > such > > > bugs; please make sure issues like this on

Bug#841294: Overrule maitainer of "global" to package a new upstream version

On Thu, Dec 08, 2016 at 06:24:32PM +0100, Didier 'OdyX' Raboud wrote: > Le jeudi, 8 décembre 2016, 18.14:12 h CET Tollef Fog Heen a écrit : > > Using open like in the code snippet above is pretty much inexcusable in > > this day and age. > > Fair enough, thanks for the

Bug#841294: Overrule maitainer of "global" to package a new upstream version

feel like goldilocks, first I'm bad because I didn't respond enough, now I'm bad because I respond too much. But apparently, I should have actually said just a little more in this one too, to explain to you how perl works :) So I'll do that now! > Le jeudi, 8 décembre 2016, 23.32:44 h CET

Bug#841294: Overrule maitainer of "global" to package a new upstream version

On Thu, Dec 08, 2016 at 03:41:14PM +0100, Vincent Bernat wrote: > ❦ 9 décembre 2016 00:32 +1030, Ron <r...@debian.org> : > > > How much am I supposed to hound you when you give a non-answer? > > Maybe assume good faith and tell me that the answer doesn't fit yo

Bug#841294: Overrule maitainer of "global" to package a new upstream version

On Thu, Dec 08, 2016 at 02:39:44PM +0100, Vincent Bernat wrote: > ❦ 8 décembre 2016 23:32 +1030, Ron <r...@debian.org> : > > > One is whatever it is that the third-party ggtags wrapper needs, which > > aiui is what Vincent and Punit are most annoyed about. But I don't &

Bug#841294: Overrule maitainer of "global" to package a new upstream version

On Mon, Dec 05, 2016 at 10:13:05PM +0100, Philip Hands wrote: > Ron <r...@debian.org> writes: > > > I'm not insisting that's what we should do. But it's certainly an > > option, and it dodges the bullet of having to say "Sucks to be you" > > without

Bug#841294: Overrule maitainer of "global" to package a new upstream version

Hi Sam, On Wed, Nov 30, 2016 at 11:39:08AM -0500, Sam Hartman wrote: > >>>>> "Ron" == Ron <r...@debian.org> writes: > > Ron> Hi OdyX, > > Ron> On Wed, Nov 16, 2016 at 03:23:47PM +0100, Didier 'OdyX' Raboud wrote: > >> Hi

Bug#845441: tftpd-hpa tries to start before filesystems are mounted and aborts

y run after all other units - so I'm going to guess you're doing something 'funny' and/or wrong with where and/or how you're mounting the tftp root you want to use ... I think you're going to need to tell us a bit more about that before we can know what's really going on here. Cheers, Ron

Bug#841294: Overrule maitainer of "global" to package a new upstream version

satisfying or technically astute rationale, if that's all it boils down to. I'd like to have something a bit more substantial and fair than that to offer the people who'd get burned without notice by this. Cheers, Ron

Bug#756367: global chokes/segfaults while parsing drupal 7

do with the actual 'source' in this case, it's hitting a limit of the generated flex scanner. Could you try this again after regenerating that with recent flex? Ron

Bug#826232: Please update to new upstream version

On Tue, Nov 15, 2016 at 11:16:41PM +0100, Andrey Gursky wrote: > Ron, > > > This is done now. Thanks for your patience. > > thanks! The 1.2.2 release hasn't been yet officially published by > upstream (only tagged in git), but it is already available in Debian! >

Bug#844356: gtags chokes on symlink loops

On Tue, Nov 15, 2016 at 06:45:12PM +, Wookey wrote: > On 2016-11-16 04:57 +1030, Ron wrote: > > > > What are you actually building that source with? > > I actually inherited this kernel tree (on a machine that needs a > patched kernel). But I expect it's built with

Bug#841294: Overrule maintainer of "global" to package a new upstream version

ould be fixed in sid now though. Good bug reports are the foundation for getting things fixed, so thanks for setting a good example there. Cheers, Ron

Bug#844356: gtags chokes on symlink loops

really a benefit to someone, but in this case, it looks like you've got a bug in your build scripts that other things will choke on too, and the easy 'fix' for that is something you probably ought to be doing on codebases this size anyway, if you're actually using it on them. Cheers, Ron

Bug#844330: global: Emacs-related error on package install "ERROR: global is broken"

em for people using this, it will need a patch written still one way or the other. Cheers, Ron

Bug#841294: Overrule maintainer of "global" to package a new upstream version

On Tue, Nov 08, 2016 at 04:56:40PM +, Ian Jackson wrote: > Ian Jackson writes ("Re: Bug#841294: Overrule maintainer of "global" to > package a new upstream version"): > > I made this timeline to show how Ron thinks it is appropriate to deal > > wi

Bug#841294: Overrule maintainer of "global" to package a new upstream version

On Tue, Nov 08, 2016 at 02:52:29PM +, Ian Jackson wrote: > Ron writes ("Bug#841294: Overrule maintainer of "global" to package a new > upstream version"): > > I think you missed the bit about "comprehending the problem and building > > consensus o

Bug#841294: Overrule maintainer of "global" to package a new upstream version

On Mon, Nov 07, 2016 at 12:09:21PM -0800, Nikolaus Rath wrote: > On Nov 07 2016, Ron <r...@debian.org> wrote: > > > I've taken the time to repeat this all again now, because regardless > > of how it got here, I actually have some faith in the new face of the > &

Bug#841294: Overrule maintainer of "global" to package a new upstream version

On Sun, Nov 06, 2016 at 05:09:56PM -0800, Nikolaus Rath wrote: > On Nov 06 2016, Ron <r...@debian.org> wrote: > > On Thu, Nov 03, 2016 at 09:20:30AM +0100, Philip Hands wrote: > >> Ron <r...@debian.org> writes: > >> > > >> > I can

Bug#835380: This bug can probably be closed

value from efibootmgr is tested, as I noted in the original bug report. .Ron -- Ron Murray <r...@rjmx.net> PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761 signature.asc Description: OpenPGP digital signature

Bug#841294: Overrule maintainer of "global" to package a new upstream version

On Thu, Nov 03, 2016 at 09:20:30AM +0100, Philip Hands wrote: > Ron <r...@debian.org> writes: > > > > I can try to clarify that if there's a question in your mind that > > you don't think I touched on there. > > The question that remains is what you actually inten

Bug#841533: You could revert to gcc-5

and gcc-6, I have no idea whether it'll work for previous or future gcc versions. It depends on whether gcc, cc and other executables are symlinked to gcc-5, cc-6 and so on. Hope it helps. .Ron -- Ron Murray <r...@rjmx.net> PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E86

<    1   2   3   4   5   6   7   8   9   10   >