Package: ruby-blankslate
Version: 2.1.2.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite
Package: redmine
Version: 1.3.0+dfsg1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
From
Package: ruby-pdf-writer
Version: 1.1.8+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to
Package: ruby-activesupport-2.3,ruby-activerecord-2.3
Version: 2.3.14-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'squeeze'.
It installed fine in 'squeeze', then the upgrade to 'sid' fails
Package: rdtool-elisp
Version: 0.6.34-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'squeeze'.
It installed fine in 'squeeze', then the upgrade to 'sid' fails.
From the attached log (scroll to
Package: libsdl-ruby
Version: 2.1.1.1-1
Severity: grave
Tags: sid
Justification: renders package unusable
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
* ruby-sdl breaks libsdl-ruby ( 2.1.1.1-2~)
*
Package: haml-elisp
Version: 1:3.0.15-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'squeeze'.
It installed fine in 'squeeze', then the upgrade to 'sid' fails.
From the attached log (scroll to
Source: haml-elisp
Followup-For: Bug #672251
Hi,
found another occurrence during the test of the sass-elisp
package in sid. That should be easier to reproduce.
Setting up haml-elisp (1:3.0.15-3) ...
Install haml-elisp for emacs
Skipping byte-compilation for emacs: Not supported
Install
Package: chef
Version: 0.10.10-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package left unowned
directories on the system after purge, which is a violation of
policy 6.8:
Package: libchef-ruby,libchef-ruby1.8
Version: 0.10.10-1
Severity: grave
Tags: sid
Justification: renders package unusable
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
Package: libchef-ruby
Version:
Package: chef
Version: 0.10.10-2
Followup-For: Bug #675365
Hi,
/var/lib/chef/ is still there ...
0m42.0s ERROR: FAIL: Package purging left files on system:
/var/lib/chef/ not owned
Andreas
chef_0.10.10-2.log.gz
Description: GNU Zip compressed data
user debian...@lists.debian.org
usertag 679606 piuparts
clone 679606 -1
reassign 679606 ruby-hpricot 0.8.6-2
fixed 679606 0.8.6-3
reassign -1 ruby-fast-xs 0.8.0-2
reopen -1
thanks
cloning and reassigning to ruby-fast-xs which needs to add
Breaks/Replaces since it takes over some files from
Package: chef-solr
Version: 10.12.0+dfsg-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install.
From the attached log (scroll to the bottom...):
[...]
Setting up rabbitmq-server (2.8.4-1) ...
Package: redmine-sqlite
Version: 2.3.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
From
Package: feed2imap
Version: 1.0-2
Severity: serious
Tags: sid jessie
User: debian...@lists.debian.org
Usertags: piuparts
Control: close -1 1.2-1
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
It depends on ruby-feedparser, but that breaks feed2imap (
Package: redmine
Version: 2.3.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + redmine-mysql
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a
Package: ruby-hoe
Version: 3.8.0-1
Severity: serious
Tags: sid
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
0m16.1s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpWTr6TG',
'apt-get', '-y',
Source: ruby-prof
Version: 0.13.1-1
Severity: serious
Hi,
ruby-prof FTBFS on all architectures except powerpc:
https://buildd.debian.org/status/package.php?p=ruby-prof
Excerpt from
https://buildd.debian.org/status/fetch.php?pkg=ruby-profarch=i386ver=0.13.1-1stamp=1387838705
make DESTDIR=
Package: ruby-actionpack-action-caching
Version: 1.1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' fails
because it tries
Followup-For: Bug #749994
Control: found -1 4.0.5.1-1
Install tdiary-mode for emacs24
install/tdiary-mode: Handling install for emacsen flavor emacs24
ERROR: install script from tdiary-mode package failed
dpkg: error processing package emacs24-nox (--configure):
subprocess installed
Control: notfound -1 4.0.5.1-1
Control: close -1 4.0.5.1-1
On 2014-11-04 11:31, Andreas Beckmann wrote:
Install tdiary-mode for emacs24
install/tdiary-mode: Handling install for emacsen flavor emacs24
ERROR: install script from tdiary-mode package failed
dpkg: error processing package
Followup-For: Bug #767842
Similar problems exist with ruby-actionpack-3.2:
Selecting previously unselected package ruby-actionpack.
Unpacking ruby-actionpack (from .../ruby-actionpack_2%3a4.1.6-2_all.deb) ...
Replacing files in old package ruby-actionpack-3.2 ...
Selecting previously
Package: ruby-twitter
Version: 5.11.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' fails
because it tries to overwrite
Package: ruby-activemodel,ruby-activesupport
Version: 2:4.1.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks
Hi,
during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package, leaving
On 2014-11-11 13:55, Antonio Terceiro wrote:
The Breaks: relationships were there originally, but removing them was
how I achieved a successfull upgrade from wheezy in the first place,
after some hours of trial and error. aptitude would figure the upgrade
out just fine, but apt-get wouldn't.
Package: ruby-fog-sakuracloud,ruby-fog
Version: 0.1.1-1
Severity: serious
Tags: sid
User: trei...@debian.org
Usertags: edos-file-overwrite
Architecture: amd64
Distribution: sid
Hi,
automatic installation tests of packages that share a file and at the
same time do not conflict by their package
Package: ruby-simple-navigation
Version: 3.11.0-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
your package has
Depends: ruby-rails-3.2 | ruby-sinatra
but ruby-rails-3.2 is not in jessie and will go away from sid at some
point eventually. Please make ruby-sinatra
On 2014-11-17 19:03, gregor herrmann wrote:
On Sun, 02 Nov 2014 22:52:13 +0100, Andreas Beckmann wrote:
Unpacking ruby-actionpack-action-caching (1.1.1-1) ...
dpkg: error processing archive
/var/cache/apt/archives/ruby-actionpack-action-caching_1.1.1-1_all.deb
(--unpack):
trying
On 2014-11-14 20:51, Antonio Terceiro wrote:
The following packages will be REMOVED:
gcc-4.7-base
The following packages have been kept back:
rails
The problematic package is ruby-activesupport-2.3 which gets a higher
score (score=21) than ruby-activesupport (score=11) (probably due to a
Package: ruby-jbuilder,ruby-responders
Version: 2.0.2-1
Severity: serious
Tags: sid
User: trei...@debian.org
Usertags: edos-file-overwrite
Architecture: amd64
Distribution: sid
Hi,
automatic installation tests of packages that share a file and at the
same time do not conflict by their package
Source: tdiary
Version: 4.0.5.1-1
Severity: normal
Tags: experimental
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + tdiary-contrib
tdiary-contrib/experimental is not installable:
The following packages have unmet dependencies:
tdiary-contrib : Depends: tdiary (= 4.0)
Package: ruby-fog-voxel
Version: 0.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it
Package: ruby-fog,ruby-fog-xml
Version: 1.24.0-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 0.1.1-1
Architecture: amd64
Distribution: experimental
Hi,
automatic installation tests of packages that share a file and at the
same time do not conflict
Package: ruby-actionpack-page-caching
Version: 1.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'sid' fails
because it tries to
Package: ruby-fog-storm-on-demand
Version: 0.1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails
because it tries to
Package: rex,rexical
Version: 1.0.5-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 1.2.1-1
Architecture: amd64
Distribution: sid
Hi,
automatic installation tests of packages that share a file and at the
same time do not conflict by their package
Package: ruby-fog-vmfusion
Version: 0.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails
because it tries to
Package: rhc
Version: 1.35.4-2
Severity: grave
Tags: sid
Justification: renders package unusable
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
0m24.1s ERROR: Command failed (status=100): ['chroot',
Package: diaspora-common
Version: 0.5.0.1+debian1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the
Package: ruby-facebox-rails
Version: 0.2.0-1
Severity: serious
Tags: sid
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is not
installable in sid:
1m9.9s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmp_8jCeg',
'apt-get', '-y',
Package: ruby-fog-powerdns
Version: 0.1.1-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: affects -1 + conserver-client
Hi,
automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency
Source: ruby-gnome2
Version: 2.2.5-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
ruby-gnome2 FTBFS in the arch:all buildd:
https://buildd.debian.org/status/fetch.php?pkg=ruby-gnome2=all=2.2.5-2=1447078649
[...]
debian/rules
control: tag -1 sid stretch
On Sat, 31 Oct 2015 13:06:55 -0500 Adam Majer wrote:
> Furthermore, rebuilding does not fix the bug at root of the
> problem. If MySQL get upgraded to another minor version while keeping
> its soname as is (ie. ABI doesn't change), ruby-mysql will
Package: ruby-mousetrap-rails
Version: 1.4.6-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old
Control: found -1 0.5.3.0+debian1
On 2015-09-07 12:04, Pirate Praveen wrote:
> tested on jesse and sid machines and everything went fine.
I can still reproduce the problem in piuparts, are you sure you used a
fresh database server installation?
piuparts does its tests with
Control: severity -1 serious
Control: clone -1 -2
Control: reopen -2
Control: reassign -1 ruby-devise 3.5.2-2
Control: fixed -1 3.5.2-3
This bug needs a fix on the ruby-activerecord-session-store side, too,
by adding
Breaks+Replaces: ruby-devise (<< 3.5.2-3~)
otherwise you can still run into it
Source: gem2deb
Version: 0.30.2
Severity: serious
Justification: fails to build from source
Hi,
gem2deb FTBFS everywhere:
https://buildd.debian.org/status/package.php?p=gem2deb=unstable
test: running dh-make-ruby against a directory should get the package name
correctly. :F
Package: gitlab
Version: 8.8.2+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From
Package: gitlab
Version: 8.8.2+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From
Package: gitlab
Version: 8.8.2+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From
Package: ruby-aws
Version: 2.10.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: clone -1 -2
Control: reassign -2 ruby-base32 0.3.2-2
Control: retitle -2 ruby-base32: ships /usr/lib/ruby/vendor_ruby/version.rb
Hi,
during a test with piuparts I noticed your
Package: gitlab
Version: 8.8.2+dfsg-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From
On Wed, 25 Nov 2015 10:59:36 -0200 Antonio Terceiro
> according to
> https://packages.debian.org/search?searchon=contents=fast_xs.so=filename=unstable=any
> sh4 is the only architecture where ruby-hpricot ships that file.
That output is seriously outdated (#810590), or did you see a ruby 2.2.0
Control: retitle -1 ruby-hpricot: package contains fast_xs.so if built with
DEB_BUILD_OPTIONS=nocheck
Control: tag -1 sid stretch
On Thu, 24 Dec 2015 20:40:28 + (UTC) Thorsten Glaser wrote:
> Unpacking ruby-hpricot (0.8.6-5+b1) ...
> dpkg: error processing archive
>
Package: diaspora-common
Version: 0.5.6.3+debian1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
Package: ruby-mousetrap-rails
Version: 1.4.6-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old
Package: diaspora-installer
Version: 0.5.3.0+debian1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the
Package: ruby-bcat
Version: 0.6.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed the maintainer scripts of your
package don't support all the ways they are going to be called.
See policy 6.5 at
On 2016-02-25 08:36, Pirate Praveen wrote:
> ruby-mousetrap-rails is not part of any stable release. So should I
> really handle this upgrade case?
Yes. Especially since the fix should be trivial.
Andreas
___
Pkg-ruby-extras-maintainers mailing list
No, you didn' get the point of this bug. Please install the package by
copy+pasting the name from the subject :-)
Andreas
PS: Query Structured Language
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
Source: passenger
Version: 5.0.22-1
Severity: important
Hi,
passenger FTBFS on kfreebsd-*:
https://buildd.debian.org/status/fetch.php?pkg=passenger=kfreebsd-amd64=5.0.22-1=1449534348
https://buildd.debian.org/status/fetch.php?pkg=passenger=kfreebsd-i386=5.0.22-1=1449530910
c++ -o
Package: diaspora
Version: 0.5.5.1+debian-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
On 2016-03-01 06:13, Balasankar C wrote:
> On Thu, 25 Feb 2016 13:07:39 +0100 Andreas Beckmann <a...@debian.org>
> wrote:
>> On 2016-02-25 08:36, Pirate Praveen wrote:
>>> ruby-mousetrap-rails is not part of any stable release. So should
>>> I really handle this
On 2016-03-01 13:15, Pirate Praveen wrote:
>
>
> Control: severity -1 wishlist
>
> On 2016, മാർച്ച് 1 5:19:35 PM IST, Andreas Beckmann <a...@debian.org> wrote:
>
>> The test was done upgrading from the previous version in testing to sid
>> before the curre
Followup-For: Bug #817012
Control: found -1 1.5.1-2
Hi,
removal of the old package is not sufficient, you still need to add
Breaks+Replaces:
Selecting previously unselected package ruby-amqp.
Preparing to unpack .../ruby-amqp_1.5.1-2_all.deb ...
Unpacking ruby-amqp (1.5.1-2) ...
dpkg:
Package: diaspora-common
Version: 0.5.7.1+debian2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package modifies files it has
shipped in /usr.
>From the attached log (scroll to the bottom...):
1m54.3s ERROR: FAIL: debsums
Package: gitlab
Version: 8.5.8+dfsg-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From
Followup-For: Bug #830931
Similar problems in jessie:
GEM_PATH= ruby -e 'gem "ruby2ruby"'
/usr/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find
'ruby2ruby' (>= 0) among 8 total gem(s) (Gem::LoadError)
from /usr/lib/ruby/2.1.0/rubygems/dependency.rb:309:in
On 2016-07-14 18:34, Debian Bug Tracking System wrote:
>* Move config files to /usr/share/doc as examples and
> copy them to /var/lib for modification (Closes: #821086)
Was this a typo (and you actually put them in /usr/share/gitlab) or did
you just make another RC bug? The package may
Package: gitlab
Version: 8.9.0+dfsg-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package creates the 'gitlab'
user/group as a regular user/group instead of a system one.
Package: diaspora-common
Version: 0.5.9.1+debian4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the
Package: gitlab
Version: 8.9.0+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From
Package: diaspora-common
Version: 0.5.9.1+debian2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the
Followup-For: Bug #830099
Similar problems in jessie:
ruby -e 'gem "em-http-request"'
/usr/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find
'em-socksify' (>= 0.3) among 24 total gem(s) (Gem::LoadError)
from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1295:in
Followup-For: Bug #830090
Similar problems in jessie:
ruby -e 'gem "em-spec"'
/usr/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find
'rspec' (> 2.6.0) among 13 total gem(s) (Gem::LoadError)
from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1295:in `block in
Followup-For: Bug #830067
Similar problems in jessie:
ruby -e 'gem "cassiopee"'
/usr/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find
'cassiopee' (>= 0) among 14 total gem(s) (Gem::LoadError)
from /usr/lib/ruby/2.1.0/rubygems/dependency.rb:309:in `to_spec'
Followup-For: Bug #830060
Similar problems in jessie:
ruby -e 'gem "appraisal"'
/usr/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find
'appraisal' (>= 0) among 18 total gem(s) (Gem::LoadError)
from /usr/lib/ruby/2.1.0/rubygems/dependency.rb:309:in `to_spec'
Followup-For: Bug #830238
Similar problems in jessie:
GEM_PATH= ruby2.1 -e gem\ \"stompserver\"
/usr/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find
'stompserver' (>= 0) among 8 total gem(s) (Gem::LoadError)
from /usr/lib/ruby/2.1.0/rubygems/dependency.rb:309:in
Followup-For: Bug #830097
Similar probles in jessie:
ruby -e 'gem "file-tail"'
/usr/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find
'tins' (~> 1.0) among 9 total gem(s) (Gem::LoadError)
from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1295:in `block in
Followup-For: Bug #830094
Similarproblems in jessie:
ruby -e 'gem "indentation"'
/usr/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find
'indentation' (>= 0) among 9 total gem(s) (Gem::LoadError)
from /usr/lib/ruby/2.1.0/rubygems/dependency.rb:309:in `to_spec'
Followup-For: Bug #830235
Similar problems in jessie:
ruby -e 'gem "webrobots"'
/usr/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find
'webrobots' (>= 0) among 12 total gem(s) (Gem::LoadError)
from /usr/lib/ruby/2.1.0/rubygems/dependency.rb:309:in `to_spec'
Followup-For: Bug #830088
Similar problems in jessie:
ruby -e 'gem "em-socksify"'
/usr/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find
'em-socksify' (>= 0) among 13 total gem(s) (Gem::LoadError)
from /usr/lib/ruby/2.1.0/rubygems/dependency.rb:309:in `to_spec'
Followup-For: Bug #829691
Similar problems in jessie:
ruby -e 'gem "shoulda"'
/usr/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find
'shoulda-matchers' (< 3.0, >= 1.4.1) among 10 total gem(s) (Gem::LoadError)
from
On 2016-07-10 07:11, Pirate Praveen wrote:
>> 1m24.6s ERROR: FAIL: debsums reports modifications inside the chroot:
>> /var/lib/diaspora-common/database.yml
>
> Why is this a problem? I thought only /usr/share needs to be read only.
> Which other directory I can use then for this purpose (to
Package: ruby-sass-rails
Version: 5.0.4-2
Severity: serious
Justification: fails to build from source
Hi,
tha last upload of ruby-sass-rails FTBFS on the buildds:
https://buildd.debian.org/status/fetch.php?pkg=ruby-sass-rails=all=5.0.4-2=1467374152
Followup-For: Bug #820073
Control: found -1 0.5.9.1+debian1
Hi,
now the problem has shifted to
1m24.6s ERROR: FAIL: debsums reports modifications inside the chroot:
/var/lib/diaspora-common/database.yml
Andreas
diaspora-common_0.5.9.1+debian1.log.gz
Description: application/gzip
Package: tdiary-core
Version: 4.2.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries
Package: diaspora-common
Version: 0.6.3.0+debian1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'sid' fails.
>From the attached log
Followup-For: Bug #841583
Control: block -1 with 851131
The --force problem is specific to mysql, it does not happen with
mariadb. But it fails differently on mariadb:
[...]
2017-01-18 13:52:53 140102037378944 [Note] /usr/sbin/mysqld (mysqld
10.1.20-MariaDB-3) starting as process 3768 ...
Package: diaspora
Version: 0.6.0.0+debian-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
Package: obs-worker
Version: 2.7.1-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to remove.
>From the attached log (scroll to the bottom...):
Removing obs-worker (2.7.1-6) ...
invoke-rc.d: could not
Package: obs-api
Version: 2.7.1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the
Package: obs-api
Version: 2.7.1-9
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):
Package: node-mustache,ruby-mustache
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 1.0.2-1
Control: found -1 2.3.0-1
Hi,
automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency
Package: ruby-json-pure,ruby-json
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 2.0.1+dfsg-2
Control: found -1 2.0.2+dfsg-2
Hi,
automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency
Package: diaspora-installer
Version: 0.6.0.0+debian4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package installs
world-writable files.
>From the attached log (scroll to the bottom...):
ERROR: BAD PERMISSIONS
Followup-For: Bug #856720
Control: found -1 0.6.3.0+debian4
Hi,
and there we go again ...
[...]
Precompiling assets...
W, [2017-03-30T07:12:27.702004 #19736] WARN -- : You are setting a key that
conflicts with a built-in method OmniAuth::AuthHash::InfoHash#name defined at
Package: diaspora-common
Version: 0.6.3.0+debian3
Severity: critical
Justification: breaks the whole system
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package makes havoc in the
chroot.
>From the attached log (scroll to the bottom...):
Package: diaspora-common
Version: 0.6.3.0+debian4
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package left unowned
directories on the system after purge, which is a violation of
policy 6.8:
On 2017-03-17 19:06, Debian Bug Tracking System wrote:
> gitlab (8.13.11+dfsg-6) unstable; urgency=medium
> .
>* Improve configuration file parsing by using source (Closes: #857967)
I checked the diff and it looks good, thanks.
piuparts didn't test the package, yet, and I don't plan to do
1 - 100 of 136 matches
Mail list logo