> Exception: tostring() has been removed. Please call tobytes() instead.
Thanks for reporting. Turns out upstream has fixed this, so this will
get fixed with the next upstream release.
Gr.
Matthijs
signature.asc
Description: Digital signature
> Error:(Exception) "tostring() has been removed. Please call tobytes()
> instead.".
Thanks for reporting. I've informed upstream about this bug, it will
probably be fixed for the next upstream release.
Gr.
Matthijs
signature.asc
Description: Digital signature
Package: debootstrap
Version: 1.0.75
Followup-For: Bug #586158
Hi,
it seems this problem is still present in the most recent version, but
manifests differently (possibly earlier, in addition to the failure
reported back in 2010, dunno). Here's what I did:
matthijs@grubby:~/docs/Virtual
Hi Stephane,
> I am just not convinced with your workaround.
> The two signals are from a different nature and we have them both for a
> reason.
Well, given that SIGPWR is the default signal sent on halt by lxc-stop,
making systemd handle that signal by shutting down seems like a
solution, not a
Hi Nulld1g1t,
> On a D8 host server with D7 containers upgraded to D8 with systemd -
> following the instructions from the LXC Debian page.
>
> When I use lxc-stop command to cleanly stop a container, it waits,
> times out and finally kills the container instead of issuing a clean
> shutdown.
Package: lxc
Version: 1:1.0.6-6+deb8u1
Severity: normal
Dear Maintainer,
while debugging an lxc problem, I was surprised by the lack of any log
output from lxc-start, which turned out to end up in a logfile. This
report is against the stable version of lxc, since I can't easily test
the
Hi Alejandro,
I just stumbled upon this bug in UI::Dialog with improper escaping of
shell metacharacters. I reported it upstream:
https://rt.cpan.org/Public/Bug/Display.html?id=107364review
I was going to contact the Debian security team about this issue, when I
noticed that this bug has been
Package: thinkfan
Version: 0.9.2-1
Severity: important
Tags: patch
Hi,
while modifying my configuration to be a bit more aggressive on high
temperatures, I found that thinkfan exited without changing the fan
level. When started with -n, it wrote:
setfan_ibm: Error writing to
Hi,
this bug is marked as fixed in 5.0~a3, but I can't find the commit that
fixes it? Looking at the git master version, it seems this is still
broken as well?
Hi Edmund,
It failed to build in Jessie, amd64 and arm64. In each case the error
was:
Thanks for reporting! A bit of digging shows that upstream fixed this
already in r27079, which I think is part of the latest 1.5.0 release.
I'll try to upload that version soon, and verify if this bug is
Hi Antoine,
What do you have in DAEMON_ARGS then?
DAEMON_ARGS=--fork --config /data/applications/grobbebol/grobbebol.cfg
One thing that strikes me as a possibility is that I probably don't use
the init.d script at all here. I am running willie in a Jessie system
running systemd as PID 1.
Hi Antoine,
Still unsolved is that if stopping takes a long time, or never
completes, --kill is never called and the subsequent start happens
immediately and fails.
Why is that? is it because the return value of --quit is incorrect?
should a bug report be filed there?
I see that the
Hi Antoine,
I just tried running willie, but it seems that the restart and stop
actions of the init script are broken.
I don'T believe they are. I am using them here without problems.
Interesting.
One thing with this package is that the config file is not automatically
configured right
Hi,
I just tried running willie, but it seems that the restart and stop
actions of the init script are broken.
On a related note, I just noticed that the --kill invocation in do_stop
is mostly useless. do_stop in the initscript runs willie --quit and if
the returns a non-zero status, runs
Installing python3-pkg-resources and python3-setuptools from sid fixes this,
making me believe python3-pip is missing a dependency.
Still doesn't work:
matthijs@login:~$ pip3
Traceback (most recent call last):
File /usr/bin/pip3, line 9, in module
load_entry_point('pip==1.5.6',
(25-08-1982) mart...@brumit.nl
Are you sure that you want to sign this key with your
key Matthijs Kooijman matth...@stdin.nl (A1565658)
Really sign? (y/N) y
However, when multiple uids are present, the fingerprint is not shown:
[INFO] Sign the following keys according to your policy
Package: signing-party
Version: 1.1.11-1
Severity: normal
Hi folks,
When fetching some keys (presumably those with expired subkeys), I get
errors from caff. Here's the command and output to reproduce:
matthijs@grubby:~$ caff e1c21845
[INFO] Fetching keys from pgp.mit.edu, this may take a
Seems I missed last year's ping, but I'm still here! :-)
signature.asc
Description: Digital signature
Hi Etienne,
it seems that last year, you were planning to maintain the gnome3
version of hamster-applet, hamster-time-tracker. Are you still
interested in this? Perhaps you're interested in comaintaining the
package?
It seems that there has been some new activity upstream in the last
weeks, with
into the Debian
version first?
On a related note: It seems there is a new upstream version available,
that integrated the single patch currently in the debian version.
Gr.
Matthijs
Description: Fix conntrack parsing for kernels using lowercase protocol names
Author: Matthijs Kooijman matth...@stdin.nl
Hey Matthias,
1.4.2 is available. Most online games use it, so 1.4.1 is no longer very
useful in multiplayer mode, hence the elevated priority.
Thanks for the reminder, I've just uploaded the new version.
Gr.
Matthijs
signature.asc
Description: Digital signature
Package: npm
Version: 1.4.21+ds-1
Severity: normal
Dear maintainer,
The npm list command (in unstable) seems to use the ansicolors module,
but AFAICS it is not available in Debian yet?
matthijs@grubby:~$ npm list
npm ERR! Error: Cannot find module 'ansicolors'
npm ERR! at
Package: npm
Version: 1.4.21+ds-1
Severity: normal
Dear maintainer,
when installing the serialport package through npm, I get the following
messages:
matthijs@grubby:~$ npm install -g serialport
/home/matthijs/.node_modules/bin/serialportterm -
Package: volumeicon-alsa
Version: 0.4.6-2.1
Severity: normal
Hi,
it would be great if this package could provide a .desktop file, which
makes it easier to start. Also, this allows simply linking or copying
the desktop file into ~/.config/autostart to make the application
autostart.
Perhaps it's
Hey Christoph,
Good news: Upstream fixed the issue. I expect the next release within
the next four to six weeks. In my understanding the bug you've
encountered isn't that important it requires an immediate upload to
Debian. But I might be convinced otherwise.
Cool! I'm not in a particular
Hey Eugene,
It would be nice to have latest and greatest openttd 1.4.0 which
features, among other things, merged CargoDist.
Good point! I was busy when 1.4.0 was released and then forgot about it
afterwards. I'll have a look right now, thanks for the reminder!
Gr.
Matthijs
signature.asc
Hi Nobuhiro,
Hmm, are you saying that libpng-config is in the -tools package? Isn't
it customary to put it in -dev?
libpng-config is available in libpng16-devtools package.
# Perhaps, it will be fixed this so that it can be used as
libpng-devtools virtual package.
This is provided by
Hi Joël,
Could you test the OpenTTD version in experimental and report if it
fixes the problems you were seeing?
I will try as soon as possible. I have halted my sparc due to some
kernel instabilities (3.2 is not stable on all sun4u I have).
Did you get a chance to have another look
Package: lintian
Version: 2.5.22.1
Severity: normal
When running lintian op openttd 1.4.0 (not yet uploaded), it says:
E: openttd source: source-is-missing os/dos/cwsdpmi/cwsdpmi.txt
N:
N:The source of the following file is missing. Lintian checked a few
N:possible paths to find
Hey folks,
it seems the patch referenced for this bug has been integrated upstream
and released as part of the 2.7 release last year.
Any plans to update to that release?
Gr.
Matthijs
signature.asc
Description: Digital signature
Hi Nobuhiro,
thanks for your report!
This problem is solved by adding libpng16-tools to Build-Depends.
(...)
checking libpng... not found
configure: error: libpng-config couldn't be found
configure: error: you supplied '2', but it seems invalid
make[1]: *** [override_dh_auto_configure]
Hi Rodolfo,
could you try with the current (latest) uswsusp package and the latest
initramfs-tools package?
I just tried this on my current machine and didn't get the warning.
The original report was on another machine, but downgrading uswsusp to
the stable version (1.0+20110509-3) allows me to
On Fri, 2013-11-29 at 15:35 +0100, Matthijs Kooijman wrote:
upstream developers for the openttd package have identified a remote
denial-of-service (program crash) in the openttd game. They have made
patches available, which I'd like to include in wheezy and squeeze.
[...]
Attached
] Fix CVE-2013-6411 (Denial of service using forcefully
+crashed aircrafts). See http://security.openttd.org/en/CVE-2013-6411
+for details.
+
+ -- Matthijs Kooijman matth...@stdin.nl Fri, 29 Nov 2013 12:11:14 +0100
+
openttd (1.0.4-6) stable-security; urgency=high
* [9ca1ffd] Improve
Hey Niels,
I have been thinking about this some more and I have come to the
conclusion that we cannot ensure packages are Lintian clean in both
use-cases. For many checks, we might be able to do it, but there are
some where the output associated with the check depends on the packages
Hi Bastien,
Any news of this bug ? I volontuer to implement this fonctionnality
I haven't looked at this bug (or the wishlist bug I linked before) since
my last message. If you want to find out what needs to happen and update
/ rewrite / whatever my patch, feel free (I'll be away for the next
Package: initscripts
Version: 2.88dsf-43
Severity: normal
Dear Maintainer,
Normally, the mount-functions.sh mounts /run, /tmp, etc as tmpfs
filesystems. To signal this fact to the other bootscripts, it creates a
.tmpfs file inside.
However, when the mounting fails, and the corresponding
Package: ucf
Version: 3.0027+nmu1
Severity: normal
Hi folks,
on my system, I have php5-cgi and php5-cli installed, which each have
their respective ucf-registered conffile:
/etc/php5/cgi/php.ini
/etc/php5/cli/php.ini
However, the latter is a symlink to the former:
$ ls
Ok, I've merged these two patches with some modifications
Looks good. Thanks for taking care of it.
They look good to me too. Thanks for spotting the small details I missed
:-)
Gr.
Matthijs
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Package: xserver-xorg-input-wacom
Version: 0.15.0+20120515-2
Followup-For: Bug #675802
Hi folks,
for me, this bug also affects the buttons on the pad, not just the touch
ring.
Looking at the upstream changelog, a few pad-button related fixes have
been made since 0.15 (though a quick attempt at
Package: virtualbox-dkms
Version: 4.1.18-dfsg-2.1
Severity: normal
Tags: patch
Hi,
the version in experimental contains patches to build with kernel 3.7
and 3.8, but changes in the kernel break building on 3.9 again, because
some defines were moved.
Here's a trivial patch to fix building
Hi Joël,
a while ago you reported a color problem with OpenTTD on your sparc64.
Some palette-related fixes that made things work on my sparc64 with 8bit
video were included in the 1.3.0 OpenTTD release, which was recently
uploaded to experimental.
Could you test the OpenTTD version in
Hi,
I tested this patch (by applying it locally to the files in
/usr/lib/mime/packages), but it didn't work for me. My libreoffice
version (1:3.6.4-1) uses --nologo instead of --no-logo. Perhaps this is
a typo in your patch?
In any case, I've attached an updated patch which works for me
Hi Bertrand,
I did a bit more digging into the palette code of SDL, trying to figure
out what is happening and what we could be expecting from this. What
follows is a fairly detailed description of what I've learned, which is
probably not so interesting for you, but I wanted to write it down for
And here are the attachments I promised in the previous mail...
attachment: correct.pngattachment: wrong.png
This provides some examples on using dpkg-buildflags and buildflags.mk
in debian/rules, notes that --export=make is not recommended and
explicitly mentions that the list of build flags is subject to change.
Closes: #657627
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
man/dpkg
Hi,
It seems to me that the best place to put the enabling code is in
/etc/bash.bashrc, but that's of course not up to the bash-completion
package.
One thing that springs to mind is to have bash offer an
/etc/bash.bashrc.d directory similar to /etc/profile.d, so
bash-completion can ship a
Hi Arthur,
It is generally not recommended to use LDAP accounts for daemons because
you will get into all sorts of problems when the network or LDAP server
is unavailable and during boot and shutdown.
Yeah, but the filesystem that stores the mail is shared between
different (lxc) virtual
Hi Jaldhar,
I've added this to 2.1.7-3 which I just uploaded to unstable.
Awesome, thanks!
Gr.
Matthijs
signature.asc
Description: Digital signature
The bug for nslcd I reported is here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692633
signature.asc
Description: Digital signature
The bug for dovecot I reported is here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692632
signature.asc
Description: Digital signature
Hey Julian,
thanks for reporting this bug and including the patch. I'll make sure
that this get fixed in upstream.
Since wheezy has fontconfig 2.8, this shouldn't be a problem there. For
sid, this isn't a problem yet, but I guess fontconfig 2.10 will be
packages sooner or later, so I'll see if I
=high
+
+ * [e7a5026] Fix CVE-2012-3436 (Denial of service using ships on half
+tiles and landscaping). See
+http://security.openttd.org/en/CVE-2012-3436 for details.
+
+ -- Matthijs Kooijman matth...@stdin.nl Wed, 01 Aug 2012 23:20:31 +0200
+
openttd (1.2.1-1) unstable; urgency=low
Hi Moritz,
This still needs to be fixed in testing/wheezy. Since testing is frozen
please only upload the isolated security fix and ask for a freeze
exception/unblock.
I've asked the Release Team if it's ok to upload a new upstream bugfix
release, or if they would rather have just this fix
Hi Steven,
thanks for your comments.
the intent was to include version 1.2.2, I only included the debdiff for
1.2.1 since the final 1.2.2 release had not happened at that time.
It has now, so I'm preparing an updated debdiff right now.
In which case perhaps you could attach a new debdiff?
Package: debian-maintainers
Severity: normal
Not sure what I should put here, but I still enjoy being a maintainer! ;-)
Gr.
Matthijs
signature.asc
Description: Digital signature
This is a resend of an earlier message that really didn't want to make
it through to the Debian servers. I've uploaded the debdiffs and
changelog here instead of attaching them:
http://www.stdout.nl/static/tmp/openttd-debdiffs/
Original message follows
---
Hi folks,
I've attached debdiffs for
Hi folks,
I've attached debdiffs for both of the proposed options for review.
I hate to nag, but upstream has released version 1.2.2 yesterday and I'd
like to start packaging either option.
Could someone have another look at this? Upstream has made no further
changes to 1.2.2 relative to
Hi Raphael,
FWIW, I saw no debdiff on the list and there's no debdiff in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683376 either.
Are you sure you sent it to 683...@bugs.debian.org ?
Weird. It's really in my sent box, but it never ended up at bugs.d.o
apparently. I'll resend the mail
Hi,
Weird. It's really in my sent box, but it never ended up at bugs.d.o
apparently. I'll resend the mail in a minute.
Apparently that didn't work either. My STMP logs show that bugs-master
accepted the resent message this morning, but then it got lost. I'll
contact the postmaster about that.
Package: lintian
Version: 2.5.10
Severity: normal
Hi folks,
I just stumbled upon lintian giving me a false unused-override
tag. This happens when you override some tag because the file
needed for it is in another package, but then run lintian on both
packages involved: Lintian now finds the file
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package openttd. Recently, upstream developers have
discovered a security problem in most versions of OpenTTD, including the
one in testing.
For squeeze/stable, a fixed
Hi Niels,
We cannot really make this decision without knowing what we are
looking at.
Please include a debdiff for each option showing the differences
between the version in testing and the version that option would provide.
Ok, I'll do so as soon as upstream releases the 1.2.2 RC1, which
Hi Moritz,
Please see http://security.openttd.org/en/CVE-2012-3436
I was just working on this, I'll send a fixed package to your RT today.
Gr.
Matthijs
signature.asc
Description: Digital signature
Hi Stefan,
In my experience, with several USB/ hotpluggable lirc devices and a
separate /var/ partition, this is the actual problem. What happens is
that the lircd socket gets created underneath the final /var/run/,
/run/ respectively, before it is mounted on its final place, thereby
Hi,
I'm interested in this feature as well (so hopefully bash-completion can
replace its /etc/profile.d/bash_completion.sh with an
/etc/bash.bashrc.d/bash_completion.sh to really work out of the box, see
#678174).
So, I created a patch. It isn't very complicated (pretty much copied the
lines for
Package: bash-completion
Version: 1:1.99-3
Severity: minor
Hi folks,
as was already mentioned in an aside in #593835: It's nice that
bash_completion is now enabled by default through /etc/profile.d, but
this only works for login shells. In particular, shells running in a
screen session or a
Package: lirc
Version: 0.9.0~pre1-1
Severity: normal
Hi,
I was trying to get lirc running, but for some reason the /var/run/lirc
directory showed up empty after boot. Lircd was running, but the socket
and pidfile were not there. After a morning of debugging I found out
what was happening, but
Hi Stefan,
I'm pretty sure this is due to a missing LSB dependency on $local_fs
for lirc's init script.
I'm not so sure this is really the case: The problem is really that the
udev rule triggers a lirc (re)start too soon on the boot sequence, not
that the normal init script invocation is too
Hi Joël,
On sparc64, openttd colors are swapped (green is green, but red seems to be
replaced by blue and blue by red). I think there is an endianess trouble in
openttd.
I've managed to reproduce the problem (or at least _a_ problem) on an
old Ultra1 I managed to get my hands on for this
tag 669145 pending
tag 669145 pending
thanks
Date: Tue Apr 17 22:17:20 2012 +0200
Author: Matthijs Kooijman matth...@stdin.nl
Commit ID: b72702fdd4adbdebdbe8c5aed080079196563969
Commit URL:
http://git.debian.org/?p=users/agx/git-buildpackage.git;a=commitdiff;h
Package: gnome-settings-daemon
Version: 3.2.2-3
Severity: minor
Hi,
the gnome-settings-daemon manpage documents these options:
gnome-settings-daemon [--debug] [--no-daemon] [--gconf-prefix]
[--display=DISPLAY]
However, not all of those are supported and not all supported options are
tag 669159 pending
thanks
Date: Tue Apr 17 22:41:48 2012 +0200
Author: Matthijs Kooijman matth...@stdin.nl
Commit ID: a43e9b9b2c95fe7f3252fb9c6c3de861c7f8d4a6
Commit URL:
http://git.debian.org/?p=users/agx/git-buildpackage.git;a=commitdiff;h=a43e9b9b2c95fe7f3252fb9c6c3de861c7f8d4a6
Patch URL
tag 669159 pending
thanks
Date: Tue Apr 17 22:41:48 2012 +0200
Author: Matthijs Kooijman matth...@stdin.nl
Commit ID: a43e9b9b2c95fe7f3252fb9c6c3de861c7f8d4a6
Commit URL:
http://git.debian.org/?p=users/agx/git-buildpackage.git;a=commitdiff;h=a43e9b9b2c95fe7f3252fb9c6c3de861c7f8d4a6
Patch URL
tag 669145 pending
tag 669145 pending
thanks
Date: Tue Apr 17 22:17:20 2012 +0200
Author: Matthijs Kooijman matth...@stdin.nl
Commit ID: b72702fdd4adbdebdbe8c5aed080079196563969
Commit URL:
http://git.debian.org/?p=users/agx/git-buildpackage.git;a=commitdiff;h
Package: git-buildpackage
Severity: wishlist
Tags: patch
Hi Guido,
for a while, I've been missing an option in git-dch to automatically
commit the resulting changelog. In my work flow, I regularly think I'm
done packaging, so I generate the changelog using git-dch, commit it and
then build the
Package: git-buildpackage
Severity: normal
Tags: patch
Hi Guido,
seems the current debian/rules does not support nocheck, since debhelper
still calls the override_dh_auto_test target, even when nocheck is
given (only dh_auto_test itself is a no-op when nocheck is given).
I'll send over a patch
Thanks: Matthijs Kooijman
Closes: #669149
---
debian/rules |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/debian/rules b/debian/rules
index 6360dff..63845b5 100755
--- a/debian/rules
+++ b/debian/rules
@@ -14,6 +14,7 @@ PYCHECKER_ARGS=-boptparse --no-override
Package: git-buildpackage
Severity: wishlist
Tags: patch
Hi Guido,
usually I want git-dch to use only the first line of commit messages,
which is the default. However, occasionally I have a commit that
warrants some more explanation, also in the Debian changelog, so I'd
like to use the full
Thanks: Matthijs Kooijman
Closes: #669145
---
I think this patch adds some value for some people, at least myself.
Feel free to change the default for import-msg, I've just used the
format I'm used to, but I'm not sure if there is any de facto standard
for it.
I considered always popping up
This new tag makes git-dch use the full commit message when generating
the Debian changelog file, even when --full is not given.
Thanks: Matthijs Kooijman
Closes: #669159
---
docs/chapters/releases.sgml | 12 ++--
docs/manpages/git-dch.sgml | 11 ---
gbp/dch.py
Package: git-buildpackage
Version: 0.5.32
Severity: minor
Hi,
I just tried importing a .tar.xz with git-import-orig, which works.
However, the manpage says upstream-source can either be a gzip or bzip2
compressed tar archive or an already unpacked source tree.
Could you update the manpage to be
I'm currently discussing how to properly fix this with upstream,
so we'll probably see a fix for this issue in openttd 1.2.0.
Upstream has committed a fix to include a language-only entry (without a
country code) for every language supported. This fix should be included
in the upcoming 1.2.0
Hi Cyril,
Here's a patch for this FTBFS. No intent to NMU.
Thanks for the patch. However, upstream already released a new version
(in response to this bug) to fix this issue, so I'll be packaging that
instead.
Gr.
Matthijs
signature.asc
Description: Digital signature
Hi Ronny,
The locale keys used in the Comment entries of the openttd desktop file
are much too specific. I use locale de_CH (German/Switzerland) and got
the untranslated comment because the translation was only available for
the specific locale de_DE (German/Germany). The country
Hi Simon,
The hardening CPPFLAGS are missing from the current build; which
includes -D_FORTIFY_SOURCE=2. The following patch enables them.
Hmm, seems I missed that one, as well as the hardening-check tool to
test this stuff. On a second reading of the documentation, they are
promoted well
Hey Joey,
I'm not sure I agree: If I remember correctly, this requires adding the
dpkg-maintscript-helper call to three different maintainer scripts
(preinst, postinst, postrm), with identical arguments.
That's what dh_installdeb automates.
Ah! I initially thought you referred to the
Hi Jonathan,
The cdrom_id program from the udev package (version 167-3) refuse to
freeze
with a linux 2.6.39. That prevent the system to suspend.
It works will with a 2.6.38 kernel, then the problem starts with the 2.6.39
kernel.
Said to be fixed in 3.2. Can you confirm?
Seems so:
Hey Joey,
I thought I saw something on debian-dpkg about dpkg-maintscript-helper
getting support for removal of old directories, as this presumably does.
Although I could be remembering wrong, if it's going to do it,
this should use it.
For reference, here's the wishlist report about it:
Hey Joey,
Yes, and if all the work is done by dpkg-maintscript-helper anyway,
I tend to feel that adding this special interface to use it does not
actually make anything simpler. So it could just document that it needs
to be used and point at dh_installdeb's support for maintscript.
I'm not
Package: debhelper
Version: 8.0.0
Severity: wishlist
Tags: patch
Hi folks,
I just converted a patch to use dh_installdocs --link-doc to store the
documentation in just one of my binary packages instead of duplicating
them in multiple packages.
However, it turns out that when you do this for an
---
autoscripts/preinst-rmdocdir |6 ++
dh_installdocs | 21 +
2 files changed, 27 insertions(+), 0 deletions(-)
create mode 100644 autoscripts/preinst-rmdocdir
diff --git a/autoscripts/preinst-rmdocdir b/autoscripts/preinst-rmdocdir
new file mode
Hi Joey,
Your patch omits this file.
Woops, I just resent the patch wit the file added.
I thought I saw something on debian-dpkg about dpkg-maintscript-helper
getting support for removal of old directories, as this presumably does.
Although I could be remembering wrong, if it's going to do
Package: udisks
Version: 1.0.4-3
Severity: wishlist
Hi folks,
I just found out about the udisks command, which seems like a nice way
to control udisks from the commandline (e.g., without having to start
nautilus and grab my mouse just to mount or unmount something).
This is of course only
Hi folks,
I also tried to prevent the negatiation from happening by passing
Accept-Encoding: identity in the HTTP request using wget, but that
didn't help
I just realized that this is not about Accept-Encoding, but the
Accept: header. If apt would send an Accept: text/plain header, the
mirror
Hi folks,
just stumbled upon this report, and I have a small suggestion to improve
Jonathan's patch:
--- a/policy.sgml
+++ b/policy.sgml
@@ -2256,18 +2256,13 @@
massage this example in order to make it work for your
package.
example compact=compact
-CFLAGS =
Package: debconf
Version: 1.5.41
Severity: minor
Tags: patch
Hi folks,
just ran into an issue with debconf's debug logging, which I'm preparing
a patch for.
The issue is simple: When confmodule sends an unknown command to
debconf, it replies with:
Unsupported command \$command\ (full line
Package: dpkg-dev
Version: 1.16.1.2
Severity: wishlist
File: /usr/bin/dpkg-buildflags
Hi folks,
I've been reading up on dpkg-buildflags, hardening et al, to get my
dh-based package to as compliant as possible. However, I got quite
confused about what I should do and how I should do it. Instead
Package: debconf
Version: 1.5.41
Severity: normal
Hi folks,
after spending quite some time on debugging a nullmailer postinst issue,
I discovered that debconf's db_set chokes when multi-line values are
passed to it (in this particular case, /etc/mailname contained two
lines, and db_set
Before, unknown commands or invalid commandlines could cause an error to
be sent to the confmodule, but not printed with DEBCONF_DEBUG=developer,
making debugging such an error hard.
---
Debconf/ConfModule.pm |8 ++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git
101 - 200 of 444 matches
Mail list logo
