Bug#887742: dictem: orig tarball changed from 1.0.4-2 to 1.0.4-3

2018-03-02 Thread Yauheni Kaliuta
Since the same .orig.tar.gz is a part of stable already, I cannot
update it, sorry :(. I'm discussing with the upstream about releasing
a new version.

On 1 February 2018 at 10:21, Yauheni Kaliuta <y.kali...@gmail.com> wrote:
> Hi, Jeremy!
>
> I see I made a mistake with packaging of -2, it is packaged as native.
>
> For the early .orig.tar.gz, it looks repacked from git, the checksum
> doesn't match http://www.mova.org/~cheusov/pub/dictem/dictem-1.0.4.tar.gz.
> When switching to 3.0 format, I inclined to use the very original
> tarball.
>
> Could you make some sort of manual sync for that?
>
> On 19 January 2018 at 17:30, Jeremy Bicha <jbi...@debian.org> wrote:
>> Source: dictem
>> Version: 1.0.4-4
>> Severity: important
>>
>> Ubuntu automatically syncs packages from Debian, but dictem won't sync
>> because dictem_1.0.4.orig.tar.gz changed after 1.0.4-2.
>>
>> To fix this, I suggest switching debian/source/format to 3.0 (quilt)
>> and making sure that you explicitly use the older 1.0.4.orig.tar.gz
>>
>> I am happy to do an NMU to take care of this if you like.
>>
>> Thanks,
>> Jeremy Bicha



Bug#887742: dictem: orig tarball changed from 1.0.4-2 to 1.0.4-3

2018-02-01 Thread Yauheni Kaliuta
Hi, Jeremy!

I see I made a mistake with packaging of -2, it is packaged as native.

For the early .orig.tar.gz, it looks repacked from git, the checksum
doesn't match http://www.mova.org/~cheusov/pub/dictem/dictem-1.0.4.tar.gz.
When switching to 3.0 format, I inclined to use the very original
tarball.

Could you make some sort of manual sync for that?

On 19 January 2018 at 17:30, Jeremy Bicha  wrote:
> Source: dictem
> Version: 1.0.4-4
> Severity: important
>
> Ubuntu automatically syncs packages from Debian, but dictem won't sync
> because dictem_1.0.4.orig.tar.gz changed after 1.0.4-2.
>
> To fix this, I suggest switching debian/source/format to 3.0 (quilt)
> and making sure that you explicitly use the older 1.0.4.orig.tar.gz
>
> I am happy to do an NMU to take care of this if you like.
>
> Thanks,
> Jeremy Bicha



Bug#887742: dictem: orig tarball changed from 1.0.4-2 to 1.0.4-3

2018-01-20 Thread Yauheni Kaliuta
On 19 January 2018 at 17:30, Jeremy Bicha  wrote:
> To fix this, I suggest switching debian/source/format to 3.0 (quilt)
> and making sure that you explicitly use the older 1.0.4.orig.tar.gz
>

I, actually, had the idea to switch to 3.0, just was a bit lazy :)

> I am happy to do an NMU to take care of this if you like.

If you are not in hurry, I'll do it soon myself.



Bug#765448: [Pkg-libvirt-maintainers] Bug#765448:

2014-10-29 Thread Yauheni Kaliuta
Hi, Guido!

Hmmm, almost missed the message, google spammed it.

On Thu, Oct 16, 2014 at 9:52 PM, Guido Günther a...@sigxcpu.org wrote:
 On Thu, Oct 16, 2014 at 04:53:03PM +0300, Yauheni Kaliuta wrote:

[...]
 In such cases responsible maintainers provide different
 binary packages with different features enabled.
[...]

 What about sending patches to dlopen polkit and fall back to socket
 based auth if it's not available?

Well, I'll have a look when get some free time. At the moment I'm not
aware of the stuff.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765448:

2014-10-16 Thread Yauheni Kaliuta
You can decrease priority if it's so important for you, but I consider
that as a bug. In such cases responsible maintainers provide different
binary packages with different features enabled. Up to you, of course,
if you have attitude to keep debian as a usable and universal OS or
not.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765448: libvirt-daemon-system is not installable on non-systemd system

2014-10-15 Thread Yauheni Kaliuta
Package: libvirt-daemon-system
Version: 1.2.8-3
Severity: normal

Dear Maintainer,

attempts to do apt-get dist-upgrade recently started to report:

The following packages will be REMOVED:
  libvirt-bin libvirt-daemon-system virt-goodies

$  apt-cache policy libvirt-daemon-system
libvirt-daemon-system:
  Installed: 1.2.8-3
  Candidate: 1.2.9-3
  Version table:
 1.2.9-3 0
500 http://ftp.fi.debian.org/debian/ unstable/main amd64 Packages
 *** 1.2.8-3 0
500 http://ftp.fi.debian.org/debian/ jessie/main amd64 Packages
100 /var/lib/dpkg/status

The reason is that the new libvirt-daemon-system version Depends of
policykit-1,
which depends of libpam-systemd which Depends of systemd which is blocked
on my
system.

Since it's declared, that systemd is not mandatory in Debian, the package
must
be installable (or what I did wrong?).


-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0kaliuta1+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libvirt-daemon-system depends on:
ii  adduser  3.113+nmu3
ii  gettext-base 0.19.2-3
ii  init-system-helpers  1.21
ii  libapparmor1 2.8.0-8
ii  libaudit11:2.4-1
ii  libavahi-client3 0.6.31-4
ii  libavahi-common3 0.6.31-4
ii  libblkid12.25.1-4
ii  libc62.19-11
ii  libcap-ng0   0.7.4-2
ii  libdbus-1-3  1.8.8-2
ii  libdevmapper1.02.1   2:1.02.90-2
ii  libgnutls-deb0-283.3.8-3
ii  libnl-3-200  3.2.24-2
ii  libnl-route-3-2003.2.24-2
ii  libnuma1 2.0.10~rc2-3
ii  librados20.80.6-1
ii  librbd1  0.80.6-1
ii  libsasl2-2   2.1.26.dfsg1-11
ii  libselinux1  2.3-2
ii  libssh2-11.4.3-4
ii  libsystemd0  215-5+b1
ii  libvirt-clients  1.2.8-3
ii  libvirt-daemon   1.2.8-3
ii  libvirt0 1.2.8-3
ii  libxml2  2.9.1+dfsg1-4
ii  libyajl2 2.1.0-2
ii  logrotate3.8.7-1

Versions of packages libvirt-daemon-system recommends:
pn  bridge-utils  none
ii  dmidecode 2.12-3
ii  dnsmasq-base  2.72-2
ii  ebtables  2.0.10.4-3
ii  iproute2  3.16.0-2
ii  iptables  1.4.21-2
ii  parted3.2-6
ii  pm-utils  1.4.1-15

Versions of packages libvirt-daemon-system suggests:
pn  apparmor none
pn  auditd   none
pn  policykit-1  none
pn  radvdnone
pn  systemd  none
pn  systemtapnone

-- Configuration Files:
/etc/libvirt/qemu.conf [Errno 13] Permission denied:
u'/etc/libvirt/qemu.conf'

-- no debconf information


Bug#541283: dictem: autoloads for entrypoints

2009-08-16 Thread Yauheni Kaliuta
Hi!

So, you do not like (require 'dictem) or what?



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#452488: qca-tls unusable with psi (qt4)

2007-11-23 Thread Yauheni Kaliuta
Package: qca-tls
Version: 1.0-4

psi has been rebuilt with qt4 in unstable, but there is no qca-tls for it.
As a result, it is impossible to use TLS with psi now



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#387089: Debian #387089

2006-11-11 Thread Yauheni Kaliuta

For the last option, I have a hack
diff --git a/tools/c_rehash.in b/tools/c_rehash.in
index 4497cbd..d76e693 100644
--- a/tools/c_rehash.in
+++ b/tools/c_rehash.in
@@ -59,12 +59,15 @@ sub hash_dir {
 		}
 	}
 	closedir DIR;
-	FILE: foreach $fname (grep {/\.pem$/} @flist) {
+	FILE: foreach $fname (grep {/\.pem$|\.crt$/} @flist) {
 		# Check to see if certificates and/or CRLs present.
 		my ($cert, $crl) = check_file($fname);
 		if(!$cert  !$crl) {
-			print STDERR WARNING: $fname does not contain a certificate or CRL: skipping\n;
-			next;
+			($cert, $crl) = check_file($openssl x509 -in \$fname\ -inform der  -outform pem | );
+			if(!$cert  !$crl) {
+print STDERR WARNING: $fname does not contain a certificate or CRL: skipping\n;
+next;
+			}
 		}
 		link_hash_cert($fname) if($cert);
 		link_hash_crl($fname) if($crl);
@@ -102,6 +105,9 @@ sub link_hash_cert {
 		my $fname = $_[0];
 		$fname =~ s/'/'\\''/g;
 		my ($hash, $fprint) = `$openssl x509 -hash -fingerprint -noout -in '$fname'`;
+		if(!$hash || !fprint) {
+			($hash, $fprint) = `$openssl x509 -hash -fingerprint -noout -in '$fname' -inform der`;
+		}
 		chomp $hash;
 		chomp $fprint;
 		$fprint =~ s/^.*=//;


Bug#397620: More FTBFS info

2006-11-11 Thread Yauheni Kaliuta

Steve,

For me it's built ok if you install libpop-dev before building (not
after has found the problem)


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#397908: syscall workaround

2006-11-11 Thread Yauheni Kaliuta

_syscalln macroses defined only for __KERNEL__ in unistd.h. A
workaround like for i386 helps to build it, but I do not know how it
is correct. The code has been taken from unistd.h
diff --git a/src/base/linux_syscall_support.h b/src/base/linux_syscall_support.h
index 0dfdd8d..41b3b17 100644
--- a/src/base/linux_syscall_support.h
+++ b/src/base/linux_syscall_support.h
@@ -323,6 +323,106 @@ struct dirent64;
   BODY(type, name, r(__r0), r(__r1), r(__r2), r(__r3),\
r(__r4), r(__r5)); \
 }
+  #elif defined (__x86_64__)
+#undef _syscall0
+#undef _syscall1
+#undef _syscall2
+#undef _syscall3
+#undef _syscall4
+#undef _syscall5
+#undef _syscall6
+
+#define __syscall_return(type, res) \
+do { \
+	if ((unsigned long)(res) = (unsigned long)(-127)) { \
+		errno = -(res); \
+		res = -1; \
+	} \
+	return (type) (res); \
+} while (0)
+
+#define __syscall_clobber r11,rcx,memory 
+#define __syscall syscall
+
+#define _syscall0(type,name) \
+type name(void) \
+{ \
+long __res; \
+__asm__ volatile (__syscall \
+	: =a (__res) \
+	: 0 (__NR_##name) : __syscall_clobber ); \
+__syscall_return(type,__res); \
+}
+
+#define _syscall1(type,name,type1,arg1) \
+type name(type1 arg1) \
+{ \
+long __res; \
+__asm__ volatile (__syscall \
+	: =a (__res) \
+	: 0 (__NR_##name),D ((long)(arg1)) : __syscall_clobber ); \
+__syscall_return(type,__res); \
+}
+	   
+#define _syscall2(type,name,type1,arg1,type2,arg2) \
+type name(type1 arg1,type2 arg2) \
+{ \
+long __res; \
+__asm__ volatile (__syscall \
+	: =a (__res) \
+	: 0 (__NR_##name),D ((long)(arg1)),S ((long)(arg2)) : __syscall_clobber ); \
+__syscall_return(type,__res); \
+}
+
+#define _syscall3(type,name,type1,arg1,type2,arg2,type3,arg3) \
+type name(type1 arg1,type2 arg2,type3 arg3) \
+{ \
+long __res; \
+__asm__ volatile (__syscall \
+	: =a (__res) \
+	: 0 (__NR_##name),D ((long)(arg1)),S ((long)(arg2)), \
+		  d ((long)(arg3)) : __syscall_clobber); \
+__syscall_return(type,__res); \
+}
+
+#define _syscall4(type,name,type1,arg1,type2,arg2,type3,arg3,type4,arg4) \
+type name (type1 arg1, type2 arg2, type3 arg3, type4 arg4) \
+{ \
+long __res; \
+__asm__ volatile (movq %5,%%r10 ; __syscall \
+	: =a (__res) \
+	: 0 (__NR_##name),D ((long)(arg1)),S ((long)(arg2)), \
+	  d ((long)(arg3)),g ((long)(arg4)) : __syscall_clobber,r10 ); \
+__syscall_return(type,__res); \
+} 
+
+#define _syscall5(type,name,type1,arg1,type2,arg2,type3,arg3,type4,arg4, \
+	  type5,arg5) \
+type name (type1 arg1,type2 arg2,type3 arg3,type4 arg4,type5 arg5) \
+{ \
+long __res; \
+__asm__ volatile (movq %5,%%r10 ; movq %6,%%r8 ;  __syscall \
+	: =a (__res) \
+	: 0 (__NR_##name),D ((long)(arg1)),S ((long)(arg2)), \
+	  d ((long)(arg3)),g ((long)(arg4)),g ((long)(arg5)) : \
+	__syscall_clobber,r8,r10 ); \
+__syscall_return(type,__res); \
+}
+
+#define _syscall6(type,name,type1,arg1,type2,arg2,type3,arg3,type4,arg4, \
+	  type5,arg5,type6,arg6) \
+type name (type1 arg1,type2 arg2,type3 arg3,type4 arg4,type5 arg5,type6 arg6) \
+{ \
+long __res; \
+__asm__ volatile (movq %5,%%r10 ; movq %6,%%r8 ; movq %7,%%r9 ;  __syscall \
+	: =a (__res) \
+	: 0 (__NR_##name),D ((long)(arg1)),S ((long)(arg2)), \
+	  d ((long)(arg3)), g ((long)(arg4)), g ((long)(arg5)), \
+	  g ((long)(arg6)) : \
+	__syscall_clobber,r8,r10,r9 ); \
+__syscall_return(type,__res); \
+}
+
   #endif
   #if defined(__x86_64__)
 struct msghdr;