Bug#1036799: sylpheed: unable to send or read email after upgrading to Debian 12

I am a long term gmail user and I have tried sylpheed in the past, long  before Debian 12. I could not get it to work. From my investigations gmail works with relatively few email clients on Linux. It does however work with Thunderbird. From what I understand it takes a considerable amount of

Bug#694605: adopting

I guess am adopting this. Please don't expect any upload any time soon as I have too much too learn, and I see too many real issues as described in the bug reports. However if you would like to also work on it or a similar project please do contact me.

Bug#370126: (no subject)

I am trying to reproduce this (or work towards it) but quite frankly I am finding a more general problem. It occasionally dies and all the icons disappear. I assume it is the same problem although the description is not exactly the same.

Bug#1063839: lwm: fixed bugs, lintian clean, cross compiles, please review

Package: sponsorship-requests Severity: normal X-Debbugs-Cc: debian-cr...@lists.debian.org, s...@debian.org, np.bam...@gmail.com I have forked lwm so that my work can be reviewed: https://salsa.debian.org/npbamber/lwm If this is approved please grant me permission so I can keep the repository

Bug#1063649: maint-guide: synatx error in setup instructions for sbuild

Package: maint-guide Severity: important X-Debbugs-Cc: np.bam...@gmail.com Dear Maintainer, Hi Osamu, I think I found an error in section 3.6 (sbuild) of Guide for Debian Maintainers. I think > $ sudo usermod -a -G sbuild should be > $ sudo usermod -a -G sbuild yours Nicholas -- System

Bug#1051002: dwm: please set XDG_CURRENT_DESKTOP and use it to configure xdg-desktop-portal

    I attach a diff that describes a proposed fix. The file dwm-portals.conf should go into debian/xdg-desktop-portal so as  to be installed in /usr/share/xdg-desktop-portal diff -r debian-8/desktop/dwm.desktop debian-9/desktop/dwm.desktop 6a7,14 > X-GNOME-WMName=dwm > DesktopNames=dwm >

Bug#1051010: lwm: please set XDG_CURRENT_DESKTOP and use it to configure xdg-desktop-portal

So I have been reading up on flatpak documentation: https://docs.flatpak.org/en/latest/ Reading this it is clear that at least for the moment flatbox sandboxing is more of a line in the sand than the Berlin wall. This explains why the portals config is so hard to test. I attach the two

Bug#1063032: idesk: Please write script to convert dekstop files to idesk files

Package: idesk Version: 0.7.5-8 Severity: wishlist X-Debbugs-Cc: np.bam...@gmail.com Dear Maintainer, It would make it easier to switch from more modern desktops to idesk if such a utility script were available. -- System Information: Debian Release: trixie/sid APT prefers unstable APT

Bug#1063030: (no subject)

Package: idesk Version: 0.7.5-8 Severity: wishlist X-Debbugs-Cc: np.bam...@gmail.com Dear Maintainer, The home page (https://idesk.sourceforge.net/html/usage.html) has adequate information. However there is almost known in the man page. -- System Information: Debian Release: trixie/sid APT

Bug#1051010: lwm: please set XDG_CURRENT_DESKTOP and use it to configure xdg-desktop-portal

Firstly by copying, pasting and editing the xsessions desktop file from icewm to lwm I have been able to get XDG_CURRENT_DESKTOP=lwm into systemd, without any other files. I can see that this is the cleanest method. That said I infer from what I saw that every display manager is doing its own

Bug#1051010: Bug #1051010: lwm: please set XDG_CURRENT_DESKTOP and use it to configure xdg-desktop-portal

t; doesn't really work as a reminder of what bug and what package you're talking about. I hope that's compatible with your workflow. On Fri, 02 Feb 2024 at 12:11:13 +, Nicholas Bamber wrote: So far in order to investigate I have: 1. installed discord on a lwm desktop via flatpak. This works but

Bug#943917: some thoughts

I have come to believe this is not a bug. It may be that environment.d is very nice for systemd integration, but it is not very granular. Any environment entered via that route will end up in systemd user environments possibly even when it was not intended. Scripts in Xsession.d on the other

Bug#1051010: Investigating

So far in order to investigate I have: 1. installed discord on a lwm desktop via flatpak. This works but is pretty ugly and the whole filesystem is exposed. 2. Looking into ways to get the XDG_CURRENT_DESKTOP into the systemd user environment. Putting a script into the 55 priority in

Bug#940016: I can't reproduce

Control: tags 940016 + unreproducible + moreinfo I have a sddm set up with lwm as one of the options and it has not happened to me so far. Have you tried looking in your ~/.xsession-errors ? I guess you would need to reboot to be able to access given that you are dealing with a screen

Bug#810158: usrmerge/ksh

tag 810158 +wontfix thanks Thanks for the bug report. I've tagged this wontfix for now, but I will review when: 1. The usrmerge package has no piuparts errors. 2. The usrmerge package has a decent popcorn score. 3. The usrmerge bug reports do not scare me.

Bug#807810: Mention what if one wants to mark the bug forwarded to more than one place

James, I agree that I can see no need to support multiple forwarding addresses. However it turns out we currently support that. As a test this bug has been forwarded to two locations. Currently this bug is asking for that to be documented. On 17/12/15 14:17, James McCoy

Bug#807810: Mention what if one wants to mark the bug forwarded to more than one place

On 17/12/15 19:29, James McCoy wrote: On Dec 17, 2015 12:57 PM, "Nicholas Bamber" <nicho...@periapt.co.uk <mailto:nicho...@periapt.co.uk>> wrote: > > James, > I agree that I can see no need to support multiple forwarding addresses. However it

Bug#807810: Mention what if one wants to mark the bug forwarded to more than one place

I don't think that quite follows. I was not suggesting that bugs.debian.org change anything. But they might lock it down in the future. So if we document precisely how things work now we would be overdocumenting the system. On 17/12/15 23:05, 積丹尼 Dan Jacobson wrote: reassign 807810

Bug#807810: if there is more than one forwarded bug address

123456 "http://example.net/bugs/666 http://example.org/bugs/777; "NB" == Nicholas Bamber <nicho...@periapt.co.uk> writes: NB> But this syntax does not actually forward the bug report. It documents NB> where the bug report has been forwarded to. Why would we need more NB> than one of those?

Bug#807810: got it

But this syntax does not actually forward the bug report. It documents where the bug report has been forwarded to. Why would we need more than one of those? On 15/12/15 23:19, 積丹尼 Dan Jacobson wrote: Well, think email CCs. Who would have thought only one allowed! "NB" == Nicho

Bug#807810: got it

Actually the bts man page states the syntax: forwarded bug address It makes it faitly clear that only one upstream address is supported. On 15/12/15 03:17, 積丹尼 Dan Jacobson wrote: "NB" == Nicholas Bamber <nicho...@periapt.co.uk> writes: NB> Forgot to copy the submitter. F

Bug#807810: got it

Okay. On 15/12/15 03:17, 積丹尼 Dan Jacobson wrote: "NB" == Nicholas Bamber <nicho...@periapt.co.uk> writes: NB> Forgot to copy the submitter. Fixed! NB> On 13/12/15 12:32, Nicholas Bamber wrote: You want to be able to support forwarding to two places. I doubt that thi

Bug#807810: clarify please

I don't see why this is not clear. Bug reports that have been sent to upstream are marked with proof that they have been sent upstream.

Bug#807810: got it

You want to be able to support forwarding to two places. I doubt that this is a worthwhile idea, but in any case it would firts need to be fixed in the Debian bugs system.

Bug#807810: got it

Forgot to copy the submitter. Fixed! On 13/12/15 12:32, Nicholas Bamber wrote: You want to be able to support forwarding to two places. I doubt that this is a worthwhile idea, but in any case it would firts need to be fixed in the Debian bugs system.

Bug#802503: debcommit: Mention ~ in tag message, not .

Julian, I would be happy to take ownership of this, but I would rather any work on it did not hold up the next release of devscripts. On 12/12/15 10:25, Julian Andres Klode wrote: On Tue, Oct 20, 2015 at 10:29:00PM +0200, Julian Andres Klode wrote: Control: reassign -1 devscripts Control:

Bug#807241: freedesktop menus in Debian

Bill, I was led by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693135 into looking at packaging this archlinux package https://anonscm.debian.org/cgit/pkg-perl/packages/xdg-menu-convert.git/tree/?id=72ad66b . I am now having second thoughts as to whther this is worthwhile. As you are

Bug#458789: clean-orig-sorce target (custom download scripts)

available via the debian/watch interface. Does that make my point clearer? On 07/12/15 13:13, Osamu Aoki wrote: Please respond to 748...@bugs.debian.org Please drop 458...@bugs.debian.org Hi, On Sun, Dec 06, 2015 at 04:03:34PM +, Nicholas Bamber wrote: Osamu, I

Bug#807241: more info

I'm not going to call it 'xdg-menu' because that name could refer to a number of projects in the wild internet. Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749565 , Unless someone comes up with a better name I'll call it 'xdg-menu-convert'. I am treating the repository as the

Bug#807241: ITP: archlinux-xdg-menu -- Convert freedesktop files to a format used by various WMs

Package: wnpp Severity: wishlist Owner: Nicholas Bamber <nicho...@periapt.co.uk> * Package name: archlinux-xdg-menu Version : 0.7.6.2 Upstream Author : Sergej Pupykin <ser...@aur.archlinux.org> * URL : https://wiki.archlinux.org/index.php/Xdg-me

Bug#749565: hmm

There is some confusion here as two different upstream packages have been conflated. The one mentioned on the Arch linux wiki page is Perl based not python based.

Bug#458789: custom download scripts

Osamu, I was just thinking about this because the internet is the modern day equiavlent of the Wild West. It seems the bug report is fairly old and quite a lot of what is talked about has been implemented. However the essential issue is that some packages just do not fit into the normal

Bug#807011: ksh: Conditional variable expansion problem in while loop

Satoh, It is not releveant how this works in other shells (or even other versions of ksh). All that matters is whether this syntax is defined by the POSIX standard. It's not even documented as a bash feature let alone a POSIX standard. It may be of interest to you to be reminded

Bug#804597: blah

uscan does not seem to take very long to run. That makes this somewhat unimportant. I would like to see an example before persuing this. Also I tried with LWP::UserAgent::ProgressBar. It provides a different interface than LWP::UserAgent which means make it optional is quote hard.

Bug#804597: blah

On 03/12/15 15:34, Osamu Aoki wrote: Hi, On Thu, Dec 03, 2015 at 01:58:59PM +, Nicholas Bamber wrote: uscan does not seem to take very long to run. That makes this somewhat unimportant. I would like to see an example before persuing this. Also I tried with LWP::UserAgent::ProgressBar

Bug#806752: devscripts compilation failing

more build dependencies. - Package-specific info: --- /etc/devscripts.conf --- --- ~/.devscripts --- export DEBCHECKOUT_USER='Nicholas Bamber (Periapt) <nicho...@periapt.co.uk>' export DEBFULLNAME='Nicholas Bamber' export DEBEMAIL='nicho...@periapt.co.uk' export BTS_SMTP_AUTH_USERNAME='

Bug#559429: proposed patch

tags 559429 + patch thanks diff --git a/scripts/licensecheck.pl b/scripts/licensecheck.pl index 5f81286..e84a171 100755 --- a/scripts/licensecheck.pl +++ b/scripts/licensecheck.pl @@ -544,15 +544,15 @@ sub parselicense { $license = "GENERATED FILE"; } -if ($licensetext =~ /(are made

Bug#806205: bacula-fd

I spent a good part of the day trying to figure out what was going on here. The internet is full of pleas from help from people who are getting errors like: 25-Nov 08:41 chilcott2-fd JobId 461: Fatal error: Authorization key rejected by Storage daemon. Please see

Bug#803724: Fixed licensecheck

On 22. 11. 15 19:57, Dominique Dumont wrote: On Sunday 15 November 2015 18:56:11 Dominique Dumont wrote: Unless someone has a better idea, I'm going to revert most of the modification I've done with regard to encoding. licensecheck will go back to: - use a regexp to decide whether to parse a

Bug#805770: runit: feedback from experimentation

Package: runit Version: 2.1.2-3 Severity: normal Dear Maintainer, * What led up to the situation? I was experimenting as per http://smarden.org/runit/replaceinit.html . * What exactly did you do (or not do) that was effective (or ineffective)? Firstly in stage 3 the login failed. I

Bug#472199: licensecheck still broken

Thoughts below On 19. 11. 15 16:33, Dominique Dumont wrote: On Wednesday 18 November 2015 21:08:04 Nicholas Bamber wrote: 1.) Your thoughts on #472199? My reading of the bug report is you have no interest in this as you provide the functionality in cme. On the other hand I'd quite like

Bug#803724: licensecheck still broken

On 15. 11. 15 17:56, Dominique Dumont wrote: Hello Unfortunately, licensecheck is still broken: the encoding detection based on `file` command does not work as expected. For instance, in icedove. the file mozilla/js/src/vtune/jitprofiling.h contains windows-1252 character in a comment: $ file

Bug#804492: bash completion

Benjamin, Answers below: On 17. 11. 15 21:20, Benjamin Drung wrote: Hi Nicholas, I have a few questions about that applied patch: 1) Why do you copy all bash completions to BC_BUILD_DIR? I see no reason for that additional step. The problem is that the scripts in the

Bug#804492: bash completion

On 17. 11. 15 22:43, Nicholas Bamber wrote: Benjamin, Answers below: On 17. 11. 15 21:20, Benjamin Drung wrote: Hi Nicholas, I have a few questions about that applied patch: ... 3) Why do you create the symlinks via debian/links instead of the Makefile where you do all

Bug#805091: RFP: liblwp-useragent-progressbar-perl -- LWP user agent that can display a progress bar

Package: wnpp Severity: wishlist * Package name: liblwp-useragent-progressbar-perl Version : 1.100810 Upstream Author : Marcel Grünauer * URL : http://search.cpan.org/~marcel/LWP-UserAgent-ProgressBar-1.100810/lib/LWP/UserAgent/ProgressBar.pm *

Bug#804597: suggestion

The way I would approach is this is first of all to package LWP::UserAgent::ProgressBar (as per blocking bug). Then make this module a Suggests. Then check if this module is available and if so use that, otherwise fallback to LWP::UserAgent.

Bug#805120: bugs.debian.org: https://www.debian.org/Bugs/server-control does not document "newcomer" tag

Package: bugs.debian.org Severity: normal As per title. The text reads: "Available tags currently include patch, wontfix, moreinfo, unreproducible, help, pending, security, upstream, confirmed, fixed, fixed-upstream, fixed-in-experimental, d-i, ipv6, lfs, l10n, potato, woody, sarge,

Bug#804492: bash completion

On 10/11/15 12:17, Nicholas Bamber wrote: On 10/11/15 11:59, James McCoy wrote: On Tue, Nov 10, 2015 at 09:56:26AM +, Nicholas Bamber wrote: On the contrary, I think changing Makefiles is much more appropriate. Installing the completion files in the right place under the right name

Bug#804492: bash completion

"have" mechanism from bash completion scripts +- Removed undefined "$filenames" from chdist bash completion script +- Added missing complete statement to bash completion script for debi + + -- Nicholas Bamber <nicho...@periapt.co.uk> Mon, 09 Nov 2015 10:20:57 +

Bug#804492: bash completion

On 10/11/15 11:59, James McCoy wrote: On Tue, Nov 10, 2015 at 09:56:26AM +, Nicholas Bamber wrote: On the contrary, I think changing Makefiles is much more appropriate. Installing the completion files in the right place under the right name should happen regardless of whether

Bug#804492: devscripts: bash completion broken after move to new directory

but it is not as far as I can see defined. It might be intended to be "-o filenames" as with other completions though I do not really think that makes sense. -- Package-specific info: --- /etc/devscripts.conf --- --- ~/.devscripts --- export DEBCHECKOUT_USER='Nicholas Bamber (Periapt) <

Bug#780957: pos vars

tag 780957 +wontfix severity 780957 minor thanks I can confirm that this behaviour is happening in ksh93, (though I personally cannot confirm it is not in ksh88). I looked in the POSIX spec (http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_05_01 ), and I could

Bug#633524: ex

tag 633524 + pending thanks I've prepared a patch that makes 'ex' the default. In theory the user should be getting HISTEDIT set in ~/.kshrc so this is a fallback.

Bug#728225: memory leak

tag 728225 + moreinfo unreproducible thanks I have tried the trivial script and it runs consistently at 0.4% of memory. On the other hand I tried building ksh with export DEB_BUILD_MAINT_OPTIONS=sanitize=+all The resulting package was unusable generating the following report. However I don't

Bug#736410: fibbonacci

severity 736410 minor found 736410 93u+20120801-1 tag 736410 - patch thanks If you follow the links to the stackoverflow page you get to a script that I am not sure deserves to succeed. It recurses generating exponential number of subshells. Enabling a patch that would support that strikes me

Bug#792733: setenv

tag 792733 + pending thanks I'm going for # view/manipulate and export environment variables setenv() { case $# in 0) export ;; 1) export "$1"= ;; *) export "$1"="$2" ;; esac } I also made some other necessary changes to this file.

Bug#801609: license-reconcile: FTBFS: cannot parse file 't/data/example/sample.png'

On 01/11/15 18:07, Dominique Dumont wrote: On Sunday 01 November 2015 18:59:25 Jonas Smedegaard wrote: Jonas, do you agree with this proposal ? If you mean to *not* apply filter when user has explicitly instructed what files to work on (by use of regex), then I am in favor. Could you

Bug#801609: license-reconcile: FTBFS: cannot parse file 't/data/example/sample.png'

I have had another think and I would like to make the folloiwng points. 1.) license-reconcile is an experimental package and not at all critical to Debian. Unlike decscripts so something is a really wrong if a bug in license-reconcile affects devscripts. 2.) I think what Steve meant to do was

Bug#803615: ksh: builtin -l lists nonexistent builtins

Package: ksh Version: 93u+20120801-1 Severity: normal Dear Maintainer, * What led up to the situation? ksh builtin -l lists some builtins below /opt. My guess is that these are not being installed or compiled. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT

Bug#496167: binfmts-support

tag 496167 + pending thanks The solution to this problems is fairly standard and provided by the binfmts-support package. I have checked this into the repository and it will make it into the first release where I am maintainer. http://anonscm.debian.org/cgit/collab-maint/ksh.git

Bug#801609: license-reconcile: FTBFS: cannot parse file 't/data/example/sample.png'

I am working on this in license-reconcile. However I really don't see how this could affect devscripts. devscripts is a core package, license-reconcile is no such thing, On 30/10/15 17:58, Steve Langasek wrote: Control: affects -1 devscripts We are seeing this same failure in Ubuntu

Bug#801609: license-reconcile: FTBFS: cannot parse file 't/data/example/sample.png'

Langasek wrote: On Fri, Oct 30, 2015 at 07:36:11PM +, Nicholas Bamber wrote: I am working on this in license-reconcile. However I really don't see how this could affect devscripts. devscripts is a core package, license-reconcile is no such thing, I thought my reasoning was rather clear

Bug#633524: my friend, Ed

On 29/10/15 16:53, Thorsten Glaser wrote: Nicholas Bamber dixit: you think about it. That is in both the 'fc' command defaults to using ed which does not by default exist. At the very least both packages ought to have a I think that it’s a bug that it doesn’t exist by default ;-) Both Korn

Bug#633524: my friend, Ed

tag 633524 + confirmed thanks Thorsten, Dominik, I have confimed that this bug applies to mksh as well as ksh, so I wonder what you think about it. That is in both the 'fc' command defaults to using ed which does not by default exist. At the very least both packages ought to have a

Bug#764401: clarity please

ser wrote: Nicholas Bamber dixit: Could we get some clarity on this bug report please? I am considering adopting Yeah, some people have a life and don’t answer eMails 24/7… the 'ksh' package and if I do I either want to adopt mksh as well, or work closely with the mksh owner. Mh. I’m maintai

Bug#764401: clarity please

On 28/10/15 15:19, Thorsten Glaser wrote: Nicholas Bamber dixit: Please could Thorsten and Dominik please work out who will be responsible for mksh in Debian? Can you work together if that makes sense? I can sign and upload if necessary. OK, we had a short talk on the office floor about

Bug#764401: clarity please

I have thought about this comment a little more: > It is my agreement with David Korn (the ‘k’ in “ksh”) that > mksh must not be confused for the original, so please refrain > from doing so. It seems to me that if a link from ksh to mksh is not an infringement of this agreement, then big

Bug#764401: clarity please

Could we get some clarity on this bug report please? I am considering adopting the 'ksh' package and if I do I either want to adopt mksh as well, or work closely with the mksh owner.

Bug#764401: clarity please

On 28/10/15 21:04, Thorsten Glaser wrote: Nicholas Bamber dixit: 1.) If ksh is installed then ksh should be in /etc/shells. (#790118) I don’t think so. Users should be getting ksh93 or mksh (or, in earlier releases, even pdksh), but not an alternative. 2.) If ksh is not installed but mksh

Bug#733631: ksh compatibility

tag 733631 +wontfix thanks This has been documented on the interwebs and in print as a Good Thing (TM). http://docstore.mik.ua/orelly/unix3/korn/appb_08.htm To quote: "Starting with ksh93m, the built-in arithmetic facility understands a large percentage of the C language's expressions. This

Bug#742803: curious

tag 742803 + confirmed thanks Not sure what to make of this.

Bug#378809: wontfix

tag 378809 +wontfix thanks Until there is a move to package those other packages, there is no merit in this. So tagging wontfix.

Bug#720441: seg fault

tag 720441 + moreinfo unreproducible thanks I'm getting the impression this is fixed and I can't reproduce it. Just tagging moreinfo and unreproducible for now.

Bug#699288: seg fault

tag 699288 + moreinfo unreproducible thanks I can't reproduce this. Just tagging moreinfo and unreproducible for now.

Bug#433026: set -o emacs

tag 433026 + moreinfo unreproducible thanks I don't get this issue: $ set -o emacs $ foo ksh: foo: not found [No such file or directory] $ Maybe it has been fixed. Tagging moreinfo and unreproducible.

Bug#777930: ksh

owner 777930 nicho...@periapt.co.uk thanks The upload was rejected but I will try again.

Bug#691199: ksh

block 790118 by 691199 764401 thanks The text of #790118 asks that the ksh package run 'add-shell /bin/ksh' after install, and reverses it after removal. In of itself this is reasonable, Debian has two implementations of ksh (both of which are currently orphaned). Both use the

Bug#802225: ITP: libchatbot-eliza-perl -- Chatbot::Eliza

Package: wnpp Severity: wishlist Owner: Nicholas Bamber <nicho...@periapt.co.uk> * Package name: libchatbot-eliza-perl Version : 1.05 Upstream Author : Neil Bowers <n...@bowers.com> URL : http://search.cpan.org/~neilb/Chatbot-Eliza-1.05/lib/Chat

Bug#471537: repacking

Some thoughts, (but not as yet a patch) 1. Could you check for the version number to spot repackaging? Usually a string following a "plus" sign 2. Could you look at the watch file? For example version=3 opts=dversionmangle=s/\+ds$// \ http://sf.net/bashdb/bashdb-([0-9.]*)-([0-9.]*)\.tar\.gz

Bug#777930: nmu on the 10 day delayed queue

I have uploaded the patched version on the 10 day delayed queue.

Bug#801665: further info

tag 801665 +help reassign 801665 src:bashdb thanks user debian-...@lists.debian.org usertag 801665 kfreebsd thanks The error on Debian kfreebsd for set0 is as follows: -/«BUILDDIR»/bashdb-4.3.0.91+ds/command/set_sub/dollar0.sh: line 23: enable: cannot open shared object

Bug#801665: bashdb: set0 and readc builtins do not build on non-linux

Package: bashdb Version: 4.3.0.91+ds-4 Severity: minor Dear Maintainer, bashdb 4.3.0.91+ds-4 only builds on mon-linux because we turn off compiling set0 and readc. They compile but fail to load. There are three potential sources of the problem: 1. The set0.c and readc.c code. 2. The headers

Bug#403304: Debian: bash --debugger doesn't start the debugger

uid == 0 && dollar_vars[1]) start_debugger (); I enclose a patch that I believe would address this, and suggest it is an upstream bash issue. Description: correct check on $0 in conditions for entering debugger Author: Nicholas Bamber <nicho...@periapt.co.uk> Bug: https://bugs.debian.org/cgi-

Bug#801372: bashdb: FTBS issue relating to SIGXFSZ

Package: bashdb Version: 4.3.0.91+ds-3 Severity: important Dear Maintainer, * The reproducibility server is still generating FTBS FAIL: test-sig == --- /tmp/sig-filtered.check 2015-10-08 18:21:02.42800 -1200 +++ /tmp/sig-filtered.right 2015-10-08 18:21:02.38400

Bug#801372: patch

: Nicholas Bamber <nicho...@periapt.co.uk> Forwarded: no Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801372 Last-Update: 2015-10-09 Index: bashdb/test/integration/test-sig.in === --- bashdb.orig/test/integration/test-

Bug#801402: bashdb: FTBS on kfreebsd

Package: bashdb Version: 4.3.0.91+ds-3 Severity: important Dear Maintainer, FTBS on kfreebsd, but inspection shows that the issue is still an issue (albeit more minor on other platforms) gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -I /usr/include/bash/ -I /usr/include/bash//include

Bug#801175: bashdb: semi-reproducible FTBS

Package: bashdb Version: 4.3.0.91+ds-1 Severity: important Tags: upstream patch Dear Maintainer, * The package passed extensive FTBS testing but failed when it hit the reproducibility site (jenkins). Here is an extract of the log: FAIL: test-sig .

Bug#801175: patches

output. Author: Nicholas Bamber <nicho...@periapt.co.uk> Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801175 Forwarded: no Last-Update: 2015-10-07 Index: bashdb/test/integration/check-common.sh.in === --- bashdb.ori

Bug#772500: me too

I have this isse a lot. A work around is to reassign all the keys in the preferences, but it's a pain. Earlier versions did not do this.

Bug#752724: bashdb

Oleksandr, Are you interested in fixing the RC bugs in bashdb? I've had a look and I think I could give it a go. it mainly seems to need updating to the latest pstream version.

Bug#505924: cwm

James, I have to apologize but I have been overwhelmed by stuff and I have to cut back. I am sure you will find someone else to sponsor this. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#609883: Status?

On 06/03/13 19:26, micah anderson wrote: Hi Nicholas, I'm inquiring as to the status of the packaging of percona-server-core that you took on as an ITP for the Debian Mysql packaging team. I haven't seen an update to this bug for some time now and figured it was time for a ping.

Bug#686485: [license-reconcile] some more license mappings (#1)

Phil, Thanks for the interest. It's actually now under the Debian Perl Group's reposiitory. I guess I should have updated the ITP so sorry. It's also been uploaded and is sitting in the new queue. I have to say after working on this for six months I was just desparate to get at least 0.1

Bug#505924: cwm

James, Thanks. I have downloaded and I will look. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#505924: cwm

. 3.) I am suspicious of cwm.postinst. I could look into what is required a bit more, but let me know what you think about that. On 14/11/12 23:25, Nicholas Bamber wrote: James, I got round to downloading the package today. On 27/10/12 15:47, James McDonald wrote: Hi Nicholas, Finally

Bug#694351: lsof: do not depend on perl

The scripts had to be patched and there was too much to do in recent versions. But a fix is already checked in. It should be released as soon as wheezy is released. That said most systems will have perl anyway so the impact should be small. On 25/11/12 19:09, Shawn Landden wrote: Package: lsof

Bug#505924: cwm

James, I got round to downloading the package today. On 27/10/12 15:47, James McDonald wrote: Hi Nicholas, Finally found some time to implement these changes! On 21 Sep 2012, at 01:56, Nicholas Bamber nicho...@periapt.co.uk wrote: I followed your advice and it works. I can

Bug#692871: mysql-5.5

found 692871 5.5.24+dfsg-9 tag 692871 +patch thanks This is clearly not introduced in 5.5.28+dfsg-1 and I am marking it as such. I'd like to get 5.5.28++dfsg-1 into testing before looking at this. ANd then I would like to check what we can close as a result of fixing this. -- To UNSUBSCRIBE,

Bug#692145: retitle unblock

-04 17:24:15.0 + @@ -1,3 +1,21 @@ +maradns (1.4.12-5) unstable; urgency=low + + * Resolved use of undefined environment variable in maintenance +scripts. Thanks to Andreas Beckmann and Adam Barratt for pointing +this out + + -- Nicholas Bamber nicho...@periapt.co.uk Sun, 04 Nov

Bug#692145: unblock: maradns/1.4.12-4

curious I didn't notice that. Anyway please don't remove it and I'll have another look. On 02/11/12 19:15, Adam D. Barratt wrote: Control: tags -1 + moreinfo On Fri, 2012-11-02 at 18:32 +0100, Andreas Beckmann wrote: Is CFG_TEMPLATE used before it's getting defined? $ grep -n TEMPLATE

  1   2   3   4   5   6   7   8   9   >