On 2019-02-13 Nye Liu wrote:
> Also, I'm not sure that the infinite spin wait while() makes sense in
> GNUTLS_E_EAGAIN either. Is some sort of select() more appropriate?
Hello,
It is the common idiom for this special case. See e.g. GnuTLS'
examples.
On 2019-02-13 "Torrance, Douglas" wrote:
> On 12/27/18 3:48 PM, Nye Liu wrote:
>> Package: wmbiff
>> Version: 0.4.31-1
>> Severity: important
>> Tags: upstream patch
>> If gnutls_read() or read() report EAGAIN, tlscomm_expect() fails:
>> wmbiff/nyet comm: wrote a000 CAPABILITY
>> wmbiff/nyet
On 2019-02-12 Brian May wrote:
> Andreas Metzler writes:
[...]
>> For exim I am now passing --exec
>> /path/to/daemon as argument to s-s-d
[...]
>> Alternatively (or additionally) setting --user should also work.
> OK, thanks for this. I hadn't realized you could
On 2019-02-12 Brian May wrote:
> On Thu, Feb 07, 2019 at 06:53:18PM +0100, Andreas Metzler wrote:
>>> I was planning a new upload during this week (the version in sid, will
>>> not migrate as is due to a regression in dgit's autopkgtests), but can
>>> postpone it a
On 2019-02-09 Andreas Metzler wrote:
[...]
> I really have no idea why it is not working:
Hello,
Just to get the complete story: Could you please
- doublecheck the contents of /etc/exim4/update-exim4.conf.conf, gzip and
attach it.
- Show "debconf-show exim4-config" outpu
On 2019-02-09 Günter Frenz wrote:
> Hallo
> here is the debug output using dialog-frontend:
I really have no idea why it is not working:
Here it is reading /etc/exim4/update-exim4.conf.conf and setting
the shell variable dc_eximconfig_configtype ...
> + [ -e /etc/exim4/update-exim4.conf.conf
On 2019-02-09 Günter Frenz wrote:
> Am Sat, 9 Feb 2019 13:36:27 +0100 kam folgendes bei mir an:
[...]
> > If I strip down your update-exim4.conf.conf file to the non-comment
> > lines
> > -
[...]
> With or without using -plow I get this result:
> dc_eximconfig_configtype=''
>
On 2019-02-09 Günter Frenz wrote:
> Package: exim4-config
> Version: 4.92~RC5-2
> Severity: important
> Dear Maintainer,
> when I try to run dpkg-reconfigure exim4-config only the first screen
> with the question for the general configuration appears. After selecting
> any of these the
On 2019-02-09 Lev Lamberov wrote:
> Package: exim4
> Version: 4.92~RC5-1
> Severity: important
> Dear Maintainer,
> I had fully working exim4, but after some update (I'm not sure which
> one, but the problem arose few days ago) I started to get Connection
> timed out error, say:
> 2019-02-09
On 2019-02-09 Günter Frenz wrote:
[...]
> -- Package-specific info:
[...]
> # /etc/exim4/update-exim4.conf.conf #
> # Edit this file and /etc/mailname by hand and execute update-exim4.conf
> # yourself or use 'dpkg-reconfigure exim4-config'
> #
> # Please note that this is _not_ a dpkg-conffile
On 2019-02-09 Elimar Riesebieter wrote:
> Package: exim4
> Version: 4.92~RC5-2
> Severity: important
> Dear maintainer,
> restarting exim4 on a sysvinit system does not close an existing exim4
> daemon. paniclog gives: 2019-02-09 00:07:21 socket bind() to port 25
> for address (any IPv4)
On 2019-02-07 Guillem Jover wrote:
> On Wed, 2019-02-06 at 19:58:52 +0100, Andreas Metzler wrote:
[...]
>> dpkg's changelog.Debian says:
>> * start-stop-daemon: Check whether standalone --pidfile use is secure.
>> Prompted by Michael Orlitzky .
>> the regula
Package: lsb-base
Version: 10.2018112800
Severity: serious
Hello,
there is a logic error in /lib/lsb/init-functions's killproc:
base=${1##*/}
if [ ! $pidfile ]; then
name_param="--name $base --pidfile /var/run/$base.pid"
else
name_param="--pidfile $pidfile"
fi
The
Package: dpkg
Version: 1.19.3
Severity: important
With 1.19.3 the following command stopped working:
/sbin/start-stop-daemon --stop --retry 5 --quiet --pidfile /run/exim4/exim.pid
/sbin/start-stop-daemon: matching only on non-root pidfile /run/exim4/exim.pid
is insecure
Afaict this broke exim
Control: forcemerge 921326 921205
On 2019-02-04 Vincent Lefevre wrote:
> Package: exim4-daemon-light
> Version: 4.92~RC5-1
> Severity: important
> After the latest upgrade, I got in /var/log/exim4/paniclog:
> 2019-02-01 11:15:40 socket bind() to port 25 for address 127.0.0.1 failed:
> Address
On 2019-02-04 Marc Haber wrote:
> On Sun, Feb 03, 2019 at 01:20:53PM +0100, Andreas Metzler wrote:
>> That usually is a local configuration error, starting the daemon both
>> via initscript and other means, or having another program running that
>> is bound to 25. The
On 2019-02-02 積丹尼 Dan Jacobson wrote:
> Package: exim4-daemon-light
> Version: 4.92~RC5-1
> For the last two upgrades,
> /var/log/exim4/paniclog:
> 2019-02-02 21:47:07 socket bind() to port 25 for address (any IPv6) failed:
> Address already in use: daemon abandoned
> As we see from
On 2019-02-03 Willi Mann wrote:
> just for the record, I tried to reproduce the build failure on eller
> (mipsel porterbox), but it builds fine there. I'm wondering whether the
> timeout set on line 232 of tests/srp.c (40 seconds) is too short for
> slower build hosts.
Hello,
The two builds on
On 2019-02-02 Thorsten Glaser wrote:
> Package: mcabber
> Version: 1.1.0-1.1
> Severity: serious
> Tags: ipv6
> Justification: fails release goal
> I’m currently in the FOSDEM WLAN (IPv6-only, not FOSDEM-legacy),
> and I can neither connect to the Jabber server with SRV RRs nor
> when hardcoding
Control: forwarded -1 https://gitlab.com/gnutls/gnutls/issues/685
On 2019-01-26 Hiroyuki YAMAMORI wrote:
> Package: gnutls-bin
> Version: 3.6.5-2
> Severity: normal
> Dear Maintainer,
> Some fast ciphers(suites) are strange results.
> $ gnutls-cli --benchmark-ciphers
> Checking AEAD ciphers,
Control: tags -1 confirmed
On 2019-01-22 Daniel Kahn Gillmor wrote:
> Package: gnutls-bin
> Version: 3.6.5-2
> Severity: minor
> In certtool(1), it says:
>--key-type=string
> Specify the key type to use on key generation.
> This option can be combined with
Control: severity -1 serious
On 2019-01-22 James Van Zandt wrote:
> Package: libgnutls30
> Version: 3.6.5-2
> Severity: critical
> Justification: breaks unrelated software
Hello,
I am downgrading severity. apt is not "unrelated", it *uses* gnutls.
> Dear Maintainer,
> Sun 20 Jan 2019
On 2019-01-21 積丹尼 Dan Jacobson wrote:
> Package: exim4
> Odd, something is out of sync:
> The following packages have unmet dependencies:
> exim4 : Depends: exim4-base (< 4.92~RC4-2.1) but 4.92~RC4-3 is to be
> installed
> The following actions will resolve these dependencies:
> Remove
On 2019-01-11 Daniel Kahn Gillmor wrote:
> On Thu 2019-01-10 21:48:22 +, David Woodhouse wrote:
>> On Thu, 2019-01-10 at 15:53 -0500, Daniel Kahn Gillmor wrote:
>>> what's the advantage of using alternatives instead of a package-
>>> specific displacement?
>> None really, as long as you put
Control: forwarded -1
http://lists.nongnu.org/archive/html/lynx-dev/2018-12/msg9.html
On 2019-01-10 Alex Bernier wrote:
> Package: lynx
> Version: 2.8.9rel.1-2
> Severity: normal
> Dear Maintainer,
> Lynx fails to connect on some websites using the HTTPS protocol.
> For example "lynx
On 2019-01-03 Andreas Metzler wrote:
> On 2019-01-03 me wrote:
> > Package: locate
> > Version: 4.4.2-9+b1
> > Severity: normal
> > instead of including the paths handed over through --localpath, oder
> > instead of following the paths edscribed in updatedb.con
On 2019-01-03 me wrote:
> Package: locate
> Version: 4.4.2-9+b1
> Severity: normal
> instead of including the paths handed over through --localpath, oder
> instead of following the paths edscribed in updatedb.conf, updatedb
> produces an error, that the variable does not exist, or the switch in
On 2018-12-29 "Matteo F. Vescovi" wrote:
> Andreas,
> I'll open a specific transition bug report for that, once I've tested all
> r-deps but not earlier.
> Thus, I'll leave this bug report closed since it tracks another issue (or
> feature, at your choice ;) ).
I do not understand your
On 2018-12-27 "Matteo F. Vescovi" wrote:
> Hi!
> On 2018-12-27 at 19:38 (+01), Eric Valette wrote:
>> Package: libilmbase23
>> Version: 2.3.0-3
>> Severity: critical
>> Justification: breaks unrelated software
> [...]
> Well, 2.3.0-3 revision is still in the experimental suite.
> That's the
On 2018-12-18 Andreas Metzler wrote:
> On 2018-12-17 Jonas Smedegaard wrote:
[...]
> > The hosts I experienced problems with are mail.jones.dk and
> > mail.homebase.dk - both running Postfix on Debian stable (which made me
[...]
> Thanks! FWIW as a temporary workaround yo
Control: submitter -1 lionel.si...@ulb.ac.be
[resent to (googled) submitter address]
On 2018-12-19 Lionel wrote:
> Package: libgnutls30
> Version: 3.6.5-2
> Severity: normal
> Tags: upstream
> Hi
> My problem appeared with the recent upgrade of libgnutls30 which jumped from
> version
On 2018-12-19 Lionel wrote:
> Package: libgnutls30
> Version: 3.6.5-2
> Severity: normal
> Tags: upstream
> Hi
> My problem appeared with the recent upgrade of libgnutls30 which jumped from
> version 3.5.19-1+b1 to 3.6.5-2 (i am using sid).
> With this new library when I try to connect to my
On 2018-12-17 Jonas Smedegaard wrote:
> Quoting Andreas Metzler (2018-12-17 19:37:05)
[msmtp / GnuTLS 3.6 breaks]
>> FWIW I have had successful connections against exim4 (gnutls 3.5 and
>> 3.6). Which host are you trying to connect to?
> Sorry for exaggerating!
Not at a
Package: libgnutls30
Version: 3.6.5-2
Severity: serious
Justification: maintainer's opinion
gnutls 3.6.5-2 would be a candidate for testing migration tomorrow ("Too
young, only 1 of 2 days old"). This is too quick, the changes require
more testing in sid.
cu Andreas
--
`What a good friend you
Control: reassign -1 msmtp 1.6.7-1
Control: tags -1 fixed-upstream
On 2018-12-17 Jonas Smedegaard wrote:
> Package: libgnutls30
> Version: 3.6.5-2
> Severity: serious
> Justification: Policy 3.5
> I use msmtp, and it worked fine until few days ago,
> with msmtp 1.6.7-1 and libgnutls30
On 2018-12-11 "Torrance, Douglas" wrote:
[...]
> The new package is ready and pushed to git [1]. Andreas, are you able
> to review and sponsor?
[...]
Uploaded. I have also tagged the upload in GIT.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so
On 2018-12-11 "Torrance, Douglas" wrote:
> On 12/10/2018 08:54 PM, Doug Torrance wrote:
[...]
> > Indeed. This (and a couple other commits) hadn't been included in an
> > official release yet. I just fixed this, and version 0.9.11 is now
> > available [1]. I'll prepare a new Debian package
On 2018-12-09 Adrian Bunk wrote:
> Source: wmhdplop
> Version: 0.9.10-1
[...]
> devnames.c: In function 'device_id_from_name':
> devnames.c:207:13: warning: implicit declaration of function 'major'
> [-Wimplicit-function-declaration]
>*pmajor = major(stat_buf.st_rdev);
> ^
Source: ncbi-blast+
Version: 2.7.1-1
Severity: serious
Justification: fails to build from source
Hello,
ncbi-blast+ FTBFS on current sid:
LIBRARIES: build as dynamic by default
FEATURES: GCC MT LFS DLL DLL_BUILD unix WinMain Linux
PACKAGES:
enabled: Iconv Z BZ2 PCRE MBEDTLS GMP GMP NETTLE
On 2018-10-27 Mike Gabriel wrote:
> Control: tag -1 pending
> Hello,
> Bug #912028 in remote-logon-service reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below, and you can check the diff of the fix at:
>
:00 2001
From: Andreas Metzler
Date: Sun, 2 Dec 2018 08:00:20 +0100
Subject: [PATCH] New upstream release 3.4.1~rc1
List new symbols in symbol files.
---
debian/changelog | 8
debian/libhogweed4.symbols | 7 +++
debian/libnettle6.symbols | 1 +
3 files changed, 16 inserti
On 2018-11-18 Samuel Thibault wrote:
> Andreas Metzler, le dim. 18 nov. 2018 14:21:48 +0100, a ecrit:
>> no, applications should specify the version of gcrypt they require to
>> compile succcessfully as argument to gcry_check_version instead of the
>> version they
On 2018-11-18 Andreas Metzler wrote:
> On 2018-11-18 Samuel Thibault wrote:
> > Source: libgcrypt20
> > Version: 1.8.4-3
> > Severity: important
>> debian/rules uses:
>> dh_makeshlibs -V 'libgcrypt20 (>=1.8.0-0)'
>> But that is not tight
On 2018-11-18 Samuel Thibault wrote:
> Source: libgcrypt20
> Version: 1.8.4-3
> Severity: important
> Hello,
> debian/rules uses:
> dh_makeshlibs -V 'libgcrypt20 (>=1.8.0-0)'
> But that is not tight enough. Applications would typically call
> gcry_check_version (GCRYPT_VERSION)
> which
srv sshd[12920]: Libgcrypt warning: missing
>> initialization - please fix the application
>>
>> A bug with a fix has been logged at launchpad too [1].
> I'm not seeing this atm. Andreas (Metzler) should we still do s.th. like
> this:
>
> https://www.gnupg.org/d
Control: forwarded -1 https://savannah.gnu.org/bugs/index.php?54913
On 2018-10-28 "Mathieu Parent (Debian)" wrote:
> Package: findutils
> Version: 4.6.0+git+20181018-1
[...]
> The following testcase [1]:
> mkdir foo
> mknod foo/null c 1 3
> touch foo/bindmntoverfile
> mount --bind foo/null
On 2018-10-27 Antoine Beaupré wrote:
> Patch looks good to me.
> I've merged the patch in the tree, and will upload a new version.
Hello,
Did you grab the second version, which also fixes libotr5-dev
dependency and not only the b-d?
> Do you mind canceling yours?
I have just uploaded the
Source: remote-logon-service
Version: 1.0.2.90-1
Severity: important
Control: block 878654 by -1
remote-logon-service build-depends on libgcrypt11-dev. This is a
transition package, please use libgcrypt20-dev instead.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other
Control: notfound 912027 17.08.3-1
Control: unarchive 864108
Control: forcemerge 864108 912027
Control: archive 864108
On 2018-10-27 Andreas Metzler wrote:
> Source: ktp-common-internals
> Version: 17.08.3-1
> Severity: important
> Control: block 878654 by -1
> ktp-common-
Source: ktp-common-internals
Version: 17.08.3-1
Severity: important
Control: block 878654 by -1
ktp-common-internals build-depends on libgcrypt11-dev. This is a
transition package, please use libgcrypt20-dev instead.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other
On 2018-10-27 Andreas Metzler wrote:
> Dear maintainer,
> I've prepared an NMU for libotr (versioned as 4.1.1-2.1) and
> uploaded it to DELAYED/15.
[...]
Hello,
Corrected NMUdiff (also fixing dependency) attached.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin.
@@ -1,3 +1,11 @@
+libcommoncpp2 (1.8.1-6.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * (Build-)Depend on libgcrypt20-dev instead of (dummy transition
+package) libgcrypt11-dev.
+
+ -- Andreas Metzler Sat, 27 Oct 2018 13:05:39 +0200
+
libcommoncpp2 (1.8.1-6.1) unstable; urgency
On 2018-10-27 Javier Fernandez-Sanguino wrote:
> On Sat, 27 Oct 2018 at 09:15, Andreas Metzler wrote:
>> I've prepared an NMU for chntpw (versioned as 1.0-1.1) and
>> uploaded it to DELAYED/15. Please feel free to tell me if I
>> should delay it longer.
> De
On 2018-10-27 John Paul Adrian Glaubitz wrote:
> On 10/27/18 11:33 AM, Andreas Metzler wrote:
>> I've prepared an NMU for linux-minidisc (versioned as 0.9.15-1.1) and
>> uploaded it to DELAYED/15. Please feel free to tell me if I
>> should delay it longer.
> This must hav
transition package)
+libgcrypt11-dev. Closes: #864111
+
+ -- Andreas Metzler Sat, 27 Oct 2018 11:46:51 +0200
+
libccrtp (2.0.9-2.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru libccrtp-2.0.9/debian/control libccrtp-2.0.9/debian/control
--- libccrtp-2.0.9/debian/control 2015-08
transition package)
+libgcrypt11-dev. Closes: #864141
+
+ -- Andreas Metzler Sat, 27 Oct 2018 11:43:28 +0200
+
yubiserver (0.6-3) unstable; urgency=high
* Upgrade automake.
diff -Nru yubiserver-0.6/debian/control yubiserver-0.6/debian/control
--- yubiserver-0.6/debian/control 2015-06-29 10:39
-maintainer upload.
+ * B-d on libgcrypt20-dev instead of (dummy transition package)
+libgcrypt11-dev. Closes: #864095
+
+ -- Andreas Metzler Sat, 27 Oct 2018 11:39:57 +0200
+
cadaver (0.23.3-2) unstable; urgency=low
* debian/control, debian/rules:
diff -u cadaver-0.23.3/debian/control
transition package)
+libgcrypt11-dev. Closes: #864125
+
+ -- Andreas Metzler Sat, 27 Oct 2018 11:35:03 +0200
+
netatalk (2.2.6-1) unstable; urgency=medium
[ upstream ]
diff -Nru netatalk-2.2.6/debian/control netatalk-2.2.6/debian/control
--- netatalk-2.2.6/debian/control 2017-07-30 20:08
upload.
+ * B-d on libgcrypt20-dev instead of (dummy transition package)
+libgcrypt11-dev. Closes: #864122
+
+ -- Andreas Metzler Sat, 27 Oct 2018 11:27:32 +0200
+
linux-minidisc (0.9.15-1) unstable; urgency=medium
* New upstream release.
diff -Nru linux-minidisc-0.9.15/debian/control
on libgcrypt20-dev instead of (dummy transition package)
+libgcrypt11-dev. Closes: #864139
+
+ -- Andreas Metzler Sat, 27 Oct 2018 09:52:54 +0200
+
uswsusp (1.0+20120915-6.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru uswsusp-1.0+20120915/debian/control uswsusp-1.0+20120915
transition package)
+libgcrypt11-dev. Closes: #864103
+
+ -- Andreas Metzler Sat, 27 Oct 2018 09:47:18 +0200
+
freeipmi (1.5.7-2) unstable; urgency=medium
* upload to unstable
diff -Nru freeipmi-1.5.7/debian/control freeipmi-1.5.7/debian/control
--- freeipmi-1.5.7/debian/control 2017-10-26 12
package)
+libgcrypt11-dev. Closes: #864116
+
+ -- Andreas Metzler Sat, 27 Oct 2018 09:43:55 +0200
+
libmtp (1.1.13-1) unstable; urgency=medium
* Imported Upstream version 1.1.13
diff -Nru libmtp-1.1.13/debian/control libmtp-1.1.13/debian/control
--- libmtp-1.1.13/debian/control 2017-04-16
package)
+libgcrypt11-dev. Closes: #864118
+
+ -- Andreas Metzler Sat, 27 Oct 2018 09:40:14 +0200
+
libquvi (0.9.3-1.2) unstable; urgency=medium
[ Andreas Henriksson ]
diff -Nru libquvi-0.9.3/debian/control libquvi-0.9.3/debian/control
--- libquvi-0.9.3/debian/control 2016-02-18 17:52
--- chntpw-1.0/debian/changelog
+++ chntpw-1.0/debian/changelog
@@ -1,3 +1,11 @@
+chntpw (1.0-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * B-d on libgcrypt20-dev instead of (dummy transition package)
+libgcrypt11-dev. Closes: #864097
+
+ -- Andreas Metzler Sat, 27 Oct 2018 09
@@ -1,3 +1,11 @@
+libotr (4.1.1-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * B-d on libgcrypt20-dev instead of (dummy transition package)
+libgcrypt11-dev. Closes: #864093
+
+ -- Andreas Metzler Sat, 27 Oct 2018 09:01:03 +0200
+
libotr (4.1.1-2) unstable; urgency=medium
/changelog 2018-10-27 08:56:44.0 +0200
@@ -1,3 +1,10 @@
+openvpn-auth-radius (2.1-6.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * B-d on libgcrypt20-dev instead of libgcrypt11-dev. Closes: #864127
+
+ -- Andreas Metzler Sat, 27 Oct 2018 08:56:44 +0200
+
openvpn-auth-radius (2.1-6
of libgcrypt11-dev. Closes: #864117
+
+ -- Andreas Metzler Sat, 27 Oct 2018 08:49:22 +0200
+
libpam-ccreds (10-6) unstable; urgency=low
* [2baa623] We don't need automake nor autoconf to build.
diff -Nru libpam-ccreds-10/debian/control libpam-ccreds-10/debian/control
--- libpam-ccreds-10/debian
of libgcrypt11-dev. Closes: #864123
+
+ -- Andreas Metzler Sat, 27 Oct 2018 08:45:22 +0200
+
mcabber (1.1.0-1) unstable; urgency=medium
* New upstream version
diff -Nru mcabber-1.1.0/debian/control mcabber-1.1.0/debian/control
--- mcabber-1.1.0/debian/control 2018-02-15 00:41:14.0 +0100
+
+ -- Andreas Metzler Sat, 27 Oct 2018 08:38:18 +0200
+
yubikey-server-c (0.5-1) unstable; urgency=low
* New upstream release:
diff -u yubikey-server-c-0.5/debian/control yubikey-server-c-0.5/debian/control
--- yubikey-server-c-0.5/debian/control
+++ yubikey-server-c-0.5/debian/control
@@ -2,7
-dev. Closes: #864109
+
+ -- Andreas Metzler Sat, 27 Oct 2018 08:31:08 +0200
+
kvpnc (0.9.6a-4) unstable; urgency=medium
* Team upload.
diff -Nru kvpnc-0.9.6a/debian/control kvpnc-0.9.6a/debian/control
--- kvpnc-0.9.6a/debian/control 2016-02-14 10:48:39.0 +0100
+++ kvpnc-0.9.6a/debian
-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * B-d on libgcrypt20-dev instead of libgcrypt11-dev. Closes: #864098
+
+ -- Andreas Metzler Sat, 27 Oct 2018 08:24:18 +0200
+
clamz (0.5-2) unstable; urgency=medium
* Build-Depends on pkg-config to fix FTBFS. Closes: #747769.
diff
Control: forwarded 910835 https://gitlab.com/gnutls/gnutls/issues/593
On 2018-10-12 Dimitri John Ledkov wrote:
> On Thu, 11 Oct 2018 23:46:17 +0100 Dimitri John Ledkov
> wrote:
> > Package: libgnutls30
> > Version: 3.6.4-2
[...]
> > $ elinks -dump https://google.com
> > ELinks: SSL error
>
On 2018-10-16 Andreas Metzler wrote:
[...]
> Okay, confirmed. So the failing autpkgtest is fixed by flann -6 and I
> only need to fix hugin's FTBFS.
... which is fixed with the latest hugin upload.
On 2018-10-15 Jochen Sprickerhof wrote:
> * Andreas Metzler [2018-10-15 17:23]:
[...]
> > Anyway, this change seems to be a ABI break for flann, I guess it will
> > need to add a
> > Breaks: hugin (<< fixed-version~)
> I don't think that's needed, flann_cpp l
On 2018-10-12 Dimitri John Ledkov wrote:
[...]
> gnutls_priority_set_direct(*state, "NORMAL:-CTYPE-OPENPGP", NULL)
> which used to pass fine in 3.5. (aka use normal, but disable OPENPGP
> certs), with with 3.6 this errors out, because OPENPGP certs are
> disabled now by default but that
On 2018-10-14 Jochen Sprickerhof wrote:
> * Paul Gevers [2018-10-14 21:47]:
>> Source: flann, hugin
>> Control: found -1 flann/1.9.1+dfsg-4
>> Control: found -1 hugin/2018.0.0+dfsg-2
[...]
>> With a recent upload of flann the autopkgtest of hugin fails in testing
>> when that autopkgtest is run
HA.patch
++ 39_02-dummy_wait-always-hash-the-same-amount-of-blocks-tha.patch
++ 39_03-cbc_mac_verify-require-minimum-padding-under-SSL3.0.patch
++ 39_04-hmac-sha384-and-sha256-ciphersuites-were-removed-fro.patch
++ 39_05-tests-pkcs12_encode-fix-test-for-SHA512.patch
+
+ -- Andreas Metzler
On 2018-09-29 Adrian Bunk wrote:
> Source: plotutils
> Version: 2.6-9
> Severity: serious
> Tags: ftbfs
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/plotutils.html
> ...
> FAIL: plot2hpgl
> ===
> FAIL plot2hpgl.test (exit status: 1)
That is a strange one.
On 2018-09-30 Andreas Metzler wrote:
> On 2018-09-29 Adrian Bunk wrote:
>> Source: plotutils
>> Version: 2.6-9
>> Severity: serious
>> Tags: ftbfs
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/plotutils.html
>> ...
>>
On 2018-09-29 Adrian Bunk wrote:
> Source: plotutils
> Version: 2.6-9
> Severity: serious
> Tags: ftbfs
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/plotutils.html
> ...
> FAIL: plot2hpgl
> ===
> FAIL plot2hpgl.test (exit status: 1)
[...]
Oi, a straight
On 2018-09-01 Adrian Bunk wrote:
[...]
> Breaks+Replaces on (<< ${binary:Version}) is wrong when
> the broken package is binary-all.
> And these versions shouldn't be generated here at all,
> these should be the fixed versions when the contents
> moved to libefl-all-dev.
You are obviously
On 2018-08-23 Andreas Metzler wrote:
[...]
> Almost, it is caused by upgrading automake. Building with automake
> 1:1.16.1-1 fails, downgrading to 1:1.15.1-3.1 lets the build succeed.
> Which seems to have hit other packages, too. With one report (#906774)
> reassigned to autom
Control: affects 906774 src:libtasn1-6
On 2018-08-21 Helmut Grohne wrote:
> Source: libtasn1-6
> Version: 4.13-3
> Severity: serious
> Tags: ftbfs
> User: helm...@debian.org
> Usertags: rebootstrap
> Doing an arch-only build of libtasn1-6 on amd64 fails
[...]
> builds on the buildds did not
Control: reassign -1 gnutls28
Control: forcemerge 863147 905272
On 2018-08-02 Renge wrote:
> Package: guile-gnutls
> Severity: wishlist
> Dear Maintainer,
> The guile-gnutls package is absent, yet it is still included in the
> gnutls distribution.
> Would it be packaged again?
Hello,
no I do
On 2018-07-26 Noël Köthe wrote:
> Source: gnutls28
> Version: 3.6.3-1
> Severity: wishlist
> Dear Maintainer,
> with the TLS 1.3 support in the 3.6.3 version maybe you want to add it
> to the description. See attached patch.
Thanks for the reminder, I will check what was added and removed (SSL
Control: tags -1 patch fixed-upstream
On 2018-07-22 Juhani Numminen wrote:
> Control: forwarded -1 https://github.com/ukoethe/vigra/issues/414
> On Fri, 04 May 2018 12:22:30 + Matthias Klose wrote:
> > Package: src:libvigraimpex
> > Version: 1.10.0+git20160211.167be93+dfsg-5
[...]
> >
On 2018-07-08 Niko Tyni wrote:
> Package: hugin
> Version: 2018.0.0+dfsg-1
> The autopkgtest checks of this package write to $HOME, and fail if that
> is not writable. They don't clean after themselves properly but leave
> ~/.hugindata/camlens.db around.
Hello Niko,
I have never cared or
On 2018-06-29 Mark Dickie wrote:
> Package: terminology
> Version: 1.2.1-1
> Severity: important
> Dear Maintainer,
> mark@plata:~$ terminology
> terminology: error while loading shared libraries: libelementary.so.1: cannot
> open shared object file: No such file or directory
> Package
On 2018-06-24 sergio wrote:
> On 24/06/2018 04:11, Ross Vandegrift wrote:
>>> could you update source to "enlightenment" as e17 is outdated.
>> We discussed this a while back, and decided to leave it. See:
>> https://alioth-lists.debian.net/pipermail/pkg-e-devel/2015-November/002442.html
>
On 2018-06-20 Ross Vandegrift wrote:
> On Tue, Jun 19, 2018 at 07:30:48PM +0200, Andreas Metzler wrote:
> > I looked at it and did not have any alternative bright ideas. There is
> > just a single manual (non-shlibs) dependency involved and it is there
> > for a good reason.
On 2018-06-16 Ross Vandegrift wrote:
> On Fri, Jun 15, 2018 at 09:18:59PM +0200, Bill Allombert wrote:
> > There is a circular dependency between libecore-input1, libecore-x1,
> > libevas1 and libevas1-engines-x:
> Dang, thanks for the heads up Bill.
> Andreas - the change I proposed for the
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libgcrypt20, this is a upstream bugfix/security
release of the stable branch, fixing CVE-2018-0495.
On 2018-06-11 積丹尼 Dan Jacobson wrote:
> Why use bash at all if e.g.,
> $ checkbashisms /usr/sbin/update-exim4.conf.template
> could not find any possible bashisms in bash script
> /usr/sbin/update-exim4.conf.template
> means one can just use #!/bin/sh ?
Hello,
Exim, does use #!/bin/sh.
On 2018-06-11 Colin Watson wrote:
> On Sun, Jun 10, 2018 at 04:04:13PM +0200, Andreas Metzler wrote:
[...]
> > yes, resetting IFS to its default value in confmodule helps.
> Thanks. For completeness, could you try this variant patch? If shells
> are going to be unreliable ab
On 2018-06-10 Colin Watson wrote:
> On Sun, Jun 10, 2018 at 03:03:28PM +0200, Andreas Metzler wrote:
>> I have tried debugging the issue to get a minimal testcase. I have had
>> some success. The issue is triggered by debconf.
>> /usr/share/debconf/confmodule changes IFS
Hello bash maintainers (debconf Cced),
I have tried debugging the issue to get a minimal testcase. I have had
some success. The issue is triggered by debconf.
/usr/share/debconf/confmodule changes IFS to \n and with bash5 this
change is persistent and breaks the maintainerscript. i.e. installing
On 2018-06-10 Eric Valette wrote:
> On 6/10/18 11:57 AM, Eric Valette wrote:
>> On 6/10/18 11:35 AM, Andreas Metzler wrote:
>>> exports both dc_directives and any variable listed in dc_directives,
>>> i.e. any external command will see both ${dc_directives} and
>
On 2018-06-10 Eric Valette wrote:
> On 6/10/18 11:35 AM, Andreas Metzler wrote:
> > exports both dc_directives and any variable listed in dc_directives,
> > i.e. any external command will see both ${dc_directives} and
> > ${dc_eximconfig_configtype} et al.
> right but d
On 2018-06-10 Eric Valette wrote:
> On 6/10/18 10:51 AM, Eric Valette wrote:
>> On 6/10/18 10:34 AM, Eric Valette wrote:
>>> line 330 :export dc_directives ${dc_directives}
>> Shodul be export dc_directives=${dc_directives} as far as I understand.
[...]
> and it worked. But I still think there
On 2018-06-10 Eric Valette wrote:
> On 6/10/18 10:59 AM, Eric Valette wrote:
> > On 6/10/18 10:51 AM, Eric Valette wrote:
> > 2) mv /etc/exim4/update-exim4.conf.conf
> > /etc/exim4/update-exim4.conf.conf.old
exactly what I wrote ;-)
"installs/configures successfully once the broken
801 - 900 of 3558 matches
Mail list logo
