Fabian Greffrath dijo [Mon, May 18, 2015 at 02:04:07PM +0200]:
Am Montag, den 18.05.2015, 12:51 +0100 schrieb Jonathan McDowell:
noodles@kaufmann:~$ gpg --no-default-keyring \
--keyring /srv/keyring.debian.org/keyrings/debian-keyring.gpg \
--list-key 0xCBEA8E970CCD59DF
pub
Sorry for the long time in processing your simple patch — You happened
to file it two days before my twins were born ;-)
Uploaded. I have not backported it; it would have made sense to
backport to Wheezy at that point; nowadays that Jessie is stable, I am
not yet backporting this as it is a minor
Hi,
Your report strikes me as quite weird, as I recently did the same
without any trouble. Does your Apache installation allow for
directives to be specified via .htcaccess? (look for AllowOverride
in your Apache configurations)
You mention:
Tried everything under the sun:
modified
Christoph Berg dijo [Thu, May 14, 2015 at 10:11:44PM +0200]:
Hi Gunnar,
I'd call it a LXC bug if it doesn't support POSIX shared memory.
That said, I've been bitten by this problem as well - in my case,
/dev/shm was simply not mounted and a cluster with no explicit
Source: postgresql-9.4
Version: 9.4.1-1
Severity: important
I upgraded a server (a LXC-based container) from Wheezy to
Jessie. After installing, everything looked OK, with the (live) 9.1
and (empty) 9.4 clusters running.
Now, following the instructions at
Ming-ting Yao Wei dijo [Thu, Apr 30, 2015 at 08:48:15PM +0800]:
Description : Correct your misbehavior on the command line
The package tries to fix your command line error, such as missing sudo
or typo.
Ugh. I'd fear having an automated tool that tried to call sudo for
every action I
Peter Spiess-Knafl dijo [Wed, Apr 29, 2015 at 08:17:03PM +0200]:
Hi Gunnar,
Does this bug still affect you in the latest version of pidgin (2.10.11)?
Hi,
This was a *very* old bug! I haven't seen this behaviour in a long
time. I think it's safe to mark it as closed.
Thanks!
--
To
David Prévot dijo [Thu, Apr 02, 2015 at 02:07:06AM -0400]:
Sorry for the lateness - I'm currently devoid of free time, and my
package maintainance status has suffered :(
It’s not even been a week since that bug was filed, so no need to
apologize (and yay, double happy event may drag one
Hi David!
Sorry for the lateness - I'm currently devoid of free time, and my
package maintainance status has suffered :(
I just noticed that the collabtive package embeds its own copy of (at
least) HTMLPurifier (as available in the php-htmlpurifier package) and
phpseclib (as available in the
Matthew Gabeler-Lee dijo [Tue, Mar 24, 2015 at 08:03:00PM -0400]:
On 03/24/2015 07:46 PM, Matthew Gabeler-Lee wrote:
I've attached a patch that includes the above debug messages and my
ugly(?) fix for it, which works for me. This is the first time I've
ever tried to write ruby code, so
Christian PERRIER dijo [Fri, Mar 13, 2015 at 06:38:48PM +0100]:
The state of Quintana Roo, in South-Eastern Mexico, has its own
timezone since this February:
Hello Gunnar (and family...;-)) ,
So, it actually means that a change is also needed to the tzsetup
component of D-I, so that
Package: tzdata
Version: 2015a-1
Severity: normal
Tags: patch
The state of Quintana Roo, in South-Eastern Mexico, has its own
timezone since this February:
http://www.worldtimezone.com/dst_news/dst_news_mexico11.html
http://www.cenam.mx/Hora_oficial/ (Spanish)
Raoul Gunnar Borenius dijo [Mon, Feb 16, 2015 at 11:30:24AM +0100]:
File::MkTemp and File::MkTempO provides functions to create unique strings
for use as file/directory names based on an user specified template.
The package would be very useful for Nagios/Icinga-Installations
using the
Dmitry Bogatov dijo [Thu, Feb 12, 2015 at 10:43:17AM +0300]:
- why is this package useful/relevant?
It follows unix way and manages wallpapers without connection to
your DE, WM or anything.
(...)
if there are other packages providing similar functionality, how does it
compare?
Such
While working on the reproducible builds effort [1], we have noticed
that debian-keyring could not be built reproducibly.
The attached patch removes timestamps from the build system. Once
applied, debian-keyring can be built reproducibly in our current
experimental
framework.
Added to our
...Just to report I'm not just sitting on this bug report; it does
not affect all Drupal modules (although I'm sure you stumbled on a
pretty common one!). The problem is not AFAICT on the tables parsing
(that one already bit us some time ago) but on some other artifact. I
spent some time poking
Moritz Mühlenhoff dijo [Tue, Dec 09, 2014 at 10:17:14PM +0100]:
I'm getting in touch with the authors right now. Thanks!
http://collabtive.o-dyn.de/forum/viewtopic.php?f=11t=8479
Gunnar,
is this fixed in the version in jessie?
Sorry for the delay for this reply!
I can confirm you
as git.debian.org is deprecated
+ * Debian has frozen! We will start backporting the important fixes to
+7.32
+ * Backported from 7.34: SA-CORE-2014-006 (Session hijacking CVE-2014-
+9015, Denial of service CVE-2014-9016)
+ * Several minor reliability fixes backported from 7.33
+
+ -- Gunnar Wolf gw
Before anything else, Michal: Please remember Debian is a
volunteer-run project. It is sometimes tempting to reply mails in a
haste and making ironic remarks to drive your points further. But
mails such as this one are not welcome in Debian. Please assume good
faith, and treat everybody with
tags 763956 + pending
thanks
Sorry! I have fixed it in our working tree; it will be included in the
next upload.
Thanks,
signature.asc
Description: Digital signature
Package: cifs-utils
Version: 2:6.4-1
Severity: minor
The file shipped as /usr/share/doc/cifs-utils/README is useless in a
Debian system, as its main content is the build instructions when
building from the Git tree. It does have pointers to project
resources, but I do not feel they are worth the
Package: wnpp
Severity: wishlist
Owner: Gunnar Wolf gw...@gwolf.org
* Package name: drupal8
Version : 8.0
Upstream Author : Dries Buytaert dr...@drupal.org
* URL : http://www.drupal.org/
* License : GPLv2
Programming Lang: PHP
Description : fully
Package: lintian
Version: 2.5.24
Severity: normal
When Lintian finds a Python package using dh has a ${python:Depends}
dependency, it suggests adding a build-dependency on
python-support. However, adding said build-dependency results on
build-depends-on-obsolete-package, suggesting to use
tags 747736 + unreproducible
thanks
Hi,
I have attempted to build this package on a clean chroot, and found no
problem (and thus would like to confirm with you whether this RC bug
report can be closed).
What I found in your failure build log is that all of the failing
tests I checked mention:
tags 751480 wontfix
thanks
Simon Hollenbach dijo [Fri, Jun 13, 2014 at 01:57:21PM +0200]:
Dear Maintainer,
At debian-u...@lists.debian.org, it was discussed
[ https://lists.debian.org/debian-user/2014/06/msg00856.html ff]
that the current linux source package for wheezy could not be
Hi Bruno,
* Package name: drmips
Version : 1.2.1
Upstream Author : Bruno Nova brunomb.n...@gmail.com
* URL : https://bitbucket.org/brunonova/drmips/
* License : GPL
Programming Lang: Java
Description : Educational MIPS simulator - DrMIPS
(...)
Holger Levsen dijo [Mon, Jun 09, 2014 at 01:20:13PM +0200]:
Hi Gunnar,
will you also ask for the removal of imsniff from stable and oldstable?
As long as there is still a final oldstable pointrelease scheduled, I think
this makes sense.
Right... It is a useless package. I did not think
Holger Levsen replied to my bug report on imsniff suggesting my
removal request should also be extensive to stable and oldstable:
will you also ask for the removal of imsniff from stable and oldstable?
As long as there is still a final oldstable pointrelease scheduled, I think
this makes
Package: imsniff
Version: 0.04-6
Severity: grave
Justification: renders package unusable
In March 2013, Microsoft dropped support for the MSN chat
protocol. This package deals only with this protocol, which is no
longer used.
I will be filing a request for package removal given this package has
Package: ftp.debian.org
Severity: normal
Note that I'm not part of the QA team, so am unsure if this request
should be RoQA — But am doing it because of QA.
imsniff's description reads:
The imsniff program can be used to log IM activity on the
network. It uses libpcap to capture packets and
Package: wnpp
Severity: wishlist
Owner: Gunnar Wolf gw...@gwolf.org
* Package name: pcredz
Version : 20140606
Upstream Author : Laurent Gaffie laurent.gaf...@gmail.com
* URL : http://github.com/lgandx/PCredz
* License : GPLv3+
Programming Lang: Python
Package: mate-desktop-environment
Version: 1.8.0+2~bpo70+1
Following up on the thread in the mailing list:
are there any reasons for the »strange« package description in
mate-desktop-environment (and more)
The MATE Desktop Environment, a non-intuitive and unattractive desktop
for users,
Salvatore Bonaccorso dijo [Wed, May 21, 2014 at 07:18:46AM +0200]:
the following vulnerabilities were published for collabtive.
CVE-2014-3246[0]:
| SQL injection vulnerability in Collabtive 1.2 allows remote
| authenticated users to execute arbitrary SQL commands via the folder
| parameter
tags 746993 + pending
thanks
Fixed in our working tree. Thanks!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: lintian
Version: 2.5.22.1
Severity: minor
Tags: patch
The Files-Excluded field in debian/copyright is used to exclude files
from our not-so-pristine upstream source. It is meant to discard
non-DFSG files. The field will be ignored by uscan if the copyright
file is not declared as
reopen 699286
severity 699286 wishlist
tags 699286 wontfix
thanks
I'm very sorry, this bug... does not seem ever likely to go away. I
uploaded 7.27+dfsg-1, which did away with this embedded copy, but
horribly broke Drupal for everyone. Turns out, they have a hard
dependency on the 1.4.4 version.
David Prévot dijo [Tue, Apr 15, 2014 at 04:25:47PM -0400]:
Hi Mark,
Package: owncloud
Version: 5.0.14.a+dfsg-1~bpo70+2
(...)
The package may need a dependency against php-mdb2-driver-mysql (=
1.5.0b4-1), can you please confirm the install goes smoothly with a more
recent
tags 738921 + wontfix
thanks
Hi,
Drupal currently depends on you having installed either php5-mysql or
php5-pgsql, either of them is enough to get a successful Drupal
installation. Of course, it would be desireable not to prompt you for
a DB driver that's currently not available... But we don't
tags 738918 + pending
thanks
Thanks for bringing this to our attention, and (at the same time) a
big apology for not noting this earlier! I have fixed this in our
working tree; please bear a bit with an updated package, as I'm
looking into another important bug that has to be fixed soon.
Just
Package: lintian
Version: 2.5.22.1
Severity: minor
Drupal7 triggers two Lintian checks in the W privacy-breach-generic
category. The messages are:
usr/share/drupal7/modules/aggregator/tests/aggregator_test_atom.xml
example.org/
Hi,
I will try to contact upstream to fix this bug ASAP. I cannot,
however, find the files you mention in tinymce:
$ apt-get source tinymce
$ cd tinymce-3.4.8+dfsg-0
$ find . -name jsval.js
$ find . -name mycalendar.js
$ find . -name window.js
How did you find them to be a part of tinymce?
Gunnar Wolf dijo [Sat, Apr 12, 2014 at 10:44:52AM -0500]:
(...)
I *do* see some other minified javascripts in the same directory:
prototype.php includes Prototype 1.6.0.3 (we currently ship 1.7.1),
although I don't understand why it has a PHP header...
(...)
OK, and I see in debian/copyright
Daniel Pocock dijo [Thu, Apr 10, 2014 at 12:40:27PM +0200]:
Hi Gunnar,
I just saw your comment on this bug from February 18
Personally, I don't think it is enough to say that a package is not
using some artifacts from the source tarball - while it is a technically
valid argument, it would
FWIW, this list might prove useful, and also point at libraries not
yet packaged:
drupal7$ for js in $(find . -name *.min.js); do
js=$(basename $js)
echo -n $js ⇒
found=$(apt-file search $js|cut -f 1 -d :|grep -v ^drupal7)
if [
Matteo F. Vescovi dijo [Fri, Mar 28, 2014 at 08:47:31AM +0100]:
I didn't forget you... the simple answer is that I don't know how to fix
this, if there's a fix ;-)
Anyhow, given that it's a python-related issue (iirc), could you please
test if v2.70 release (now in experimental) changes this
Package: pitivi
Version: 0.15.2-0.2
Severity: normal
I am trying to make a video out of several files. As is often the
case, the different parts of the video overlap in time, but some
finish before others.
I know a bug report should be self-contained, but OTOH I cannot paste
here 300MB of data
Forgot to comment about this for too long — Blender does /not/ run
either on armel. But it also fails to die — I left it (apparently)
running for over a full day, and it didn't seem to make anything.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
reopen 730960
tags 730960 + pending
thanks
David Suárez dijo [Fri, Mar 14, 2014 at 07:29:52PM +0100]:
Maybe I miss something, but on current unstable version (0.6.5-7), we have:
Vcs-Browser: http://git.debian.org/?p=pkg-ruby-extras/ruby-bdb.git;a=summary
Homepage:
Source: ruby-bdb
Version: 0.6.6-1
Severity: serious
Justification: FTBFS on amd64
Attempting to build this package on AMD64, I got the following
results:
88
/usr/bin/install -c -m 0755 bdb.so ./.gem.20140313-22704-1exw4lh
make[1]:
Package: devscripts
Version: 2.14.1
Severity: normal
Tags: patch
For keyring-maint work, we gpg-sign each individual commit to the
repository. We were until now using a Bazaar repository, but as we are
switching to Git, we can no longer specify that commit messages should
be signed by default.
I
tags 741040 + pending
thanks
I have just pushed my patch in the Git repo.
signature.asc
Description: Digital signature
althaser dijo [Mon, Mar 03, 2014 at 09:40:54PM +]:
Hey Gunnar,
Could you please still reproduce this issue with newer rhythmbox version
like 3.0.1-1+b1 ?
Hi,
Last.fm no longer supports service to my country, so I am not able to
check it :-(
--
To UNSUBSCRIBE, email to
One more data point: I installed an armel chroot in the same machine
where Blender is segfaulting on me, and it seems to work fine. That
means, Blender is currently running and trying to render an image... I
guess it will take quite a bit to succeed, having (the software) no
hardfloat support.
found 739194 2.69-4
thanks
I did a clean Sid reinstall, and the bug is still present in the
current version.
Blender now attempts to generate a file to aid debugging, although it
crashed too early for this file ot be of use:
$ blender -noaudio -b
Color management: using fallback mode
While I continue to learn the basics of gdb, this seems to confirm a
stack overflow: Several of the threads have corrupt stacks.
(gdb) thread apply all backtrace
Thread 6 (Thread 0x326fd240 (LWP 4977)):
#0 0x2b1adf94 in __libc_do_syscall () from
/lib/arm-linux-gnueabihf/libpthread.so.0
#1
I'm providing some further data points, guided by the kind souls in
#debian-arm ;-)
After installing gdb, blender-dbg and python3.2-dbg, I ran blender
through gdb, and got the following output:
$ gdb --args blender -b -noaudio
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software
Hi Bastien,
I am still not finished fixing this bug (and have not yet tested if my
changes will work fine as they are), but would like your
(+ftpmasters') input on whether what I'm doing is enough — I hope to
avoid needing to repackage upstream's sources. Please refer to my
commit in the Drupal7
Subject: blender: Segfaults at startup on armhf
Package: blender
Version: 2.63a-1
Severity: important
I'm trying to test Blender's performance under an armhf machine;
sadly, whatever I do to try and start Blender up results in a
segfault.
Either starting Blender up with a file to process or
Cleto Martín dijo [Mon, Feb 03, 2014 at 08:52:41PM +]:
Package: wnpp
Severity: wishlist
Owner: Cleto Martín cl...@debian.org
* Package name: telegram-cli
Version : 0.1
Upstream Author : Vitaly Valtman
* URL : https://github.com/vysheng/tg
* License
About to upload the package with this correction, thanks to Ian for
noticing it!
Ian: I do not believe this is worth a stable update, but if you
insist, please insist me on doing so, and I'll most probably push it.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
tags 736325 + confirmed
thanks
Arne Nordmark dijo [Wed, Jan 22, 2014 at 10:55:01AM +0100]:
Package: dh-make-drupal
Version: 1.7-1
Severity: normal
Developer versions of modules are detected as both recommended and
developer,
and selected over recommended versions, when scanning the
Package: collabtive
Version: 1.2-1
Severity: important
I'm quoting here a mail sent directly to me by David López. This clear
mistake of mine clearly makes several components of Collabtive
unusable by anybody but myself :-|
First of all my apologies for this message but I'm not sure if I must
Package: flvtool2
Version: 1.0.6-4
Severity: important
Tags: patch
Hi,
Your package is built using the obsolete setup.rb framework, and
depends on the ruby1.8.
Ruby1.8 is scheduled to be removed before the Jessie release. You can
apply the patch I am inlining here to make it work under
Package: ecasound
Version: 2.9.0-1
Severity: important
Tags: patch
Hi,
Your package depends on the obsolete 1.8 version of Ruby.
Ruby1.8 is scheduled to be removed before the Jessie release. You can
apply the trivial patch I am inlining here to make it work under newer
Ruby releases (including
Alessandro Ghedini dijo [Thu, Dec 05, 2013 at 07:16:50PM +0100]:
Ruby1.8 is scheduled to be removed before the Jessie release. You can
apply the trivial patch I am inlining here to make it work under newer
Ruby releases (including 1.9.1, which will be Jessie's default).
This patch also
ruby2.0 [ruby-interpreter]2.0.0.299-2
thin recommends no packages.
thin suggests no packages.
-- debconf-show failed
From 984ff8a1a01e01d3510733388338bc6d409b1fba Mon Sep 17 00:00:00 2001
From: Gunnar Wolf gw...@debian.org
Date: Tue, 19 Nov 2013 11:54:14 -0600
Subject: [PATCH] Added a status
FWIW, this patch includes fixing the Lintian warning
(init.d-script-does-not-source-init-functions) currently reported for
this package.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
James Hunt dijo [Mon, Oct 28, 2013 at 09:35:37AM +]:
Thanks Jonathan,
However, it appears the updated package hasn't hit the archive yet?
Hi James,
According to what I see, your key was uploaded to the Debian keyring
servers on October 7. Not every keyring upload is accompanied by a
Simon Paillard dijo [Mon, Oct 14, 2013 at 09:16:19PM +0200]:
While ftp.mx is managed by mmc.geofisica.unam.mx since July, I cannot access
http://debian.unam.mx/debian/project/trace/
Could you fix it ?
Hi Simon,
As I have said to the relevant people several times... I don't
understand why we
Tomas Pospisek dijo [Fri, Oct 11, 2013 at 03:46:32PM +0200]:
according to popcon there are a few user using the package. I don't
know if the number there is statistically relevant - or in other
words if those users really *are* using the package.
If we leave the package in Debian as is, then
Package: ruby-inline
Version: 3.11.2-2
Severity: important
Tags: upstream
Although ruby-inline can be required from Ruby2.0 code, trying to
actually use it fails:
$ irb2.0
require 'inline'
= true
Inline
= Inline
Inline.inline :C do;end
RuntimeError: unsupported ruby version: 2.0.0
tags 720250 + confirmed
thanks
Hi,
I confirm I stumbled upon this problem as well. It is caused by
ruby-inline, where I filed it as #725115. I am not just reassigning as
there are subtleties to both sides of the problem :-|
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
I tried to upload to the newest upstream release, 3.12.2, but the bug
behaviour persists.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
; added dependency on dpkg-dev to
+include build-hardening flags
-- Gunnar Wolf gw...@debian.org Mon, 30 Sep 2013 17:32:27 -0500
diff --git a/debian/compat b/debian/compat
index 7f8f011..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-7
+9
diff --git a/debian/control b
Tomas Pospisek dijo [Sat, Sep 14, 2013 at 12:52:52PM +0200]:
Hello Gunnar and dear Ruby maintainers,
I'm currently off, travelling the world. Possibly I will try to
bring my Ruby package up to speed, but more probably I won't.
Finding the time and calm, internet and AC current is too much of
, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
Gunnar Wolf • gw...@gwolf.org • (+52-55)5623-0154 / 1451-2244
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
tags 722378 + pending
thanks
Thank you very much for your work!
I'm tagging this bug as 'pending'. Once 722437 is dealt with, can I
ask you to close 722378?
Of course, in some time I'll go over the list and close whatever needs
to be closed... But given you will get notice for this, you might
Package: libroot-bindings-ruby-dev
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Debian Science Maintainers,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much
Package: libamrita2-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi TANIGUCHI Takaki,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the
Package: libneedle-extras-ruby1.8
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Tatsuki Sugiura,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for
Package: libmapscript-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Debian GIS Project,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the
Package: libobexftp-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Hendrik Sattler,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the
Package: libsvn-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Peter Samuelson,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the maintainers
Package: libwebapp-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi NIIBE Yutaka,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the maintainers
Package: libabstract-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Bryan McLellan,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the
Package: libsuikyo-ruby1.8
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Masahito Omote,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the
Package: libgv-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi David Claughton,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the maintainers
Package: librrd-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Debian RRDtool Team,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the
Package: libescape-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi NIIBE Yutaka,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the maintainers
Package: libtcltk-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi akira yamada,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the maintainers
Package: libposixlock-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Tomas Pospisek,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the
Package: libhtree-ruby1.8
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi NIIBE Yutaka,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the
Package: libzip-ruby1.8
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Tatsuki Sugiura,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the
Package: libvorbisfile-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Tatsuki Sugiura,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the
Package: liblangscan-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi NIIBE Yutaka,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the
Package: libmp3info-ruby1.8
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Gustavo Franco,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the
Package: libraspell-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Alex Pennace,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the
Package: libmaruku-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Debian Ruby Extras Maintainers,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier
Package: libhtml-htmltokenizer-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Deepak Tripathi,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for
Package: libamazon-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Dafydd Harries,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the
301 - 400 of 1232 matches
Mail list logo
