Package: postfix-ldap
Version: 2.10.2-1
Severity: wishlist
Tags: patch
Dear Maintainer,
LDAP SASL binds have been added to Postfix back to v2.8, at the expense
of a flag in the CCARGS [1].
It would be great if postfix-ldap included SASL support. As far as I can
tell, the change boilds down to a
tags 659971 patch
thanks
One could use the (core) module I18N::Langinfo to decode
$CONFIG{'owner'} from the user's locale to Perl's internal format.
Also, since the template is expected to be in UTF-8, it needs to be
converted as well.
Cheers,
--
Guilhem.
--- a/usr/bin/caff
+++
Oh, I forgot about UIDs, which may need to be converted as well. Patch
updated, sorry for the noise.
--
Guilhem.
diff -ru a/caff/caff b/caff/caff
--- a/caff/caff
+++ b/caff/caff
@@ -321,6 +321,7 @@
use Text::Template;
use MIME::Entity;
use Encode;
+use I18N::Langinfo;
use Fcntl;
use
tags 637222 patch
thanks
IMHO an argument against fixing the issue in Mail::Mailer directly is
that the Q-Encoding of the headers is typically done when constructing
the MIME::Entity object. Mail::Mailer extracts the envelope from/to
from the header (or delegated the extraction to eg,
Package: pinentry-curses
Version: 0.8.3-1
Severity: important
Dear Maintainer,
Since the upgrade to 0.8.3-1 pinentry-curses is no longer able to show
multiline prompts. This is problematic when used with gpg-agent, since for
instance the key ID that is being unlocked is no longer visible.
Here
tags 618781 patch
thanks
I think the problem is not with gpgsigs per se, but rather with the
LaTeX output it produces. (As Tanguy hinted at, the text output of
UTF-8 encoded input files seems to be rendered properly.) LaTeX is
in fact known for its poor support of Unicode characters in input
Package: signing-party
Version: 1.1.5-1
Severity: normal
Tags: patch
Dear Maintainer,
gpgsigs currently doesn't wrap long UIDs in its LaTeX output. This is
a problem, because after compilation and printing, the full UID is not
always visible on the printout.
I propose the enclosed patch, which
tags 736963 patch
thanks
The enclosed patch allows the user's key(s) to be passed as gpg accepts
it that is, as short, 0xshort, long or 0xlong format, as well as
a (formatted or not) fingerprint:
- 0x109E6244
- 109E6244
- 0x39278DA8109E6244
- 39278DA8109E6244
- 7420 DF86 BCE1 5A45 8DCE
Package: grub-installer
Version: 1.85
Followup-For: Bug #666974
Tags: patch
Dear Maintainer,
The bug is still present in Wheezy's installer. The enclosed (naive)
patch makes sure grub-installer jumps to state 2 (hence ignores
$default_bootdev) if grub-installer/bootdev is known. It has been
Hi,
I'd also be happy to give a hand by becoming an adopter.
Cheers,
--
Guilhem.
signature.asc
Description: Digital signature
Hi Thijs,
On Sun, 23 Feb 2014 at 14:53:28 +0100, Thijs Kinkhorst wrote:
Thank you both for your interest.
And thanks for your trust :-)
If you give me your alioth username I will arrange the commit access.
My alioth username is guilhem-guest. By the way as far as I'm concerned
I'll use
Interesting. Since 2008-03-16 /usr/share/signing-party/ is explicitly
added to the $PATH. Does your gpg.conf explicitly sets a value for
exec-path?
I'm just curious as I can't reproduce that bug in a clean sid chroot;
But your solution is cleaner is cleaner and more robust since it doesn't
That's cool! I cannot think of any side effect either, short of
- that'll only work on POSIX systems (unsure if we care, but it'd
still be possible to fallback to STDIN on non-POSIX systems), and
- one would not longer be able to answer the questions with things like
‘yes | caff …’.
Well you've been warned :-P
[WARN] You have set arguments to pass to Mail::Mailer. Better fix
your MTA. (Also, Mail::Mailer's error reporting is non existant, so
it won't tell you when it doesn't work.)
As for the error itself, it has nothing to do with caff but with the
“non
notfound 728543 1.1.5-1
thanks
Hi Carsten,
If anything should depend on libnet-smtp-ssl-perl it should probably be
libmailtools-perl (which provides Mail::Mailer and which signing-party
depends on), not signining-party itself.
libmailtools-perl actually added the dependency somewhere between
Hi there,
While adding signencrypt support to caff certainly wouldn't hurt, I'm
unsure what is the threat model exactly and what what kind of
vulnerability a message signature would patch. I mean, the only
interesting thing in the messages caff sends is the attachment
(encrypted together with
On Wed, 21 Aug 2013 at 10:40:38 -0400, Joey Hess wrote:
caff seems to have its own hard-coded list of keyservers, rather than using
the same ones I have gpg configured to use. This seems a gratuitous
duplication
of configuration.
An alternative would be to grep ~/.gnupg/gpg.conf for
Hi Carsten,
On Tue, 25 Feb 2014 at 17:24:43 +0100, Carsten Schoenert wrote:
So everything should be fine for Jessie or greater. But as I can't check
Wheezy directly. So a quick search via packages.debian.org shows me the
dependency is still missing in Wheezy
Hi,
Are you sure the issue was encountered using 1.1.4-1? According to the
changelog a similar bug, #590666, was fixed during that release.
I can't reproduce the bug anyway.
Cheers,
--
Guilhem.
signature.asc
Description: Digital signature
Hi,
On Tue, 19 Mar 2013 15:47:18 +0100 Dominik George wrote:
it actually tells you about the wrong permissions when you tell it to
continue after the error. Which is really not very helpful.
I pushed a patch to make it dump gpg's standard error after importing
the keys, meaning you'd get
Hi,
In fact the manpage says (all) subkeys are removed by default unless pgp-clean
is used with flag -s:
-s --export-subkeys
Do not remove subkeys. (Pruned by default.)
Cheers,
--
Guilhem.
signature.asc
Description: Digital signature
Hi,
Ideally solving this bug would solve #637115 as well. But I couldn't
find a nice way to integrate mutt (probably other MUAs as well) with
caff. First I've got two questions:
1/ Do you want to interact with the MUA (for instance to edit the
headers), or should it work in batch mode?
Control: found -1 2013.60-1
Hi,
I fully second this patch. Would be great to see it applied in Jessie ;-)
Another common use case is where the dropbear in the ramdisk should
listen on a port other than 22: then a simple firewall rule can make
it inaccessible from the whole world while keeping
Hi there,
In case you would like to try it out and give feedback before the
release, I pushed a fixed to the repository.
svn://svn.debian.org/pgp-tools/trunk/
gpgparticipants formatted content is now accepted on caff's STDIN.
(Only v4 keys annotated with Fingerprint OK and ID OK are
Hi,
While your tool would certainly be a valuable addition to signing-party,
a blocker is that it gets the digest algorithm on certificate signatures
by parsing the output of ‘--list-packets’, which as far as I can tell
isn't documented.
IMHO a better (and faster) approach would be, as you
Hi Jonas,
This looks useful indeed, but after a quick look at the code it doesn't
really appeal to me, as the script seems rather unfinished.
Also, I find it rather confusing that it's not possible not to report
expired/revoked subkeys in case the key has other valid subkey(s)
covering the same
Hi,
I wonder if these scripts are still useful? As of 1.1.6-1 caff is able
to parse key fingerprints directly from a gpgparticipants(1) format (and
annotated) list. See also #622560:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622560
Cheers,
--
Guilhem.
signature.asc
Description:
Control: tag -1 wontfix
Hi,
On Thu, 20 Mar 2014 21:51:52 -0700, H. S. Teoh wrote:
I'm also running into this problem, caff insists on sending email with
MAIL FROM as username@localhost instead of the value I set in
$CONFIG{'email'}. I've tried Todd Lyons' workaround but it still
didn't work
Hi Stefan,
On Wed, 07 May 2014 at 11:25:37 +0200, Stefan Huber wrote:
gpgparticipants sets LC_CTYPE=C.UTF-8 for gpg when printing each key.
On systems where C.UTF-8 is not available (e.g., Gentoo), the fallback
locale causes the output not to be UTF-8 encoded, even if the
overridden LC_CTYPE
On Wed, 07 May 2014 at 14:22:30 +0200, Stefan Huber wrote:
Thank you for applying the patch. Since you apply LANGUAGE=en to gpg,
you may want to look into using LC_TIME=en for /bin/date, such that the
time on the first line is given in English?
As ‘en’ is not a valid locale, I think date(1)
Hi,
On Mon, 16 Jun 2014 at 17:59:45 +0200, Olivier Berger wrote:
False error : a result of my own customizations.
Sorry about the bothering.
No problem :-)
It might still be useful to fix this (which looks like a race condition
and/or unexpected output from gpg). Would you mind sharing your
Source: grub-legacy
Version: 0.97-67
Severity: normal
Tag: patch
Dear Maintainer,
It'd be convenient to place grub-install's temporary files in $TMPDIR
when set. Right now they are placed in /tmp, which on a typical install
is on the same partition as /; hence if for some reason / is mounted
Hi Jochen,
On Sat, 23 Aug 2014 at 17:31:06 +0200, Jochen Schmitt wrote:
I would like to forward several patches which I have applied to the
pgp-tools package in Fedora for upstream integration.
Thanks!
diff -urNp --exclude-from=/home/mdomsch/excludes --minimal
Hi Noël,
On Tue, 26 Aug 2014 at 18:43:51 +0200, Noël Köthe wrote:
caff doens not convert the IDN domains to punycode:
Hmm, it's working fine here (signing-party 1.1.8-1):
:~$ locale
LANG=en_US.UTF-8
LANGUAGE=en
LC_CTYPE=en_US.utf8
LC_NUMERIC=C
LC_TIME=en_DK.utf8
LC_COLLATE=en_US.utf8
I did file a bug against gpg2 a couple of weeks ago (#751266). I'm
a bit reluctant to implement a dirty bugfix in caff, as one can fallback
to gpg in the meantime.
Cheers,
--
Guilhem.
signature.asc
Description: Digital signature
Hi Ralf,
On Mon, 02 Jun 2014 at 22:22:15 +0200, Ralf Jung wrote:
After setting up caff as described in https://wiki.debian.org/caff, I still
get the following warnings when caff sends a mail
Use of uninitialized value $name in pattern match (m//) at
/usr/share/perl5/Mail/Internet.pm line
Hi,
Is there a reason *not* to enable SASL binds in postfix-ldap? After
all, dict_ldap.so is linked against libsasl and OpenLDAP's libldap,
which does support SASL binds. Furthermore, ldap_table(5) and
/usr/share/doc/postfix/LDAP_README.gz already mention SASL binds (OK
it's written that their
Control: retitle -1 Mail::Internet spews warnings for unnamed users
Control: reassign -1 libmailtools-perl 2.12-1
Control: tag -1 patch
(split /,/, $name)[0] is undefined when $name is the empty string.
--
Guilhem.
--- a/Mail/Internet.pm
+++ b/Mail/Internet.pm
@@ -532,7 +532,7 @@
#
Package: netcat-openbsd
Version: 1.105-7
Severity: normal
Dear Maintainer,
An interesting feature available in the new release is the addition of
a ‘-F’ flag, to pass the first connected socket to the standard output
and exit. (This is useful with the ‘ProxyUseFdPass’ option in OpenSSH
6.5 or
Control: severity -1 important
Hi Ilario,
First off, thanks for this thorough report :-)
This seems to be due to gpg ignoring signatures under the cutoff
certification level (2 by default) when exporting with the
‘export-clean’ option.
Compare the output of the following two lines:
gpg
Control: notfound -1 1.4.16-1.1
Contol: merge -1 735363
This seems to be working now:
gpg --export $keyID | gpg --homedir $(mktemp -d --tmpdir gpg.XX)
--trust-model=always --import
--
Guilhem.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (990,
Package: gnupg2
Version: 2.0.23-1
Severity: important
Dear Maintainer,
gnupg2 is also affected by #735363 (and #737128).
$ gpg --export $keyID | gpg2 --homedir $(mktemp -d) --trust-model=always
--import
gpg: keyring `/tmp/tmp.CgvawKyhkU/secring.gpg' created
gpg: keyring
On Wed, 11 Jun 2014 at 17:56:50 +0200, Ilario Gelmetti wrote:
I have to retire my statement on Key2: the problem is present also with
this key. To verify this I created a new gpg key with an empty pubring
and tried to sign with caff that Key2 and it didn't work. With my main
key I didn't see
Package: busybox
Version: 1:1.22.0-6
Severity: wishlist
Dear Maintainer,
In udebs, it is common to redirect the standard output of a command to
a fifo, and use that to display progress bars in the installer.
trap 'kill $pid' EXIT
/path/to/command $fifo
while read -u 7 n; do
Package: pinentry-curses
Version: 0.8.3-2
Severity: normal
Tags: upstream
Dear Maintainer,
When two parallel instance gpg(1) prompt the user for a passphrase,
there should be a locking mechanism to avoid both pinentry to try to
modify the TTY at the same time.
The problem is visible in the
Package: mutt
Version: 1.5.22-1
Severity: normal
Tags: patch
Dear Maintainer,
As signing-party's pgpring, Mutt's does not look at the right field as
key lengh for DSA and Elgamal keys, which results to an incorrect
output similar to that reported in #602284. The attached patch, adapted
from
On Tue, 21 Nov 2010 at 20:51:12 +0100, Franck Joncourt wrote:
Is there a proper document which explains to us how the fields are organized
in a
keyblock according to the algorithm used? I have looked at the gnupg sources,
and found a bit of information in build_packet.c, but this is still
Control: tag -1 moreinfo
Hi Nik,
mutt is capable of tagging messages matching a given pattern, and of
applying an action on all tagged messages, hence your second motivating
point is untrue IMHO.
That said, I believe your tool can be of interest, and possibly to mutt
users as well. I've got a
Package: mysql-server
Version: 5.5.35+dfsg-2
Severity: normal
Dear Maintainer,
When installing a MySQL server in a non-interactive environment (for
instance using a configuration manager):
DEBIAN_FRONTEND=noninteractive apt-get install mysql-server
The post-install hook currently creates a
Package: slapd
Version: 2.4.39-1
Severity: wishlist
Dear Maintainer,
When installing slapd in a non-interactive environment (for instance
using a configuration manager):
DEBIAN_FRONTEND=noninteractive apt-get install slapd
Currently a new database ‘olcDatabase={1}hdb,cn=config’ is
Oh by the way, please note that the email address I use for packaging,
namely guil...@guilhem.org, is not that of the primary UID of my OpenPGP
key 7420 DF86 BCE1 5A45 8DCE 9976 3927 8DA8 109E 6244.
Thanks!
--
Guilhem.
signature.asc
Description: Digital signature
gnupg2 2.0.26-3 has been packaged today, and includes a fix for #751266.
Setting $CONFIG{'gpg'} to be 'gpg2' in the .caffrc is working again.
--
Guilhem.
signature.asc
Description: Digital signature
Hi there,
FYI, the soon to be 1.1.11 release of signing-party includes a new
script ‘gpg-key2latex’, which hopefully will solve the following
limitations inherent to the PS format:
- Support for Unicode in User ID (xelatex might be required for CJK
characters, though).
- Support for UAT
-party (1.1.10-1+deb8u1) unstable; urgency=medium
+
+ [ Guilhem Moulin ]
+ * caff:
++ Fix RCF 2822 violation: Never localize the Date header, regarless of
+ the LC_ALL, LC_TIME and LANG in use. Regression introduced in r698.
+ (Closes: #767371)
+
+ -- Guilhem Moulin guil
Control: retitle -1 unblock: signing-party/1.1.10-2
unblock signing-party/1.1.10-2
On Fri, 07 Nov 2014 at 23:26:24 +0100, Niels Thykier wrote:
On 2014-11-07 22:36, Guilhem Moulin wrote:
I would like to upload the attached changes: a regression bug has been
introduced in signing-party 1.1.10-1
@@
+signing-party (1.1.10-3) unstable; urgency=medium
+
+ [ Guilhem Moulin ]
+ * caff:
++ Fix RCF 2822 violation: Never localize the Date header, regarless of
+ the LC_ALL, LC_TIME and LANG in use. Regression introduced in r698.
+ (Closes: #767371)
+
+ -- Guilhem Moulin guil
Control: severity -1 wishlist
Hi Matthijs,
If no UID(s) is (are) selected, gpg wants to make sure you really intend
to sign all UIDs. So a workaround is to preselect all UIDs; with gpg2
it's can be done in one go with a single command in the prompt: ‘uid *’
(OTOH if you use the 1.4 branch, as
Hej Nelson,
On Mon, 17 Nov 2014 at 19:15:58 -0200, Nelson A. de Oliveira wrote:
Couldn't gpg-key2* support a homedir option like gpg?
In indeed, and so could caff, gpglist, gpgsigs and probably other tools
in the signing-party package ;-) But is there really a use case that's
not covered
Control: severity -1 wishlist
Control: retitle -1 Please support GnuPG 2.1
Hi Brian,
On Tue, 02 Dec 2014 at 17:23:21 -0500, Brian Minton wrote:
If I have the gpg config entry set to gpg2 (with or without the path)
version 2.1, I get the following message:
(I'm assuming you're talking about
Control: tags -1 + pending
Hi Nelson,
On Sat, 29 Nov 2014 at 13:17:35 -0200, Nelson A. de Oliveira wrote:
caff has a hardcoded e-mail subject.
It would be good if we could also customize it (in .caffrc)
Done in r739:
https://anonscm.debian.org/viewvc/pgp-tools?view=revisionrevision=739
There
On Tue, 02 Dec 2014 at 17:23:21 -0500, Brian Minton wrote:
If I have the gpg config entry set to gpg2 (with or without the path)
version 2.1, I get the following message:
gpg: skipped 0424DC19B678A1A9: No secret key
0424DC19B678A1A9 is my key, the private key of which is usable by gpg2
On Tue, 02 Dec 2014 at 19:20:22 -0500, Brian Minton wrote:
Update: That did not in fact fix the problem. I had removed the gpg2 line
from the config file. When I put it back in, it still gives the message.
I just pushed a fix (r741) for the branches 1.4 and 2.0 of GnuPG. The
2.1 branch has a
Control: tags -1 + pending
Hi Peter,
On Thu, 11 Dec 2014 at 19:28:29 +0100, Peter Lebbing wrote:
I noticed that the quiet zone is only about 2 modules, and that's
assuming you cut it exactly at the lines. My phone had no problem
scanning the picture even on a starkly contrasting background,
This is due to GnuPG 2.1 ignoring --secret-keyring:
--secret-keyring file
This is an obsolete option and ignored. All secret keys are
stored in the private-keys-v1.d directory below the GnuPG home
directory.
But caff has its own GnuPG home (~/.caff/gnupghome by
Following http://lists.gnupg.org/pipermail/gnupg-devel/2015-January/029301.html
caff's $CONFIG{'secret-keyring'} has been deprecated, and the symlinks
are automatically created when the secret keyrings are not present.
--
Guilhem.
signature.asc
Description: Digital signature
I'm a bit reluctant to make caff non-interactive by default, and would
rather let users specify the MUA and their options themselves, rather
than hardcoding a bunch of supported MUAs in caff. My 'mail-cmd'
proposal above seems to achieve the same thing (let users interact with
their MUA to add
Hi Ewen,
Your report says you have signing-party 1.1.4-1, but your patch seems to
be against a more recent version :-P But anyway I agree that the
standard output shouldn't be thrown away like that. That said the
absence of GPG_TTY in the environment doesn't seem to bother my gpg(1);
doesn't
Control: retitle -1 caff: The absence of GPG_TTY causes silent caff failures in
OSX
Control: tag -1 + pending
On Wed, 21 Jan 2015 at 11:12:44 +1300, Ewen McNeill wrote:
- MacPorts (OS X) (gpg 1.4.18): works _without_ sderr redirected, fails with
stderr redirected (no output, exit code 1),
On Wed, 21 Jan 2015 at 15:52:45 +1300, Ewen McNeill wrote:
if (defined($ENV{MACHTYPE})
$ENV{MACHTYPE} =~ /apple/ ! defined($ENV{'GPG_TTY'})) {
warn warning: Certain gpg actions may fail if GPG_TTY is not set, ,
causing silent caff failures.\n;
}
But maybe there should
In fact I changed that (r773) to symlink the agent's socket(s) instead;
it's much cleaner as it doesn't spawn multiple agent in
~/.caff/gnupghome and the temporary directories. However caff won't
work with gpg = 2.1.2, due to gpg not flushing its standard output
before the status prompts during
Package: mysql-server
Version: 5.5.42-1
Severity: normal
Dear Maintainer,
When checking for insecure root accounts, ‘debian-start.inc.sh’ merely
lists root accounts with an empty password:
SELECT COUNT(*) FROM mysql.user WHERE user='root' and password='';
However, such an account can be
Package: src:linux
Version: 4.0.2-1
Severity: important
Dear Maintainer,
I have the following — probably not so common — configuration:
- libreboot BIOS (a deblobed coreboot) with a GRUB2 payload
- root is BTRFS, with rootflags=subvol=@
Since I don't want to flash a new payload onto the
On Fri, 15 May 2015 at 13:47:59 +0100, Ben Hutchings wrote:
On Fri, 2015-05-15 at 05:24 +0200, Guilhem Moulin wrote:
On Fri, 15 May 2015 at 03:57:35 +0100, Ben Hutchings wrote:
GRUB knows how to do this properly, so you're just making things
difficult for yourself.
Since there is always
On Fri, 15 May 2015 at 03:57:35 +0100, Ben Hutchings wrote:
GRUB knows how to do this properly, so you're just making things
difficult for yourself.
Since there is always a risk of bricking the board when flashing the
BIOS chip, I don't want to add a hook add flash it whenever I upgrade
the
Package: dput
Version: 0.9.6.4
Severity: normal
Dear Maintainer,
dput uses a hardcoded ‘/usr/bin/gpg’ when checking signatures. This no
longer works if the user uses GnuPG 2.1 (currently available in
experimental) has migrated her keyring to the keybox format, since this
format is not readable
upstream release. (Closes: #775222.)
[ Guilhem Moulin ]
* debian/source/format: 3.0 (quilt)
* debian/compat: 9
* debian/control: bump Standards-Version to 3.9.6 (no changes necessary).
* debian/copyright: add machine-readable file.
* Split up package in dropbear-bin (binaries
On Mon, 01 Jun 2015 at 07:53:28 -0500, Karl O. Pinc wrote:
On Mon, 1 Jun 2015 13:46:26 +0200 Guilhem Moulin guil...@guilhem.org wrote:
On Sun, 31 May 2015 at 21:30:25 -0500, Karl O. Pinc wrote:
On Mon, 1 Jun 2015 03:30:36 +0200 Guilhem Moulin guil...@guilhem.org
wrote:
I'd rather
‘configure_networking’ was moved to the background in commit a3b7a7d6.
According to debian/changelog it was meant to be a fix for #514213 and
#524728. I'd say the proper fix would be to follow Simon McVittie's
suggestion [0] and split the dropbear package as follows:
* dropbear-bin
Control: tags -1 patch
Here is a patch setting the homedir to $(mktemp -d /root-XX).
--
Guilhem.
--- /home/guilhem/initramfs-tools/hooks/dropbear 2014-08-12 00:15:40.0 +0200
+++ /usr/share/initramfs-tools/hooks/dropbear 2015-06-16 23:11:27.060710678 +0200
@@ -31,8 +31,9 @@
for so
On Fri, 29 May 2015 at 19:47:43 +0200, Guilhem Moulin wrote:
I believe the issue it that the init-premount script sets $IPOPTS while
‘configure_networking’ uses $IP to pick and configure interfaces.
Forget about that. IP is assigned properly by the ‘init’ script, and
IPOPTS isn't used anywhere
In fact /dev/pts is mounted in the ‘init’ initramfs script since commit
261811b5 [0], so we could simply remove ‘scripts/init-premount/devpts’.
--
Guilhem.
[0]
https://anonscm.debian.org/cgit/kernel/initramfs-tools.git/commit/init?id=261811b5d0524c7fe579bf4ca22915c2dc4b636f
signature.asc
Control: tags -1 patch
Control: retitle -1 Stalled SSH connections after existing initrd due to
remaining dropbear children processes
To terminate all existing SSH sessions, it's somewhat cleaner to kill
all children before exiting the server.
Cheers,
--
Guilhem.
--- dropbear/dropbear
On Fri, 29 May 2015 at 23:35:26 -0500, Karl O. Pinc wrote:
Or maybe adding a flush after the ipconfig brings the
interface down.
Hopefully this would remove the old boot-temporary ip
netmask, routes, etc. and leave the interface clean
and ready to get it's normal configuration.
On Sun, 31 May 2015 at 21:30:25 -0500, Karl O. Pinc wrote:
On Mon, 1 Jun 2015 03:30:36 +0200 Guilhem Moulin guil...@guilhem.org wrote:
I'll see if the linux-initramfs-tool would be willing to accept an
‘unconfigure_networking’ function using ip(1).
I haven't looked at all the pieces
An arguably simpler alternative to copying mountpoint(1) is to grep
through /proc/mounts.
--
Guilhem.
signature.asc
Description: Digital signature
On Fri, 29 May 2015 at 19:18:04 +0200, Guilhem Moulin wrote:
An arguably simpler alternative to copying mountpoint(1) is to grep
through /proc/mounts.
Forgot the patch, sorry.
--
Guilhem.
--- a/usr/share/initramfs-tools/scripts/init-premount/devpts
+++ b/usr/share/initramfs-tools/scripts/init
tags -1 patch
thanks
I believe the issue it that the init-premount script sets $IPOPTS while
‘configure_networking’ uses $IP to pick and configure interfaces.
--
Guilhem.
--- a/usr/share/initramfs-tools/scripts/init-premount/dropbear
+++
Hi,
The problem is that, while klibc can bring up and down network
interfaces, the interface configuration does not go away.
What doesn't go away exactly? (What do you mean by “interface
configuration”?) I wonder if ip(8) could help, by the way. It's
included in the initrd, can flush routes
The MIME::Field::ParamVal module is provided by libmime-tools-perl, on
which caff depends.
$ dpkg -L libmime-tools-perl | grep ParamVal.pm
/usr/share/perl5/MIME/Field/ParamVal.pm
$ dpkg -l | grep libmime-tools-perl
ii libmime-tools-perl 5.505-1 all Perl5
applied as well.
http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/2015q3/001777.html
However, this time I didn't pull in the changes (although Debian is now 3
releases behind…)
On Fri, Jul 31, 2015 at 05:44:09AM +0200, Guilhem Moulin wrote:
Alright, this one is new to me. I'm not sure how
Hi there,
On Thu, 30 Jul 2015 at 22:21:21 +0200, Helmut Grohne wrote:
In general, I'd find sponsoring this NMU much easier if the package
split and the fixing of those many bugs could happen in separate
uploads. Each part is complex and the fallout is hard to estimate. I
understand that such
Hi Gianfranco,
On Thu, 20 Aug 2015 at 07:23:55 +, Gianfranco Costamagna wrote:
I didn't follow the thread, and seems that other DDs are already caring of
this one, so I would just put my .02$ (and let me know if you need a review
or help).
Thanks! So far only Helmut has given feedback
Control: tags -1 pending
Hi Tomasz,
On Sun, 23 Aug 2015 at 12:47:01 +0200, Tomasz Buchert wrote:
my gpg key is paticular: it has an uid that has been revoked and then
subsequently recreated. As a result, it does not show up in the output of
gpglist.
I've created a patch that fixes that. It
Hi Helmut,
On Tue, 28 Jul 2015 at 23:01:57 +0200, Helmut Grohne wrote:
dropbear has two problems concerning cross compilation:
* It runs a build arch strip which cannot handle the crossed binaries.
Thus the build fails (see attached log).
* It does not run dpkg-shlibdeps, thus Depends are
.
On Sat, Jul 11, 2015 at 03:20:52PM +0200, Guilhem Moulin wrote:
Note that while the current maintainer (Gerrit, CC'ed) told me to go
ahead and proceed with a NMU, they are not able to sponsor me at the
moment. Furthermore I'm currently a DM and would be open to
co-maintenance once time is ripe
Hi Vincent, Gerrit,
On Tue, 14 Jul 2015 at 18:42:53 -0700, Vincent Cheng wrote:
NMUs are intended to be minimally intrusive and be targeted to fix
specific bugs (and usually RC/important ones); that means that in
general, you should avoid things like new upstream releases and
extensive
Hi,
On Mon, 20 Jul 2015 at 13:55:35 +0200, Maria Valentina Marin wrote:
While working on the “reproducible builds” effort [1], we have noticed
that dropbear could not be built reproducibly.
There is an ongoing effort to refactor and split the dropbear package in
order to isolate the binary,
Package: irssi-plugin-otr
Version: 1.0.0-1+b2
Severity: normal
Dear Maintainer,
‘src/otr-formats.c’ defines a couple of irssi templates to be configured
with ‘/format otr ’. The list of templates and their current
values is listed by the ‘/format otr’ command:
[Statusbar]
stb_plaintext
ackage with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/n/netmask/netmask_2.4.3-1.dsc
Changes since the last upload:
[ Robert Stone ]
* New upstream release. (Closes: #802884.)
[ Guilhem Moulin ]
* debian/patches:
+ Make the build reproducible: s
Hi,
On Fri, 16 Oct 2015 at 16:01:21 +0200, e-mmanuel wrote:
> During upgrade of roundcube (from 1.1.2+dfsg.1-4 to 1.1.2+dfsg.1-5),
> aptitude reports errors and upgrade stops.
Hmm odd. The 1.1.2+dfsg.1-4 → 1.1.2+dfsg.1-5 upgrade works just file in a
clean(+dialog) sid chroot:
~# echo 'deb
1 - 100 of 1049 matches
Mail list logo
