Package: ruby-gitlab,python-gitlab
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 1:1.3.0-1
Control: found -1 4.2.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-factory-bot
Version: 4.8.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + ruby-factory-girl
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the
Source: ruby-influxdb
Version: 0.3.16-1
Severity: serious
Justification: fails to build from source
Hi,
ruby-influxdb/experimental FTBFS with ruby2.5 as the default ruby:
Failures:
1) InfluxDB::Client#full_url escapes params
Failure/Error: expect(url).to
Followup-For: Bug #884514
Control: reopen -1
Control: affects -1 + ruby-fog
No longer shipping the file in ruby-fog is only half of the fix. Now
ruby-fog-aws still needs Breaks+Replaces: ruby-fog (<< 1.42.0).
Andreas
___
Pkg-ruby-extras-maintainers
Source: ruby-rspec
Version: 3.5.0c3e0m0s0-1
Severity: serious
Tags: sid buster experimental
Justification: fails to build from source
Control: found -1 3.6.0c0e0m0s0-1~exp1
Control: block 888531 with -1
Hi,
ruby-rspec in both sid and experimental FTBFS due to test failures
with ruby2.5 as the
Source: ruby-faraday
Version: 0.13.1-1
Severity: serious
Justification: fails to build from source
Hi,
ruby-faraday/experimental recently started to FTBFS:
┌──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rb
Package: ruby-fog-aws
Version: 2.0.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
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries
Package: ruby-licensee
Version: 8.9.0-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
1m12.9s ERROR: FAIL: Broken symlinks:
Package: ruby-psych
Version: 2.2.4-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m27.6s ERROR: FAIL: Broken symlinks:
Source: ruby-grape
Version: 0.19.2-2
Severity: serious
Justification: fails to build from source
Hi,
ruby-grape/experimental FTBFS in a current sid+experimental environment.
Please see the attached build log for details.
Andreas
ruby-grape_0.19.2-2.log.gz
Description: application/gzip
Source: ruby-openid-connect
Version: 1.1.3-1
Severity: serious
Justification: fails to build from source
Hi,
the last upload of ruby-openid-connect did FTBFS:
https://buildd.debian.org/status/fetch.php?pkg=ruby-openid-connect=all=1.1.3-1=1505764236=0
This looks like an insufficiently versioned
Package: ruby-nmatrix
Version: 0.1.0~rc3-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
ruby-nmatrix FTBFS (at least) since GCC 7 was made the default compiler:
In file included from math.cpp:125:0:
math/idamax.h: In instantiation of 'int
Source: ruby-net-ssh
Version: 1:4.2.0-1
Severity: serious
Justification: fails to build from source
Hi,
the last upload of ruby-net-ssh does FTBFS:
https://buildd.debian.org/status/fetch.php?pkg=ruby-net-ssh=all=1%3A4.2.0-1=1505233484=0
Package: ruby-sentry-raven
Version: 2.5.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...):
Package: gitlab
Version: 8.13.11+dfsg1-11
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-server
Version: 2.7.4-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 the
Package: gitlab
Version: 8.13.11+dfsg1-10
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: gitlab
Version: 8.13.11+dfsg1-10
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: gitlab
Version: 8.13.11+dfsg1-9
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-mustermann,ruby-mustermann19
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 1.0.0-2
Control: found -1 0.4.3+git20160621-1
Hi,
automatic installation tests of packages that share a file and at the
same time do not conflict by their package
On Sat, 8 Jul 2017 08:28:17 +0200 Lucas Nussbaum wrote:
> Source: ruby-rest-client
> Version: 1.8.0-3
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170707 qa-ftbfs
> Justification: FTBFS on amd64
Hi Lucas,
you files a bunch
Package: schleuder
Version: 3.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' to 'jessie' to 'stretch' to 'buster'.
It installed fine in 'wheezy', and upgraded to 'jessie' and
Package: diaspora
Version: 0.6.0.1+debian-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed when
triggered.
>From the attached log (scroll to the bottom...):
Processing triggers for libc-bin (2.24-12) ...
Package: diaspora-installer
Version: 0.6.6.0+debian1
Severity: grave
Tags: security
Justification: user security hole
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package installs
world-writable files, including a bunch of .rb scripts,
On 2017-05-02 20:02, Antonio Terceiro wrote:
> Can you clarify exactly why you think a dangling symlink should warrant
> severity serious?
If the target is supposed to be there (because there is a
Depends: target-shipping-package), usually something will be broken if
the link was messed up. If
Package: ruby-prof
Version: 0.16.2+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m20.4s ERROR: FAIL: Broken symlinks:
Package: camping
Version: 2.1.580-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m47.8s ERROR: FAIL: Broken symlinks:
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+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:
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...):
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
Package: gitlab
Version: 8.13.11+dfsg-2
Severity: serious
Hi,
the postinst uses several
export $(cat $conffile)
constructs which are very fragile to the file content. This breaks on
comments, quoted multi-word strings, and probably many more things.
Since adding comments while making local
Package: ruby-rails-assets-punycode
Version: 1.3.2-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m39.6s ERROR: FAIL: Broken
Package: ruby-haml
Version: 4.0.7-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m48.2s ERROR: FAIL: Broken symlinks:
Package: ruby-jar-dependencies
Version: 0.3.10-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
On 2017-03-09 10:27, Pirate Praveen wrote:
>> Having briefly looked at the postinst script, it appears to me that all
>> the nginx_* variables are not set at all ...
>
> nginx_* variables are set in gitlab-debian.conf. Since this version of
> gitlab makes a change in those variables postinst
On 2017-03-04 13:27, Pirate Praveen wrote:
> On ശനി 04 മാര്ച്ച് 2017 04:25 വൈകു, Andreas Beckmann wrote:
>> Yes, upgrading packages must work. And especially between versions in
>> testing (which will become relevant if 8.13.11+dfsg-4 migrates to
>> testing). And later on fro
Package: diaspora,diaspora-installer
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 0.6.0.1+debian-1
Control: found -1 0.6.3.0+debian1
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this
On 2017-03-04 08:22, Pirate Praveen wrote:
> On വെള്ളി 03 മാര്ച്ച് 2017 10:00 വൈകു, Andreas Beckmann wrote:
>> Oops, wrong template.
>>
>> It installed fine in 'stretch' (8.13.11+dfsg-2), then the upgrade to
>> 'sid' (8.13.11+dfsg-4) fails.
>
> Can you please ex
Control: reopen -1
On 2017-03-03 05:40, Pirate Praveen wrote:
> On Thu, 02 Mar 2017 22:35:55 +0100 Andreas Beckmann <a...@debian.org> wrote:
>> during a test with piuparts I noticed your package fails to upgrade from
>> 'jessie'.
>> It installed fine in 'jessie', t
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: 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: 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-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: 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
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: 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: 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: 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-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+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
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
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
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
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
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 #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 #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 #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 #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 #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 #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 #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 #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: 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
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
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: 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
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-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: 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.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
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: 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.
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:
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
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-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
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-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
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
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
>
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: 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
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: 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
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
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
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-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
1 - 100 of 136 matches
Mail list logo