Bug#791904: [HEADS-UP] libsystemd transition

[Alberto Gonzalez Iniesta]

On Sun, Sep 06, 2015 at 09:08:35PM +0200, Michael Biebl wrote:
> Am 06.09.2015 um 03:34 schrieb Michael Biebl:
> 
> > Fwiw, I tried the configuration snippet you posted earlier:
> > 
> > --
> > client
> > dev tun
> > proto udp
> > remote 1.2.3.4
> > float
> > nobind
> > verb 1
> > ca /dev/null
> > cert /dev/null
> > key /dev/null
> > 
> > #askpass
> > auth-user-pass
> > --
> > 
> > 
> > If I run systemctl start openvpn@test.service, I *don't* get prompted
> > for a passphrase with openvpn 2.3.7-1 and systemd 225-1.
> > 
> > Are you actually sure, the current openvpn package works?
> 
> Tried the same on jessie with v215, and it worked.
> To me that looks like regression in systemd 225 (or possibly earlier)
> not related to the switch from libsystemd-daemon to libsystemd.
> 
> You should probably file a bug report for that separately, so we can
> track this issue.
> 
> Michael

Thank you so much Michael. I'll do so.

Regards,

Alberto


-- 
Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico
mailto/sip: a...@inittab.org | en GNU/Linux y software libre
Encrypted mail preferred| http://inittab.com

Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D  4BF2 009B 3375 6B9A AA55

Bug#791904: [HEADS-UP] libsystemd transition

[Michael Biebl]

Am 06.09.2015 um 03:34 schrieb Michael Biebl:

> Fwiw, I tried the configuration snippet you posted earlier:
> 
> --
> client
> dev tun
> proto udp
> remote 1.2.3.4
> float
> nobind
> verb 1
> ca /dev/null
> cert /dev/null
> key /dev/null
> 
> #askpass
> auth-user-pass
> --
> 
> 
> If I run systemctl start openvpn@test.service, I *don't* get prompted
> for a passphrase with openvpn 2.3.7-1 and systemd 225-1.
> 
> Are you actually sure, the current openvpn package works?

Tried the same on jessie with v215, and it worked.
To me that looks like regression in systemd 225 (or possibly earlier)
not related to the switch from libsystemd-daemon to libsystemd.

You should probably file a bug report for that separately, so we can
track this issue.

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#791904: [HEADS-UP] libsystemd transition

[Alberto Gonzalez Iniesta]

On Fri, Sep 04, 2015 at 07:50:57PM +0200, Michael Biebl wrote:
> Am 04.09.2015 um 19:22 schrieb Michael Biebl:
> > Am 04.09.2015 um 19:09 schrieb Alberto Gonzalez Iniesta:
> >> On Fri, Sep 04, 2015 at 06:59:27PM +0200, Michael Biebl wrote:
> >>> Am 04.09.2015 um 18:53 schrieb Michael Biebl:
>  Am 04.09.2015 um 18:08 schrieb Alberto Gonzalez Iniesta:
> >>>
> > So I had to (horribly) hack the configure.ac file.
> >
> > Anyway, the problem is that once built, the call to 
> > systemd-ask-password (or
> > the request to execute systemd-tty-ask-password-agent, for that matter) 
> > fails.
> 
>  Let's first figure out why the build fails for you.
> >>>
> >>> A complete (pbuilder/schroot) log which shows what packages are
> >>> installed, would be helpful here.
> > 
> > Is your pbuilder chroot up-to-date? Does it have systemd installed?
> > 
> > Seems like your configure script doesn't detect systemd-ask-password either:
> > 
> > checking for systemd-ask-password... no
> > 
> > That's where your problem with systemd-tty-ask-password-agent is
> > probably coming from.
> 
> Ok, I now understand where the problem is:
> 
> PKG_CHECK_MODULES([libsystemd], [systemd libsystemd],
>   [],
>   [PKG_CHECK_MODULES([libsystemd], [libsystemd-daemon])]
>  )
> 
> This is the configure check.
> It first tests for libsystemd.pc *and* systemd.pc.
> If those are not available, it tests for libsystemd-daemon.pc
> 
> systemd.pc is shipped by the systemd package itself and *not* by
> libsystemd-dev. Since your pbuilder chroot doesn't have systemd
> installed, the first check always fails, but if you have
> libsystemd-daemon-dev around, the fallback succeeds.
> 
> So, the trivial workaround for that is, to add a Build-Depends on
> "systemd". This will also make sure that systemd-ask-password is
> detected properly during build.

Hi Michael,

Sorry to bug you again. I'm building 2.3.8-1 now, but the problem with
systemd-ask-password remains. It is correctly detected in the build
proccess (log attached), but still does not work.
checking for systemd-ask-password... /bin/systemd-ask-password

Current Build-Depends: debhelper (>= 7.0.50~), libssl-dev (>> 0.9.8g-9),
liblzo2-dev, libpam0g-dev, libpkcs11-helper1-dev, pkg-config, dpkg-dev
(>= 1.16.1), iproute2 [linux-any], net-tools [!linux-any], dh-systemd
(>= 1.5), libsystemd-dev [linux-any], systemd [linux-any]

Any hints would be appreciated. I could upload 2.3.7-2 just to easy the
transition now if you want.

Thanks,

Alberto


-- 
Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico
mailto/sip: a...@inittab.org | en GNU/Linux y software libre
Encrypted mail preferred| http://inittab.com

Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D  4BF2 009B 3375 6B9A AA55

Bug#791904: [HEADS-UP] libsystemd transition

[Michael Biebl]

On Sat, 5 Sep 2015 10:57:00 +0200 Alberto Gonzalez Iniesta
> Sorry to bug you again. I'm building 2.3.8-1 now, but the problem with
> systemd-ask-password remains. It is correctly detected in the build
> proccess (log attached), but still does not work.

What does not work exactly?
I don't see how this would be related to switch from libsystemd-daemon
to libsystemd.

Is this maybe an issue of 2.3.8 completely unrelated to the libsystemd
switch?

If so, please upload 2.3.7 and figure out later what's wrong with 2.3.8.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#791904: [HEADS-UP] libsystemd transition

[Michael Biebl]

Am 06.09.2015 um 03:03 schrieb Michael Biebl:
> On Sat, 5 Sep 2015 10:57:00 +0200 Alberto Gonzalez Iniesta
>> Sorry to bug you again. I'm building 2.3.8-1 now, but the problem with
>> systemd-ask-password remains. It is correctly detected in the build
>> proccess (log attached), but still does not work.
> 
> What does not work exactly?
> I don't see how this would be related to switch from libsystemd-daemon
> to libsystemd.
> 
> Is this maybe an issue of 2.3.8 completely unrelated to the libsystemd
> switch?
> 
> If so, please upload 2.3.7 and figure out later what's wrong with 2.3.8.

Fwiw, I tried the configuration snippet you posted earlier:

--
client
dev tun
proto udp
remote 1.2.3.4
float
nobind
verb 1
ca /dev/null
cert /dev/null
key /dev/null

#askpass
auth-user-pass
--


If I run systemctl start openvpn@test.service, I *don't* get prompted
for a passphrase with openvpn 2.3.7-1 and systemd 225-1.

Are you actually sure, the current openvpn package works?




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#791904: [HEADS-UP] libsystemd transition

[Michael Biebl]

Hi

Am 04.09.2015 um 13:42 schrieb Alberto Gonzalez Iniesta:
> I've been fighting with this for some time, but building with recent
> libsystemd-dev (without libsystemd-daemon-dev), makes
> systemd-ask-password support fail (disappear?). 
> Please find attached the debdiff for my work in progress. I had to patch
> the configure script in order to skip the check for
> libsystemd-daemon-dev.
> 
> Any hints/help would be appreciated. I also tried with a more recent
> upstream version, with the same result.

Hm, I don't understand why you need to patch configure.ac. Looking at
configure.ac, it has:

PKG_CHECK_MODULES([libsystemd], [systemd libsystemd],
  [],
  [PKG_CHECK_MODULES([libsystemd], [libsystemd-daemon])]
  )

So, it already checks for the new libsystemd first, then falls back to
the old libsystmd-daemon name. I.e., all you need to do is to change the
Build-Depends in debian/control from libsystemd-daemon-dev to
libsystemd-dev, for which I attached a patch [1].
I did a test build with that patch applied and the resulting package had
a proper b-dep on libsystemd. Attached is the build log.

Cheers,
Michael


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791904#10
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
dpkg-buildpackage: source package openvpn
dpkg-buildpackage: source version 2.3.7-1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Alberto Gonzalez Iniesta 
 dpkg-source --before-build openvpn-2.3.7
 fakeroot debian/rules clean
dh clean --with systemd
   dh_testdir
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/tmp/openvpn-2.3.7'
# These two get deleted on "make clean", but come in the tarball
# hack to keep them around after "make clean"
test -f distro/rpm/openvpn.spec.not || mv distro/rpm/openvpn.spec distro/rpm/openvpn.spec.not
test -f tests/t_client.sh.not || mv tests/t_client.sh tests/t_client.sh.not
dh_auto_clean
test -f distro/rpm/openvpn.spec.not && mv distro/rpm/openvpn.spec.not distro/rpm/openvpn.spec
test -f tests/t_client.sh.not && mv tests/t_client.sh.not tests/t_client.sh
# clean plugins
# /usr/bin/make -C plugin/auth-pam/ clean
# /usr/bin/make -C plugin/down-root/ clean
make[1]: Leaving directory '/tmp/openvpn-2.3.7'
   debian/rules override_dh_clean
make[1]: Entering directory '/tmp/openvpn-2.3.7'
dh_clean -X win/openvpn.nsi.orig
make[1]: Leaving directory '/tmp/openvpn-2.3.7'
 dpkg-source -b openvpn-2.3.7
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building openvpn using existing ./openvpn_2.3.7.orig.tar.gz
dpkg-source: info: building openvpn in openvpn_2.3.7-1.debian.tar.xz
dpkg-source: info: building openvpn in openvpn_2.3.7-1.dsc
 dpkg-genchanges -S >../openvpn_2.3.7-1_source.changes
dpkg-genchanges: including full source code in upload
 dpkg-source --after-build openvpn-2.3.7
dpkg-buildpackage: full upload (original source is included)
 -> Copying COW directory
  forking: rm -rf /var/cache/pbuilder/build//cow.1912 
  forking: cp -al /var/cache/pbuilder/sid.cow /var/cache/pbuilder/build//cow.1912 
I: removed stale ilistfile /var/cache/pbuilder/build//cow.1912/.ilist
  forking: chroot /var/cache/pbuilder/build//cow.1912 cowdancer-ilistcreate /.ilist find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a -links +1 -print0 \) | xargs -0 stat --format '%d %i ' 
 -> Invoking pbuilder
  forking: pbuilder build --debbuildopts  --debbuildopts  --buildplace /var/cache/pbuilder/build//cow.1912 --buildresult /var/cache/pbuilder/result/ --debbuildopts  --no-targz --internal-chrootexec chroot /var/cache/pbuilder/build//cow.1912 cow-shell /tmp/openvpn_2.3.7-1.dsc 
I: Running in no-targz mode
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Fri Sep  4 14:22:08 CEST 2015
I: pbuilder-time-stamp: 1441369328
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 7.0.50~), libssl-dev (>> 0.9.8g-9), liblzo2-dev, libpam0g-dev, libpkcs11-helper1-dev, pkg-config, dpkg-dev (>= 1.16.1), iproute2, dh-systemd (>= 1.5), libsystemd-dev
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting 

Bug#791904: [HEADS-UP] libsystemd transition

[Alberto Gonzalez Iniesta]

On Thu, Aug 27, 2015 at 02:53:32AM +0200, Michael Biebl wrote:
> Hi
> 
> On Mon, 13 Jul 2015 16:30:11 +0200 Michael Biebl  wrote:
> > Control: severity -1 important
> >
> > Hi,
> >
> > this is a heads-up that we plan to drop the libsystemd-* compat
> > libraries in about two months. At that point, your package will FTBFS
> > and this bug will be raised to serious.
> 
> This is another friendly reminder that the compat libraries will be
> dropped in 2 weeks.
> Would be great if you can prepare an upload.
> 
> Michael
> 

Hi Michael,

I've been fighting with this for some time, but building with recent
libsystemd-dev (without libsystemd-daemon-dev), makes
systemd-ask-password support fail (disappear?). 
Please find attached the debdiff for my work in progress. I had to patch
the configure script in order to skip the check for
libsystemd-daemon-dev.

Any hints/help would be appreciated. I also tried with a more recent
upstream version, with the same result.


Regards,

Alberto


-- 
Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico
mailto/sip: a...@inittab.org | en GNU/Linux y software libre
Encrypted mail preferred| http://inittab.com

Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D  4BF2 009B 3375 6B9A AA55
diff -Nru openvpn-2.3.7/debian/changelog openvpn-2.3.7/debian/changelog
--- openvpn-2.3.7/debian/changelog  2015-07-01 14:19:20.0 +0200
+++ openvpn-2.3.7/debian/changelog  2015-09-04 13:20:01.0 +0200
@@ -1,3 +1,10 @@
+openvpn (2.3.7-2) unstable; urgency=medium
+
+  * Patch configure to build without libsystemd-daemon-dev.
+(Closes: #791904). Rename debian/control Build-Dep
+
+ -- Alberto Gonzalez Iniesta   Fri, 04 Sep 2015 11:18:40 
+
+
 openvpn (2.3.7-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru openvpn-2.3.7/debian/control openvpn-2.3.7/debian/control
--- openvpn-2.3.7/debian/control2015-07-01 13:14:01.0 +0200
+++ openvpn-2.3.7/debian/control2015-09-04 13:21:16.0 +0200
@@ -2,7 +2,7 @@
 Section: net
 Priority: optional
 Maintainer: Alberto Gonzalez Iniesta 
-Build-Depends: debhelper (>= 7.0.50~), libssl-dev (>> 0.9.8g-9), liblzo2-dev, 
libpam0g-dev, libpkcs11-helper1-dev, pkg-config, dpkg-dev (>= 1.16.1), iproute2 
[linux-any], net-tools [!linux-any], dh-systemd (>= 1.5), libsystemd-daemon-dev
+Build-Depends: debhelper (>= 7.0.50~), libssl-dev (>> 0.9.8g-9), liblzo2-dev, 
libpam0g-dev, libpkcs11-helper1-dev, pkg-config, dpkg-dev (>= 1.16.1), iproute2 
[linux-any], net-tools [!linux-any], dh-systemd (>= 1.5), libsystemd-dev
 Standards-Version: 3.9.5
 Homepage: http://www.openvpn.net/
 Vcs-Git: git://anonscm.debian.org/collab-maint/openvpn.git
diff -Nru openvpn-2.3.7/debian/patches/configure_systemd-daemon.patch 
openvpn-2.3.7/debian/patches/configure_systemd-daemon.patch
--- openvpn-2.3.7/debian/patches/configure_systemd-daemon.patch 1970-01-01 
01:00:00.0 +0100
+++ openvpn-2.3.7/debian/patches/configure_systemd-daemon.patch 2015-09-04 
13:17:58.0 +0200
@@ -0,0 +1,104 @@
+Index: pp/configure
+===
+--- pp.orig/configure
 pp/configure
+@@ -16473,12 +16473,12 @@ if test -n "$libsystemd_CFLAGS"; then
+ pkg_cv_libsystemd_CFLAGS="$libsystemd_CFLAGS"
+  elif test -n "$PKG_CONFIG"; then
+ if test -n "$PKG_CONFIG" && \
+-{ { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists 
--print-errors \"libsystemd-daemon\""; } >&5
+-  ($PKG_CONFIG --exists --print-errors "libsystemd-daemon") 2>&5
++{ { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists 
--print-errors \"libsystemd\""; } >&5
++  ($PKG_CONFIG --exists --print-errors "libsystemd") 2>&5
+   ac_status=$?
+   $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
+   test $ac_status = 0; }; then
+-  pkg_cv_libsystemd_CFLAGS=`$PKG_CONFIG --cflags "libsystemd-daemon" 
2>/dev/null`
++  pkg_cv_libsystemd_CFLAGS=`$PKG_CONFIG --cflags "libsystemd" 2>/dev/null`
+ test "x$?" != "x0" && pkg_failed=yes
+ else
+   pkg_failed=yes
+@@ -16490,12 +16490,12 @@ if test -n "$libsystemd_LIBS"; then
+ pkg_cv_libsystemd_LIBS="$libsystemd_LIBS"
+  elif test -n "$PKG_CONFIG"; then
+ if test -n "$PKG_CONFIG" && \
+-{ { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists 
--print-errors \"libsystemd-daemon\""; } >&5
+-  ($PKG_CONFIG --exists --print-errors "libsystemd-daemon") 2>&5
++{ { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists 
--print-errors \"libsystemd\""; } >&5
++  ($PKG_CONFIG --exists --print-errors "libsystemd") 2>&5
+   ac_status=$?
+   $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
+   test $ac_status = 0; }; then
+-  pkg_cv_libsystemd_LIBS=`$PKG_CONFIG --libs "libsystemd-daemon" 2>/dev/null`
++  pkg_cv_libsystemd_LIBS=`$PKG_CONFIG --libs "libsystemd" 2>/dev/null`
+ test "x$?" != "x0" && 

Bug#791904: [HEADS-UP] libsystemd transition

[Michael Biebl]

Am 04.09.2015 um 18:53 schrieb Michael Biebl:
> Am 04.09.2015 um 18:08 schrieb Alberto Gonzalez Iniesta:

>> So I had to (horribly) hack the configure.ac file.
>>
>> Anyway, the problem is that once built, the call to systemd-ask-password (or
>> the request to execute systemd-tty-ask-password-agent, for that matter) 
>> fails.
> 
> Let's first figure out why the build fails for you.

A complete (pbuilder/schroot) log which shows what packages are
installed, would be helpful here.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#791904: [HEADS-UP] libsystemd transition

[Michael Biebl]

Am 04.09.2015 um 18:08 schrieb Alberto Gonzalez Iniesta:
> On Fri, Sep 04, 2015 at 02:29:34PM +0200, Michael Biebl wrote:
>> Hi
>>
>> Am 04.09.2015 um 13:42 schrieb Alberto Gonzalez Iniesta:
>>> I've been fighting with this for some time, but building with recent
>>> libsystemd-dev (without libsystemd-daemon-dev), makes
>>> systemd-ask-password support fail (disappear?). 
>>> Please find attached the debdiff for my work in progress. I had to patch
>>> the configure script in order to skip the check for
>>> libsystemd-daemon-dev.
>>>
>>> Any hints/help would be appreciated. I also tried with a more recent
>>> upstream version, with the same result.
>>
>> Hm, I don't understand why you need to patch configure.ac. Looking at
>> configure.ac, it has:
>>
>> PKG_CHECK_MODULES([libsystemd], [systemd libsystemd],
>>   [],
>>   [PKG_CHECK_MODULES([libsystemd], [libsystemd-daemon])]
>>   )
>>
>> So, it already checks for the new libsystemd first, then falls back to
>> the old libsystmd-daemon name. I.e., all you need to do is to change the
>> Build-Depends in debian/control from libsystemd-daemon-dev to
>> libsystemd-dev, for which I attached a patch [1].
>> I did a test build with that patch applied and the resulting package had
>> a proper b-dep on libsystemd. Attached is the build log.
> 
> Hi Michael,
> 
> I had to modify configure.ac because otherwise the package build would
> fail. See attached build log with the single modification to 2.3.7-1 of
> the build dependency, built in a clean sid environment *without*
> libsystemd-daemon-dev. These lines seem quite relevant:

Well, you need to have libsystemd-dev installed.
Can you should me the output of
apt-cache policy libsystemd-dev?

Have you seen the build log I sent you? It shows a clean build with
libsystemd-dev install in an up-to-date sid chroot.


> --
> No package 'libsystemd-daemon' found
> configure:16532: error: Package requirements (libsystemd-daemon) were not met:
> 
> No package 'libsystemd-daemon' found
> [..]
> configure: exit 1
> dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=${prefix}/include --mandir=${prefix}/share/man 
> --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-silent-rules --libexecdir=${prefix}/lib/openvpn 
> --disable-maintainer-mode --disable-dependency-tracking CFLAGS=-g -O2 -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security 
> CPPFLAGS=-D_FORTIFY_SOURCE=2 CXXFLAGS=-g -O2 -fPIE -fstack-protector-strong 
> -Wformat -Werror=format-security FCFLAGS=-g -O2 -fPIE 
> -fstack-protector-strong FFLAGS=-g -O2 -fPIE -fstack-protector-strong 
> GCJFLAGS=-g -O2 -fPIE -fstack-protector-strong LDFLAGS=-fPIE -pie 
> -Wl,-z,relro -Wl,-z,now OBJCFLAGS=-g -O2 -fPIE -fstack-protector-strong 
> -Wformat -Werror=format-security OBJCXXFLAGS=-g -O2 -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security 
> --enable-password-save --host=x86_64-linux-gnu --build=x86_64-linux-gnu 
> --prefix=/usr --mandir=${prefix}/share/man 
> --with-ifconfig-path=/sbin/ifconfig 
--with-route-path=/sbin/route --with-iproute-path=/sbin/ip --enable-iproute2 
--with-plugindir=${prefix}/lib/openvpn --includedir=${prefix}/include/openvpn 
--enable-pkcs11 --enable-x509-alt-username --enable-systemd returned exit code 1
> debian/rules:17: recipe for target 'override_dh_auto_configure' failed
> --
> 
> So I had to (horribly) hack the configure.ac file.
> 
> Anyway, the problem is that once built, the call to systemd-ask-password (or
> the request to execute systemd-tty-ask-password-agent, for that matter) fails.

Let's first figure out why the build fails for you.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#791904: [HEADS-UP] libsystemd transition

[Michael Biebl]

Hi Alberto!

Am 04.09.2015 um 14:29 schrieb Michael Biebl:
> checking for systemd-ask-password... /bin/systemd-ask-password

..

> checking for libsystemd... yes
> checking systemd/sd-daemon.h usability... yes
> checking systemd/sd-daemon.h presence... yes
> checking for systemd/sd-daemon.h... yes
> checking for sd_booted... yes

This is from the build log. Looks all fine.
Can you be more specific, about what problems you had?
Maybe there is something I can help with.

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#791904: [HEADS-UP] libsystemd transition

[Alberto Gonzalez Iniesta]

On Fri, Sep 04, 2015 at 06:59:27PM +0200, Michael Biebl wrote:
> Am 04.09.2015 um 18:53 schrieb Michael Biebl:
> > Am 04.09.2015 um 18:08 schrieb Alberto Gonzalez Iniesta:
> 
> >> So I had to (horribly) hack the configure.ac file.
> >>
> >> Anyway, the problem is that once built, the call to systemd-ask-password 
> >> (or
> >> the request to execute systemd-tty-ask-password-agent, for that matter) 
> >> fails.
> > 
> > Let's first figure out why the build fails for you.
> 
> A complete (pbuilder/schroot) log which shows what packages are
> installed, would be helpful here.
> 
> 

More info from within the chroot:
root@bin:~/foo/openvpn-2.3.7# apt-cache policy libsystemd-dev
libsystemd-dev:
  Installed: 225-1
  Candidate: 225-1
  Version table:
 *** 225-1 0
500 http://ftp.debian.org/debian/ sid/main amd64 Packages
100 /var/lib/dpkg/status
root@bin:~/foo/openvpn-2.3.7# pkg-config --list-all
opensslOpenSSL - Secure Sockets Layer and cryptography libraries 
and tools
zlib   zlib - zlib compression library
libssl OpenSSL-libssl - Secure Sockets Layer and cryptography 
libraries
libcrypto  OpenSSL-libcrypto - OpenSSL cryptography library
libsystemd systemd - systemd Library
libpkcs11-helper-1 pkcs11-helper - PKCS




-- 
Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico
mailto/sip: a...@inittab.org | en GNU/Linux y software libre
Encrypted mail preferred| http://inittab.com

Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D  4BF2 009B 3375 6B9A AA55

Bug#791904: [HEADS-UP] libsystemd transition

[Michael Biebl]

Am 04.09.2015 um 19:09 schrieb Alberto Gonzalez Iniesta:
> On Fri, Sep 04, 2015 at 06:59:27PM +0200, Michael Biebl wrote:
>> Am 04.09.2015 um 18:53 schrieb Michael Biebl:
>>> Am 04.09.2015 um 18:08 schrieb Alberto Gonzalez Iniesta:
>>
 So I had to (horribly) hack the configure.ac file.

 Anyway, the problem is that once built, the call to systemd-ask-password 
 (or
 the request to execute systemd-tty-ask-password-agent, for that matter) 
 fails.
>>>
>>> Let's first figure out why the build fails for you.
>>
>> A complete (pbuilder/schroot) log which shows what packages are
>> installed, would be helpful here.

Is your pbuilder chroot up-to-date? Does it have systemd installed?

Seems like your configure script doesn't detect systemd-ask-password either:

checking for systemd-ask-password... no

That's where your problem with systemd-tty-ask-password-agent is
probably coming from.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#791904: [HEADS-UP] libsystemd transition

[Alberto Gonzalez Iniesta]

On Fri, Sep 04, 2015 at 07:50:57PM +0200, Michael Biebl wrote:
> So, the trivial workaround for that is, to add a Build-Depends on
> "systemd". This will also make sure that systemd-ask-password is
> detected properly during build.
> 

Thanks a lot Michael, I'll make an upload tomorrow, probably with the
new upstream release.



-- 
Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico
mailto/sip: a...@inittab.org | en GNU/Linux y software libre
Encrypted mail preferred| http://inittab.com

Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D  4BF2 009B 3375 6B9A AA55

Bug#791904: [HEADS-UP] libsystemd transition

[Michael Biebl]

Am 04.09.2015 um 19:22 schrieb Michael Biebl:
> Am 04.09.2015 um 19:09 schrieb Alberto Gonzalez Iniesta:
>> On Fri, Sep 04, 2015 at 06:59:27PM +0200, Michael Biebl wrote:
>>> Am 04.09.2015 um 18:53 schrieb Michael Biebl:
 Am 04.09.2015 um 18:08 schrieb Alberto Gonzalez Iniesta:
>>>
> So I had to (horribly) hack the configure.ac file.
>
> Anyway, the problem is that once built, the call to systemd-ask-password 
> (or
> the request to execute systemd-tty-ask-password-agent, for that matter) 
> fails.

 Let's first figure out why the build fails for you.
>>>
>>> A complete (pbuilder/schroot) log which shows what packages are
>>> installed, would be helpful here.
> 
> Is your pbuilder chroot up-to-date? Does it have systemd installed?
> 
> Seems like your configure script doesn't detect systemd-ask-password either:
> 
> checking for systemd-ask-password... no
> 
> That's where your problem with systemd-tty-ask-password-agent is
> probably coming from.

Can you create a fresh pbuilder chroot and only apply my patch [1] and
the re-try the build?

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791904#10
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#791904: [HEADS-UP] libsystemd transition

[Michael Biebl]

Am 04.09.2015 um 19:28 schrieb Michael Biebl:
> Can you create a fresh pbuilder chroot and only apply my patch [1] and
> the re-try the build?
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791904#10

While at it, please consider marking the libsystemd-dev b-dep as
[linux-any] and only enable systemd support on Linux.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#791904: [HEADS-UP] libsystemd transition

[Michael Biebl]

Am 04.09.2015 um 19:22 schrieb Michael Biebl:
> Am 04.09.2015 um 19:09 schrieb Alberto Gonzalez Iniesta:
>> On Fri, Sep 04, 2015 at 06:59:27PM +0200, Michael Biebl wrote:
>>> Am 04.09.2015 um 18:53 schrieb Michael Biebl:
 Am 04.09.2015 um 18:08 schrieb Alberto Gonzalez Iniesta:
>>>
> So I had to (horribly) hack the configure.ac file.
>
> Anyway, the problem is that once built, the call to systemd-ask-password 
> (or
> the request to execute systemd-tty-ask-password-agent, for that matter) 
> fails.

 Let's first figure out why the build fails for you.
>>>
>>> A complete (pbuilder/schroot) log which shows what packages are
>>> installed, would be helpful here.
> 
> Is your pbuilder chroot up-to-date? Does it have systemd installed?
> 
> Seems like your configure script doesn't detect systemd-ask-password either:
> 
> checking for systemd-ask-password... no
> 
> That's where your problem with systemd-tty-ask-password-agent is
> probably coming from.

Ok, I now understand where the problem is:

PKG_CHECK_MODULES([libsystemd], [systemd libsystemd],
  [],
  [PKG_CHECK_MODULES([libsystemd], [libsystemd-daemon])]
 )

This is the configure check.
It first tests for libsystemd.pc *and* systemd.pc.
If those are not available, it tests for libsystemd-daemon.pc

systemd.pc is shipped by the systemd package itself and *not* by
libsystemd-dev. Since your pbuilder chroot doesn't have systemd
installed, the first check always fails, but if you have
libsystemd-daemon-dev around, the fallback succeeds.

So, the trivial workaround for that is, to add a Build-Depends on
"systemd". This will also make sure that systemd-ask-password is
detected properly during build.

Eventually, you should forward this issue upstream. It should drop the
"systemd" from the pkg-config check, like this:

PKG_CHECK_MODULES([libsystemd], [libsystemd],
  [],
  [PKG_CHECK_MODULES([libsystemd], [libsystemd-daemon])]
 )



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#791904: [HEADS-UP] libsystemd transition

[Michael Biebl]

Hi

On Mon, 13 Jul 2015 16:30:11 +0200 Michael Biebl bi...@debian.org wrote:
 Control: severity -1 important

 Hi,

 this is a heads-up that we plan to drop the libsystemd-* compat
 libraries in about two months. At that point, your package will FTBFS
 and this bug will be raised to serious.

This is another friendly reminder that the compat libraries will be
dropped in 2 weeks.
Would be great if you can prepare an upload.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#791904: [HEADS-UP] libsystemd transition

[Michael Biebl]

Control: severity -1 important

Hi,

this is a heads-up that we plan to drop the libsystemd-* compat
libraries in about two months. At that point, your package will FTBFS
and this bug will be raised to serious.

Regards,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?







signature.asc
Description: OpenPGP digital signature