Bug#795603: ruby-libvirt: has no rubygems-integration entry

2016-03-14 Thread Guido De Rosa
Hi,

as his was opened seven months ago, I'm currently not actively working with
this package (and Ruby) at the moment, so I'd need to regain access to a
proper eviroinment to test this, which may take some time, sorry about
that, but I'll keep you updated.

Thanks,

G.

On 10 March 2016 at 18:55, Guido Günther  wrote:

> On Sat, Aug 15, 2015 at 06:32:25PM +0200, Guido De Rosa wrote:
> [..snip..]
> > [Suggested solution / approach]
> >
> > I guess the issue can be easily fixed by adding the gemspec file taken
> > from the original gem
>
>
> Did you check that this works? If so, could you provide a tested patch?
> Cheers,
>  -- Guido
>


Bug#795603: ruby-libvirt: has no rubygems-integration entry

2015-08-15 Thread Guido De Rosa
Package: ruby-libvirt
Version: 0.5.1-3+b1
Severity: important

Dear Maintainer,

[Use case]

For my Ruby applications I like using both Bundler and
Debian-prepackaged gems (specially when they would require native
compilation). So, when in Debian, when I `bundle install`, I get
"Using... " from Bundler and there's no need to install from
rubygems.org (and compile), I just use the deb package installed
already; but when deploying in
other environments, still my application can work doing ultimately a generic
gem install (and native compile for gems like ruby-libvirt which use
extensions).

For such reason, rubygems-integration is great! as it makes the
deployment easy in Debian but still allows generic installation of gems
elsewhere.

[Problem]

Unfortunately there's no rubygems-integration for ruby-libvirt.

[Suggested solution / approach]

I guess the issue can be easily fixed by adding the gemspec file taken
from the original gem

https://rubygems.org/gems/ruby-libvirt

to this package, in such a way that it gets installed
under /usr/share/rubygems-integration/2.1/specifications/ .

See other ruby-mysql, ruby-rmagick and many others as examples.

[Other Debian releases]

Please note, this issue is not fixed in testing/unstable/experimental
versions of this package either.

Thanks.

Guido

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages ruby-libvirt depends on:
ii  libc6 2.19-18
ii  libgmp10  2:6.0.0+dfsg-6
ii  libruby2.12.1.5-2+deb8u1
ii  libvirt0  1.2.9-9
ii  ruby  1:2.1.5+deb8u1
ii  ruby1.9.1 [ruby-interpreter]  1.9.3.484-1
ii  ruby2.1 [ruby-interpreter]2.1.5-2+deb8u1

ruby-libvirt recommends no packages.

ruby-libvirt suggests no packages.

-- no debconf information



Bug#717558: [PATCH] add api/glfs.h to glusterfs-common

2013-07-22 Thread Guido De Rosa
This simple patch should fix the issue.

Thanks.


gfapi.diff
Description: Binary data


Bug#717558: glusterfs-common: /usr/include/glusterfs/api/glfs.h is missing

2013-07-22 Thread Guido De Rosa
Package: glusterfs-common
Version: 3.4.0-1
Severity: important

Dear Maintainer,

/usr/include/glusterfs/api/glfs.h has been included as of version 3.4.0
and is required to compile e.g. QEMU >= 1.4 with *native*  
Gluster support (./configure --enable-gluster, which allow bypassing
FUSE-mount to improve performance).

Generally, it's required to compile any package which uses the new
gfapi.

It is missing from glusterfs-common and should be added.

I'm not sure if other api/*.h files could be useful to be included as
well.

Thanks.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages glusterfs-common depends on:
ii  dpkg   1.16.10
ii  libc6  2.17-7
ii  libssl1.0.01.0.1e-3
ii  libxml22.9.1+dfsg1-2
ii  multiarch-support  2.17-7

glusterfs-common recommends no packages.

glusterfs-common suggests no packages.

-- no debconf information


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



Bug#319080: errata

2005-07-20 Thread Guido De Rosa
Obviously, I was talkin' about -bootclasspath (not -classpath) option
when invoking jikes. Sorry :). The small patch should be valid anyway
(at least, it works fine on my system).

G. D.



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



Bug#319080: classpath set uncorrectly in /usr/bin/jikes-sun

2005-07-19 Thread Guido De Rosa
Package: jikes-sun
Version: 0.8
Severity: important
Tags: patch


-classpath for jikes is set uncorrectly in /usr/bin/jikes-sun because
(with Blackdown java) rt.jar and others are in /usr/lib/j2se/1.4/jre/lib 
and not in /usr/lib/j2se/1.4/jre . The following very little patch 
corrects the problem.

14c14
<   JPATH=/usr/lib/j2se/1.4/jre
---
>   JPATH=/usr/lib/j2se/1.4/jre/lib

Regards,
Guido De Rosa


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11.8
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages jikes-sun depends on:
ii  j2re1.4   1.4.2.01-1 Blackdown Java(TM) 2 Runtime Envir
ii  jikes 1:1.22-2   Fast Java compiler adhering to lan

Versions of packages jikes-sun recommends:
ii  java-package  0.25   utility for building Java(TM) 2 re

-- no debconf information
14c14
<   JPATH=/usr/lib/j2se/1.4/jre
---
>   JPATH=/usr/lib/j2se/1.4/jre/lib


Bug#318757: syslog-ng: init script should accept values 1-8 and not 0-7 for $CONSOLE_LOG_LEVEL

2005-07-17 Thread Guido De Rosa
Package: syslog-ng
Version: 1.6.5-2.2
Severity: normal


In /etc/init.d/syslog-ng

###
case "x$CONSOLE_LOG_LEVEL" in
x[0-7]) 
dmesg -n $CONSOLE_LOG_LEVEL
;;
*)
echo "CONSOLE_LOG_LEVEL is of unaccepted value."
;;
esac
#

'[0-7]' should be changed to '[1-8]' (the values accepted by dmesg -n).


Regards,
Guido De Rosa


-- System Information:
Debian Release: 3.1
Architecture: i386 (i586)
Kernel: Linux 2.4.29
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages syslog-ng depends on:
ii  libc6   2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  util-linux  2.12p-4  Miscellaneous system utilities

-- no debconf information


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