peter green writes:
> I then had a poke around and noticed that an "opensaml" source package
> had recently been uploaded that seems to have taken over most of the
> binary package names from opensaml2. If the intention is for opensaml
> to replace opensaml2 can you file a removal request?
Hi,
Andreas Ley writes:
> Did not realize there now is a _shibd user that needs to access the
> keys since on jessie, shibd automatically runs as root in such a
> situation.
> [...]
> On stretch, there is a /lib/systemd/system/shibd.service which misses
> both the automatism and the warning.
Hi
Source: xml-security-c
Version: 1.2.1-3
Severity: important
Tags: patch upstream security
Forwarded: https://issues.apache.org/jira/browse/SANTUARIO-496
Control: fixed 2.0.2-1
Particular KeyInfo combinations result in incomplete DSA key structures
that OpenSSL can't handle without crashing.
Very
wagner.fer...@kifu.gov.hu (Ferenc Wágner) writes:
> Christian Fischer writes:
>
>> On Fri, 03 Aug 2018 14:42:16 +0200 wf...@niif.hu (Ferenc Wágner) wrote:
>>
>>> Unfortunately the CVE hasn't arrived yet; I'll
>>> forward it to you once it does. My acknowl
Christian Fischer writes:
> On Fri, 03 Aug 2018 14:42:16 +0200 wf...@niif.hu (Ferenc Wágner) wrote:
>
>> Unfortunately the CVE hasn't arrived yet; I'll
>> forward it to you once it does. My acknowledgement mail is of
>> subject "CVE Request 548000 for CVE
Michail Bachmann writes:
> # apt install libapache2-mod-shib2
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the
Package: debhelper
Version: 11.4
Severity: normal
Dear Maintainer,
I was forced to switch to experimental compat level 12 by #887904, and
immediately got several
package-contains-empty-directory usr/lib/debug/
Lintian warnings. After some investigation, I suspect it's because
dh_strip issues
Package: dpkg
Version: 1.18.25
Severity: minor
Dear Maintainer,
If the package name is provided on the dpkg_maintscript_helper command
line, the DPKG_MAINTSCRIPT_HELPER variable is still used for generating
debug output, which gets broken without warning if the variable isn't set
(for example
Package: apache2
Severity: minor
Dear Maintainer,
man a2enmod does not document the --force (-f) option.
Please consider describing its use.
--
Thanks,
Feri.
Control: severity -1 normal
Control: tag -1 + upstream
Valentin Vidic writes:
> On Fri, Jul 06, 2018 at 12:50:42PM +0200, Ferenc Wágner wrote:
>
>> Thanks for the report. I've been pretty busy with other tasks, but I'll
>> check this out as soon as possible, your report isn't
Moritz Mühlenhoff writes:
> Please build with -sa (as the tarball is new in stretch-security) and
> upload to security-master.
Source-only upload done, with orig tarball but without buildinfo.
Hope it's fine. Unfortunately the CVE hasn't arrived yet; I'll
forward it to you once it does. My
/projects/SANTUARIO/issues/SANTUARIO-491
+CVE: not assigned yet
+Thanks to Scott Cantor (Closes: #905332)
+
+ -- Ferenc Wágner Fri, 03 Aug 2018 11:32:52 +0200
+
xml-security-c (1.7.3-4) unstable; urgency=medium
[ Etienne Dysli Metref ]
diff -Nru xml-security-c-1.7.3/debian/gbp.conf
Package: src:xml-security-c
Severity: important
Tags: security
This is a security tracking bug.
Original report:
https://issues.apache.org/jira/projects/SANTUARIO/issues/SANTUARIO-491
The issue is null pointer dereference in the library, which happens to
mean a trivial remote DoS (shibd crash)
Dimitri John Ledkov writes:
> xml-security-c-2.0 is out and appears to compile fine against openssl
> 1.1. Is that the upstream release we were waiting to package?
Yes. Actually, the full SP3 stack was released almost two weeks ago, so
the lights are green, we're figuring out the transition
Hi Jason,
Thanks for the report. I've been pretty busy with other tasks, but I'll
check this out as soon as possible, your report isn't forgotten. I ask
for you patience till then.
--
Regards,
Feri
Andreas Beckmann writes:
> Unpacking cluster-glue-dev (1.0.12-9) ...
> dpkg: error processing archive
> /tmp/apt-dpkg-install-iCxNhp/11-cluster-glue-dev_1.0.12-9_amd64.deb
> (--unpack):
>trying to overwrite '/usr/lib/heartbeat/plugins/compress/bz2.a', which is
> also in package
wf...@niif.hu (Ferenc Wágner) writes:
> Don Armstrong writes:
>
>> On Thu, 31 May 2018, Ferenc Wágner wrote:
>>
>>> If (for example) one sets "server-user" to an invalid user name in the
>>> config file, unscd fails to start up but "syst
Don Armstrong writes:
> On Thu, 31 May 2018, Ferenc Wágner wrote:
>
>> If (for example) one sets "server-user" to an invalid user name in the
>> config file, unscd fails to start up but "systemctl start unscd" does
>> not report this failure. T
Package: unscd
Version: 0.53-1
Severity: minor
Tags: patch
Dear Maintainer,
If (for example) one sets "server-user" to an invalid user name in the
config file, unscd fails to start up but "systemctl start unscd" does
not report this failure. This is a shortcoming of Type=simple services.
Please
Michael Stone writes:
> On Thu, May 17, 2018 at 04:15:44PM +0200, you wrote:
>
>> Michael Stone writes:
>>
>>> It would not--POSIX does not disallow the . syntax.
>>
>> (This is not my point, but in my reading
>>
Michael Stone <mst...@debian.org> writes:
> On Thu, May 17, 2018 at 02:56:00PM +0200, Ferenc Wágner wrote:
>
>> When asked to enable user names containing dots, I encountered
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604242#20.
>> When do you think chow
Package: coreutils
Version: 8.26-3
Severity: wishlist
Dear Maintainer,
When asked to enable user names containing dots, I encountered
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604242#20.
When do you think chown could stop accepting the dot separator?
While it could break old scripts
Christian Ehrhardt writes:
> While not crit since all is in sid, but for backports or other re-users
> (and for correctness) I wonder if the build depedency should be versioned
> to libqb >=1.0.3-1
I pondered about it... we can't bump dependency versions for
No news yet.
--
Feri
Nish Aravamudan writes:
>> Nishanth Aravamudan writes:
>>
>>> Now, neither of these actually fix the existing packages
>>> unfortunately, which will stop pacemaker on the upgrade to a fixed
>>> package and thus stop pacemaker. I have
Nish Aravamudan writes:
> I spent some time reading the manpage myself and this is how I
> interpret the relevant section(s):
>
> Requires=
>Configures requirement dependencies on other units. If this unit
>gets activated, the units
Package: autopkgtest
Version: 5.3~bpo9+1
Severity: normal
Dear Maintainer,
The "autopkgtest-build-lxc debian sid" command exited with message
Timed out waiting for container to start network-online.target
I found that lxc-attach was in T state, stopped waiting for terminal
input (SIGTTIN).
Control: fixed -1 2.4.4-1
Nishanth Aravamudan writes:
> I believe this is because the prerm of corosync.service [...]
> unconditionally stops corosync for all Debian and Ubuntu releases
> (as the init script is installed even if unused by systemd). When
> corosync
Unfortunately the Alioth list migration delayed this mail long enough to
let me do the security upload without closing this bug in the changelog.
You may want to fill that in during the DSA workflow (if possible).
--
Regards,
Feri
Package: slapd
Version: 2.4.44+dfsg-5+deb9u1
Severity: normal
Dear Maintainer,
A partial replica slave crashed with
Apr 3 14:53:51 birch kernel: [1906479.552078] slapd[4515]: segfault at 4c ip
7f71abdbfc9b sp 7f716f184780 error 4 in
back_mdb-2.4.so.2.10.7[7f71abdb+39000]
wf...@niif.hu (Ferenc Wágner) writes:
> Nobody objected, so let's hold out until libcurl breaks us for good or
> OpenSSL 1.1 support emerges...
According to the latest comment on
https://issues.shibboleth.net/jira/browse/CPPXT-110
upstream support is getting there.
Scott, have you perha
Control: fixed 869986 1.1.18~rc3-1
Control: done 869986
Pacemaker builds again for some time, looks like the new upload was
enough to fix this breakage after all.
--
Feri
Control: tags -1 - moreinfo
Chris Lamb writes:
> We currently look for paths called "examples" under usr/share/doc/$pkg.
> What are you suggesting we look for instead? :)
Hi Chris,
I suggest to drop the $pkg constraint. For example, libwhatever-doc may
install examples into
Package: lintian
Version: 2.5.79
Severity: normal
Dear Maintainer,
Debian Policy Manual §12.3 recommends installing documentation files
(and thus examples) under the main package documentation directory
instead of the documentation directory of the separate -doc package.
However, current Lintian
Nobody objected, so let's hold out until libcurl breaks us for good or
OpenSSL 1.1 support emerges...
Control: tags -1 - moreinfo
"Adam D. Barratt" writes:
> On Wed, 2018-02-28 at 06:45 +0100, Salvatore Bonaccorso wrote:
>
>> FTR, there was a xmltooling DSA yesterday including the fix. But I
>> guess the basic question remains if xmltooling still can be updated
>> to
"Debian Bug Tracking System" writes:
> For the sake of others who upload a backport-relying-on-backports, the
> incantation is:
>
> sbuild --build-dep-resolver=aptitude -s -d stretch-backports -c
> stretch-amd64-sbuild wine_3.0-1~bpo9+1.dsc
You can leave out the -c
Package: debian-policy
Version: 4.1.3.0
Severity: minor
Dear Maintainers,
https://www.debian.org/doc/debian-policy/#main-building-script-debian-rules
reads:
clean (required) This must undo any effects that the build and binary targets
may have had [...]
I think the line break should happen
I'm still behind with backports due to the recent security release.
When keeping the stack in testing starts blocking independent work,
please notify me and I'll switch to asking for backports exceptions.
--
Feri
Chad William Seys writes:
> I would like to take you up on the offer to backport to wheezy, it
> it is still on the table. Please let me know how to download.
> Obviously we'll upgrade the server ASAP, but that won't be for a bit.
> Sorry for the extra bother!
I
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Dear Release Team,
The Security Team advised that CVE-2018-0486 should be fixed by a stable
update, because it isn't exploitable in the stretch version of the
Shibboleth stack,
Control: tag -1 + wontfix
cws...@physics.wisc.edu writes:
> Could the security fix for CVE-2018-0486 in 1.5.3+deb8u2 be pretty
> please backported to wheezy?
Hi,
It would be easy to backport, but we couldn't upload the results, because
wheezy-backports closed with the release of stretch. If a
Mathieu Malaterre <ma...@debian.org> writes:
>>> Ferenc Wágner <wf...@niif.hu> writes:
>>>
>>>> The test looks for the exported API function names in the text (T)
>>>> section, but the ppc64 nm reports them in the data (D) section:
>&
Package: git-buildpackage
Version: 0.9.6
Severity: wishlist
Hi Guido,
https://manpages.debian.org/unstable/git-buildpackage/gbp-import-orig.1.en.html
says in the description of the --merge-mode option:
[...] while keeping the current head as well as the newly important trees
as parents of
On Thu, 4 Jan 2018 23:11:23 +0100 Lukas Slebodnik
wrote:
> glibc was recently updates in debian unstable to 2.26-1 and revealed bug
> in valgrind. Fortunately it is already fixed in valgrind upstream.
> https://bugs.kde.org/show_bug.cgi?id=381289
>
> I would
u...@debian.org (Aaron M. Ucko) writes:
> Ferenc Wágner <wf...@niif.hu> writes:
>
>> I wanted to, but hit some problem... Maybe failed to access a
>> porterbox. Anyway, that error does not make any sense, knet_handle_new
>> is the first thing the tests call, s
"Aaron M. Ucko" writes:
> The build of kronosnet for ppc64 (admittedly not a release
> architecture) failed:
>
> ../../libknet/tests/api-test-coverage ../.. ../..
> Checking for exported symbols NOT available in header file
> Checking for symbols in header file NOT
"Aaron M. Ucko" writes:
> The build of kronosnet for hurd-i386 (admittedly not a release
> architecture) failed:
>
> checking for netinet/sctp.h... no
> configure: error: "missing required SCTP headers"
>
> Please consider restricting the package's Architecture setting
>
"Aaron M. Ucko" writes:
> The build of kronosnet for x32 (admittedly not a release architecture)
> ran into errors in api_knet_send_crypto_test per the below excerpts from
> https://buildd.debian.org/status/fetch.php?pkg=kronosnet=x32=1.0-1=1515554249=0
>
> Could you please take
Package: src:lz4
Severity: wishlist
Dear Maintainer,
When do you plan to upload the new lz4 package to unstable?
Would it start a difficult transition, or is there some other
reason for you keeping it in experimental?
I'd be happy to use it in Kronosnet, but I had to disable LZ4 support in
it
Chris Lamb writes:
> Thanks for the report. I have fixed this in Git:
>
> https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=28028299a402eb8d87176a537facc437ab89b6c6
Wow, that was quick!
--
Thanks,
Feri
Package: lintian
Version: 2.5.67
Severity: normal
Dear Maintainer,
My package won the
E: shibboleth-sp2 source: missing-notice-file-for-apache-license doc/NOTICE.txt
Lintian error even though all its binary packages carry NOTICE.txt due to
dh_installdocs -A doc/NOTICE.txt [...]
Looking at
I'd like to keep the current Shibboleth stack in testing at least until
I manage to upload the last backports.
--
Feri
Control: tag -1 + patch
This patch seems to help:
--- openvswitch-2.3.0+git20140819/lib/odp-util.c.orig 2017-12-10 15:34:48.312913875 +0100
+++ openvswitch-2.3.0+git20140819/lib/odp-util.c 2017-12-10 16:03:41.589150537 +0100
@@ -2967,13 +2967,20 @@
enum ovs_key_attr expected_bit = 0xff;
Oh, the above killer.c code misses the IFF_NO_PI flag, but it happens to
make no difference in this case.
--
Feri
Control: tag -1 - security
On Fri, 08 Dec 2017 17:19:21 +0100 wf...@niif.hu (Ferenc
=?utf-8?Q?W=C3=A1gner?=) wrote:
> This is a remote DoS vector in jessie, so adding the security tag.
It isn't /that/ remote, being exploitable from the LAN only. So I'm
removing the security tag after all.
--
Control: tag -1 + security
Simple reproducer attached.
This is a remote DoS vector in jessie, so adding the security tag.
--
Thanks,
Feri
/* ovs-vsctl add-br ovsbr
* then this crashes ovs-vswitchd (which restarts automatically)
*/
#include
#include
#include
#include
#include
#include
Sebastian Andrzej Siewior writes:
> this is a remainder about the openssl transition [0]. We really want to
> remove libssl1.0-dev from unstable for Buster. I will raise the severity
> of this bug to serious in a month. Please react before that happens.
Sorry, we can't
Ben Pfaff writes:
> What version of Open vSwitch is this?
The jessie version with the security update:
2.3.0+git20140819-3+deb8u1
I forgot to attach the related syslog excerpt:
Nov 30 23:06:42 vhbl08 kernel: [3400373.344953] traps: handler20[4173] general
protection ip:466280
Hi,
Yesterday an upstream switch reboot segfaulted all our ovs-vswitchd
instances at the same time. There's no MPLS or flow config in our OVS
setups, they run a bridge over a bond and several 802.1q interfaces. I
mention it here, though, as the backtrace starts similarly, so maybe
this is a
Emilio Pozuelo Monfort <po...@debian.org> writes:
> On 19/11/17 22:04, Ferenc Wágner wrote:
>
>> On Wed, 15 Nov 2017 20:08:28 + Bill Blough <de...@blough.us> wrote:
>>
>>> The package has been uploaded to unstable [...]
>>
>> xmltooling,
Package: file
Version: 1:5.30-1+deb9u1
Severity: normal
Dear Maintainer,
Please create an empty ELF shared object like this (needs libc6-dev):
$ gcc -shared -nostdlib -o dummy.so -Wl,--as-needed -lc
Now dummy.so has no program headers:
$ readelf -h dummy.so | fgrep program
Start of program
On Wed, 15 Nov 2017 20:08:28 + Bill Blough wrote:
> The package has been uploaded to unstable [...]
Dear Release Team,
xmltooling, opensaml2 and shibboleth-sp2 must be rebuilt again in this
order to correctly pick up the new xerces library.
Meanwhile I'd like to upload
"Cantor, Scott" <canto...@osu.edu> writes:
> On 11/17/17, 11:48 AM, "Pkg-shibboleth-devel on behalf of Ferenc Wágner"
> <pkg-shibboleth-devel-bounces+cantor.2=osu@lists.alioth.debian.org on
> behalf of wf...@niif.hu> wrote:
>
>> Now, th
Salvatore Bonaccorso writes:
> Thanks, need to check why my mail for 881857 did not went trough
> (since I retitled both with the CVE assignments).
I think you used the same bug number in both.
Now, this is still ongoing:
Package: vim
Version: 2:8.0.0197-4+deb9u1
Severity: normal
Dear Maintainer,
Please create /tmp/configure.ac with the following contents:
[AC_MSG_([yes])]
and position the cursor on the first character, the opening bracket.
This highlights the first closing bracket, right after "yes", instead
Control: forwarded -1 https://github.com/ClusterLabs/libqb/pull/269
"Manuel A. Fernandez Montecelo" writes:
> If upstream Hurd people were so sure about it I'd strongly consider to
> follow their advice.
That's the plan. Unfortunately, the POSIX interface defers
"Cantor, Scott" writes:
> On 10/30/17, 4:49 PM, "Sam Hartman" wrote:
>
>> My understanding is that the patches already exist, but effort didn't
>> exist within Debian to do a good job of taking those patches
>> ourselves at least the last time this was
Bill Blough writes:
> 3.2.0-1 has been uploaded to experimental.
Great, thank you very much!
--
Feri
Package: wnpp
Severity: wishlist
Owner: =?utf-8?q?Ferenc_W=C3=A1gner?=
* Package name: kronosnet
Version : 1.0 to be released this year
Upstream Author : Fabio M. Di Nitto
* URL : http://www.kronosnet.org
* License :
On Wed, 30 Aug 2017 10:04:01 -0400 Bill Blough wrote:
> Thanks for your report. I'm currently on vacation, but will work on
> updating the package as soon as I return.
Hi,
The next release of Apache Santuario (XML Security) will require Xerces
3.2. I'm already testing it,
Helmut Grohne <hel...@subdivi.de> writes:
> On Wed, Oct 11, 2017 at 03:24:50PM +0200, Ferenc Wágner wrote:
>
>> #hurd confirmed that this is a Hurd bug in glibc, and promised a fix it
>> in the next upload. So I guess an unconditional check for
>> _POSIX_MONOTO
wf...@niif.hu (Ferenc Wágner) writes:
> The configure check was added for Hurd support. Apparently, Hurd
> defines _POSIX_MONOTONIC_CLOCK to 200809L, returns the same value for
> a sysconf() query, but clock_getres (CLOCK_MONOTONIC, ) still fails
> with EINVAL.
Hi,
#hu
Helmut Grohne writes:
> libqb fails to cross build from source, because it uses an uncached
> AC_RUN_IFELSE for determining whether CLOCK_MONOTONIC works. That check
> is flawed in that availability of CLOCK_MONOTONIC is a runtime property
> and may change from system to
Control: tags -1 +moreinfo
Control: clone -1 -2
Control: retitle -2 libnss3-dev breaks the build
Roger Leigh writes:
> Please see the patches I attached to the upstream ticket here:
> https://issues.apache.org/jira/browse/SANTUARIO-471 which resolve a
> number of defects
On Sun, 09 Oct 2016 08:06:00 + Niels Thykier wrote:
> I will have a look at fixing the debhelper side of this, so it becomes
> less magic. As it is, I cannot quite grok the proposed solution in
> dh-exec - which I am pretty sure is no fault of dh-exec itself, but
> rather
Valentin Vidic writes:
> Right, the upstream is having problems with libqb, but maybe they don't
> see the problem with pacemaker libs if they are not checking the
> exported symbols.
There's no problem with the Pacemaker libs, the "missing" symbols are a
manifestation
Valentin Vidic writes:
> Seems to be related to binutils 2.29 problem reported here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1477354
Absolutely, thanks for this very good find, Valentin! These symbols
caused problems on non-x86 architectures before, and now
Package: git-ftp
Version: 1.3.1-1
Severity: normal
Tags: patch upstream
Forwarded: https://github.com/git-ftp/git-ftp/issues/377
Dear Maintainer,
Please consider this session:
$ git init
[...]
$ git config git-ftp.user myuser
$ git config git-ftp.url sftp://my.serv.er/~/www/foo
$ echo
Package: systemd
Version: 215-17+deb8u7
Severity: normal
Dear Maintainer,
man systemd-suspend.service says:
Immediately before entering system suspend and/or hibernation
systemd-suspend.service (and the other mentioned units, respectively)
will run all executables in
Package: icinga2
Version: 2.6.0-2
Severity: normal
Dear Maintainer,
After installing icinga2 and gdb, I get this:
$ /usr/sbin/icinga2 daemon -D AttachDebugger=true -D RunAsUser=wferi -D
RunAsGroup=wferi
[2017-06-26 14:51:46 +0200] information/cli: Icinga application loader
(version: r2.6.0-1)
Package: samhain
Severity: minor
Dear Maintainer,
The startup of Samhain is logged to the console like:
Starting (null)...
[...]
[ OK ] Started (null).
This happens because systemd uses the Short-Description from the
init script LSB headers here, but /etc/init.d/samhain does not
Package: stunnel4
Followup-For: Bug #782030
Here's a patch adding systemd Type=notify support:
--- a/src/ui_unix.c
+++ b/src/ui_unix.c
@@ -107,6 +107,9 @@
if(signal(SIGINT, SIG_IGN)!=SIG_IGN)
signal(SIGINT, signal_handler); /* fatal */
#endif
+#ifdef USE_SYSTEMD
+
Control: found -1 5.01-2
> When recompiled with SERIAL_CONSOLE_DEFAULT=1 and other settings in
> config.h the serial console works fine. However setting the
> parameters from the boot prompt with lilo (or pxelinux) does not.
I'm in the same situation with Syslinux: passing serial options on the
Package: mailman
Severity: minor
Tags: patch l10n upstream
Dear Maintainer,
The last sentence of /usr/share/mailman/hu/cronpass.txt goes like:
Kérdéseidet, problémáidat, megjegyzéseidet, egyéb mást a(z)
%(owner)s címre küld.
The last word misses a 'd' at the end, it should be 'küldd',
Package: debian-policy
Severity: minor
Dear Maintainer,
Your control file specifies
https://anonscm.debian.org/git/dbnpolicy/policy.git
as Vcs-Browser, but the gitweb interface gives "Bad object id:" messages
when clicking into the shortlog section. Please switch to
On Sat, 31 Dec 2016 23:33:13 -0800 Russ Allbery wrote:
> + To support merged-/usr systems, packages must not
> + install files in both path
Is there a reason to omit the leading slash in this construct? I think
I'd find /path more symmetric and thus easier to
Hi Christoph,
You seem to have stakes with PostgreSQL and also upload resource-agents
now and then: have you got plans for dealing with this issue?
--
Regards,
Feri
Apollon Oikonomopoulos writes:
> On 09:15 Thu 11 May, Christian Balzer wrote:
>
>> Firstly I recreated the initial state bu unmasking drbd and enabling
>> it, then reloading systemd.
>>
>> That find then gives us:
>> ---
>> /run/systemd/generator.late/drbd.service
>>
Apollon Oikonomopoulos writes:
> On 17:53 Wed 10 May , Christian Balzer wrote:
>
>> # systemctl disable drbd
>> drbd.service is not a native service, redirecting to systemd-sysv-install.
>> Executing: /lib/systemd/systemd-sysv-install disable drbd
>> insserv: warning:
Hi,
I'll start preparing a jessie backport soon.
If no complication arises, I'll simply upload it and close this bug.
--
Thanks,
Feri
Pavel Polacek writes:
> (gdb) bt
> #0 __lll_lock_wait () at
> ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
> #1 0x7f032831c479 in _L_lock_909 () from
> /lib/x86_64-linux-gnu/libpthread.so.0
> #2 0x7f032831c2a0 in __GI___pthread_mutex_lock
Ping?
--
Thanks,
Feri.
Package: ntp
Version: 1:4.2.6.p5+dfsg-7+deb8u2
Severity: important
Dear Maintainer,
Under systemd restarting the NTP daemon is racy, which can lead to a
silent failure to start a new instance of the daemon during upgrades.
The problem is that systemd has no separate restart action, just does
a
Hi,
How is this supposed to work now? On a fresh stretch install, with
/etc/ssh/sshd_config being identical to /usr/share/openssh/sshd_config,
dpkg-reconfigure openssh-server does not ask anything:
# DEBCONF_DEBUG=developer dpkg-reconfigure openssh-server
debconf (developer): starting
Source: unixodbc
Severity: wishlist
Dear Maintainer,
As noted in #843847, we use an unofficial backport of an unofficial
2.3.4 package. Now that you've kindly provided an official 2.3.4-1,
I'd like to switch to an official backport as well. Could you please
provide a jessie backport of it? Or
Control: reassing 849848 qa.debian.org
Simon Ruderich <si...@ruderich.org> writes:
> On Sun, Jan 01, 2017 at 12:06:39PM +0100, Ferenc Wágner wrote:
>
>> https://qa.debian.org/bls/bytag/I-no-compiler-commands.html says:
>>
>> Possible issues this might h
wf...@niif.hu (Ferenc Wágner) writes:
> Niels Thykier <ni...@thykier.net> writes:
>
>> Ferenc Wágner:
>>
>>> Thanks for re-closing this bug. Could you please help me understand why
>>> xml-security-c 1.7.3-4 hasn't migrated to testing yet, even th
Package: blhc
Severity: normal
Dear Maintainer,
https://qa.debian.org/bls/bytag/I-no-compiler-commands.html says:
Possible issues this might hint at:
* A package being Architecture: all, though it only contains architecture
independent data.
which I don't get. The very point of
Niels Thykier <ni...@thykier.net> writes:
> Ferenc Wágner:
>
>> Thanks for re-closing this bug. Could you please help me understand why
>> xml-security-c 1.7.3-4 hasn't migrated to testing yet, even though
>> https://qa.debian.org/excuses.php?package=xml-securi
101 - 200 of 303 matches
Mail list logo