Bug#896698: deprecating needs-recommends

On Mon, Sep 17, 2018 at 10:50:01PM +0200, gregor herrmann wrote: > On Sat, 15 Sep 2018 15:40:33 +0200, Michael Biebl wrote: > > > On Thu, 30 Aug 2018 12:03:31 +0200 Paul Gevers wrote: > > > I have just pushed commit 9fade8dcb501250f704da9c77af1f8e6165dc941 that > > > documents that we want to

Bug#908826: vagrant/stable is incompatible with virtualbox/stretch-backports (now 5.2)

On Mon, Sep 17, 2018 at 03:16:05PM +0200, Lucas Nussbaum wrote: > On 15/09/18 at 09:46 -0300, Antonio Terceiro wrote: > > On Fri, Sep 14, 2018 at 05:10:48PM +0200, Lucas Nussbaum wrote: > > > Package: vagrant > > > Version: 1.9.1+dfsg-1+deb9u1 > > &

Bug#908826: vagrant/stable is incompatible with virtualbox/stretch-backports (now 5.2)

On Fri, Sep 14, 2018 at 05:10:48PM +0200, Lucas Nussbaum wrote: > Package: vagrant > Version: 1.9.1+dfsg-1+deb9u1 > Severity: normal > > Hi, > > vagrant 1.9.1+dfsg-1+deb9u1 is now incompatible with virtualbox from > stretch-backports (version 5.2.18-dfsg-1~bpo9+1). It worked fine with >

Bug#908813: [PATCH] spec: user xdelta v3 for rpm builds, too

Control: tags -1 + pending On Fri, Sep 14, 2018 at 12:39:08PM +0300, Markus Lehtonen wrote: > Package: pristine-tar > Version: 1.44 > Tags: patch > > Nowadays, it's ubiquitous and pristine-tar supports it. applied, thanks signature.asc Description: PGP signature

Bug#907846: autopkgtest: Please consider additional section for tutorial web page

On Tue, Sep 04, 2018 at 08:59:12PM +0200, Paul Gevers wrote: > Control: reassign -1 debci > > Dear Paul > > You're looking at this file: > https://salsa.debian.org/ci-team/debci/blob/master/docs/TUTORIAL.md > > It would be awesome if you could propose changes to that file instead of > the

Bug#905586: lxc: diff for NMU version 1:2.0.9-6.1

On Fri, Aug 31, 2018 at 02:42:15PM +0200, Salvatore Bonaccorso wrote: > Hi Antonio, > > On Fri, Aug 31, 2018 at 08:14:57AM -0300, Antonio Terceiro wrote: > > On Thu, Aug 30, 2018 at 10:06:15PM +0200, Salvatore Bonaccorso wrote: > > > Control: tags 905586 + pending

Bug#905586: lxc: diff for NMU version 1:2.0.9-6.1

On Thu, Aug 30, 2018 at 10:06:15PM +0200, Salvatore Bonaccorso wrote: > Control: tags 905586 + pending > > > Dear maintainer, > > I've prepared an NMU for lxc (versioned as 1:2.0.9-6.1) and > uploaded it to DELAYED/5. Thanks! > Please feel free to tell me if I should delay it longer. on the

Bug#907118: error:141a318a:ssl routines:tls_process_ske_dhe:dh key too small

On Thu, Aug 23, 2018 at 03:24:52PM -0600, dann frazier wrote: > Package: bip > Version: 0.8.9-1.1 > Severity: normal > Tags: patch > > I run bip on a stretch system, and connect to it from a hexchat client on > sid. After a recent upgrade of the client, which pulled in openssl 1.1, > hexchat

Bug#907118: error:141a318a:ssl routines:tls_process_ske_dhe:dh key too small

Control: severity -1 important Hi, I would like to reinforce the request for a stable update: - according to the openssl maintainer, this is a security issue and should be fixed in stable - without such fix, bip on stable will soon be unusable to any client using a recent enough openssl

Bug#906130: allow autopkg restrictions in debian/control

Control: tag -1 + wontfix Control: close -1 On Tue, Aug 14, 2018 at 06:46:56PM +0200, Matthias Klose wrote: > Package: autopkgtest > Version: 5.5 > > Seen when the Python autodep8 tests were enabled. Tests start failing when > these have e.g. output on stderr. It should be possible to specify

Bug#905317: autopkgtest: "flaky" restriction seems not to work when dep unsatisfiable

Control: close -1 Control: tag -1 + wontfix On Fri, Aug 03, 2018 at 10:54:44AM +0800, Ralf Treinen wrote: > Package: autopkgtest > Version: 5.4.1 > Severity: normal > > Hi, > > the flaky restriction does not seem to work in case of an unsatisfiable > test dependency. This can be observed on

Bug#905527: `apt show` fails to parse record for librust-winapi-dev (while `apt-cache show` succeeds)

On Sun, Aug 05, 2018 at 12:20:54PM -0300, Antonio Terceiro wrote: > Package: apt > Version: 1.6.3 > Severity: normal > > ~$ apt-cache show librust-winapi-dev > [... stuff ...] > ~$ apt show librust-winapi-dev > E: Unable to parse package fi

Bug#905527: `apt show` fails to parse record for librust-winapi-dev (while `apt-cache show` succeeds)

Package: apt Version: 1.6.3 Severity: normal ~$ apt-cache show librust-winapi-dev [... stuff ...] ~$ apt show librust-winapi-dev E: Unable to parse package file /var/lib/apt/lists/ftp.br.debian.org_debian_dists_unstable_main_binary-amd64_Packages (2) E: Internal Error, Unable to parse a package

Bug#905439: su from util-linux breaks autopkgtest

Control: tag -1 + moreinfo unreproducible On Sat, Aug 04, 2018 at 03:11:17PM +, Lumin wrote: > Package: autopkgtest > Version: 5.4.2 > Severity: serious > > the "su" command from util-linux breaks autopkgtest. The previous > working one comes from shadow. > > python-h5py-dbg is already the

Bug#905153: autodep8: set Restrictions: allow-stderr on generated tests

On Wed, Aug 01, 2018 at 07:53:12AM +0100, Rebecca N. Palmer wrote: > On 01/08/18 02:58, Antonio Terceiro wrote: > > FWIW, most of the supported package types do already set allow-stderr. > > From a quick look, of 4 of 9 explictly set allow-stderr, and 2 append > > `2&g

Bug#905153: autodep8: set Restrictions: allow-stderr on generated tests

On Tue, Jul 31, 2018 at 11:15:58PM +0100, Rebecca N. Palmer wrote: > Package: autodep8 > Severity: wishlist > > (Moving to a new bug: note that I have not decided whether I agree with this > proposal.) > > On 31/07/18 14:59, Paul Gevers wrote: > > Hi Rebecca, > > > > On 30-07-18 08:57, Rebecca

Bug#904921: wand: Wrong dependencies on libmagickcore-6.q16-6 instead of libmagickwand-6.q16-6

Hi On Mon, Jul 30, 2018 at 10:27:57AM -0300, Antonio Terceiro wrote: > FWIW, I intend to upload the patch below. wand is used as a test case in > the test suite of autopkgtest, and this bug causes it to fail. I noticed you are working in the git repository, so I will *not* be making

Bug#904921: wand: Wrong dependencies on libmagickcore-6.q16-6 instead of libmagickwand-6.q16-6

Hi, On Sun, Jul 29, 2018 at 10:57:44AM -0300, Antonio Terceiro wrote: > Source: wand > Version: Wrong dependencies on libmagickcore-6.q16-6 instead of > libmagickwand-6.q16-6 > Severity: serious > Justification: missing dependencies > > I think there is a typo in

Bug#904921: wand: Wrong dependencies on libmagickcore-6.q16-6 instead of libmagickwand-6.q16-6

Source: wand Version: Wrong dependencies on libmagickcore-6.q16-6 instead of libmagickwand-6.q16-6 Severity: serious Justification: missing dependencies I think there is a typo in Depends: which causes this: $ python3 -c 'from wand.image import Image' Traceback (most recent call last): File

Bug#893501: ruby2.5 FTCBFS: configures for the build architecture

Em 22 de julho de 2018 10:57:16 BRT, Chris Hofstaedtler escreveu: >Hi Helmut, > >* Helmut Grohne [180722 13:55]: >> ruby2.5 fails to cross build from source, because it fails passing >> --host to ./configure. The simple solution to this problem is >deferring >> the task to dh_auto_configure.

Bug#903408: Uploading new version of autodep8 to unstable

On Wed, Jul 11, 2018 at 09:10:46AM +0200, Rafael Laboissière wrote: > The packages that use the Octave support of autodep8 are starting to fail on > ci.d.n. This will become epidemic. Please, react to my message below. > > Cheers, > > Rafael > > * Rafael Laboissière [2018-07-10 13:21]: > >

Bug#893595: marked as done (autopkgtest doesn't handle long package names (>= 55 char) properly)

Control: reopen -1 Actually, the debci upload does *not* fix this, it just works around the limitation on the debci side. This is a limitation in *lxc*, which does not support containers names longer than 50-something characters. This should be handled in autopkgtest-virt-lxc signature.asc

Bug#897308: O: ruby-setup -- the setup.rb install tool for Ruby

On Tue, 01 May 2018 12:17:17 +0200 Vincent Fourmond wrote: > Package: wnpp > Severity: normal > > > Hello, > > I intend to orphan the ruby-setup package. It is technically > team-maintained by the Debian Ruby team, but the other listed uploader > hasn't touched the package for a very long

Bug#901030: some context

On Tue, Jun 12, 2018 at 02:34:57PM +0200, Hans-Christoph Steiner wrote: > > I agree that there can't be a Restriction for every config under the > sun. I'm thinking more like Ian, where there can be some useful chunks > with a finer grain than "needs isolation". Allowing a test definition to

Bug#899267: Reopen: Bug#899267: ruby2.5: FTBFS on kfreebsd-any

On Sun, 10 Jun 2018 23:38:18 +0200 Svante Signell wrote: > reopen -1 > found 899267 2.5.1-2 > thanks > > Hello, > > Unfortunately the patch 0006-fix-kfreebsd-build.patch was not applied, > resulting in a failing build. I'm attaching that file again, now named > 0007-fix-kfreebsd-build.patch

Bug#901030: some context

Control: severity -1 wishlist Control: tag -1 + wontfix On Fri, Jun 08, 2018 at 12:35:13PM +0200, Hans-Christoph Steiner wrote: > > This issue was discovered while working on getting autopkgtest running > smoothly in Docker containers running in Gitlab CI on salsa.debian.org: >

Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

On Sat, May 26, 2018 at 02:29:56AM +0200, Pierre-Elliott Bécue wrote: > Le mardi 22 mai 2018 à 21:16:14+0530, Vasudev Kamath a écrit : > > Hi Antonio, > > > > Antonio Terceiro <terce...@debian.org> writes: > > > > > Control: forwarded -1 > >

Bug#900046: ifupdown doesn't work inside lxc

Control: severity -1 grave On Fri, 25 May 2018 08:11:53 +0200 Ivan Sergio Borgonovo wrote: > Package: ifupdown > Version: 0.8.33 > > upgrading from 0.8.32 to 0.8.33 ifupdown doesn't work anymore inside > lxc. Downgrading fix the problem, but dpkg takes a lot in the set up

Bug#900046: ifupdown doesn't work inside lxc

root@test:~# reboot of course this is not great. The attached patch fixes the issue From d2f8480107882f65ff72607bec7504174cec8855 Mon Sep 17 00:00:00 2001 From: Antonio Terceiro <terce...@debian.org> Date: Fri, 25 May 2018 09:23:08 -0300 Subject: [PATCH] ifupdown-pre.service: only call udevadm if pr

Bug#899324: ruby-font-awesome-rails: broken with fonts-font-awesome 5

Package: ruby-font-awesome-rails Version: 4.7.0.2-1 Severity: grave Justification: renders package unusable Recently fonts-font-awesome 5 has been uploaded to ustable. There are some significant changes upstream, including but not limited to font files being renamed. fonts-font-awesome 5.0.10-4

Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

Control: forwarded -1 https://salsa.debian.org/fonts-team/fonts-font-awesome/merge_requests/1 On Sun, May 20, 2018 at 06:15:08PM -0300, Antonio Terceiro wrote: > Control: reopen -1 > > On Sun, May 20, 2018 at 10:32:38PM +0530, Vasudev Kamath wrote: > > Antonio Terceiro <t

Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

Control: reopen -1 On Sun, May 20, 2018 at 10:32:38PM +0530, Vasudev Kamath wrote: > Antonio Terceiro <terce...@debian.org> writes: > > 2) revert the changes in fonts-font-awesome in unstable, upload the > > new release to experimental, and give people a few months to

Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

Package: fonts-font-awesome Version: 5.0.10-1 Severity: grave Font-Awesome version completely changed everything, and any web applications that use it are now broken unless they go through some manual intervention. https://fontawesome.com/how-to-use/upgrading-from-4 As a maintainer of multiple

Bug#897653: tar 1.30 breaks pristine-tar

Control: tag -1 + patch On Mon, May 14, 2018 at 11:07:50AM -0700, Bdale Garbee wrote: > Paul Eggert <egg...@cs.ucla.edu> writes: > > > On 05/14/2018 07:56 AM, Antonio Terceiro wrote: > >> I still need to study the > code a bit further to try to come up with a >

Bug#898501: Broken symlinks

On Mon, May 14, 2018 at 03:10:34PM +0200, Paul Gevers wrote: > On Sun, 13 May 2018 14:14:05 -0300 Antonio Terceiro > <terce...@debian.org> wrote: > > not only that. there are 60+ packages that directly build-depend on > > fonts-font-awesome, and these changes probably

Bug#897653: tar 1.30 breaks pristine-tar

data (see below for one example). This is not a problem for newly imported tarballs, but it is a problem for tarballs that were imported with tar < 1.30. On Thu, May 03, 2018 at 05:14:54PM -0300, Antonio Terceiro wrote: > Package: tar > Version: 1.30+dfsg-1 > Severity: grave >

Bug#869191: pristine-tar: pristine-xz failed to reproduce build of ../util-linux_2.30.1.orig.tar.xz

Control: severity -1 important On Sun, May 13, 2018 at 03:00:44PM +0200, Alf Gaida wrote: > Control: severity -1 grave > > can confirm that the patch work fine. sure, thanks for testing. I have applied the patch to the git repository, and it will be available in the next upload. However this

Bug#898501: Broken symlinks

On Sat, 12 May 2018 12:39:50 -0700 Sean Whitton wrote: > Package: fonts-font-awesome > Version: 5.0.10-1 > Severity: grave > Control: affects -1 cider > > Dear maintainer, > > The latest upload introduces some new broken symlinks: > > fonts-font-awesome:

Bug#898524: FTBFS: unsatisfiable dependencies

Source: stylish-haskell Version: 0.8.1.0-1 Severity: serious Justification: fails to build from source Tags: sid buster Install stylish-haskell build dependencies (apt-based resolver) --- Installing build dependencies Reading package

Bug#898216: unattended-upgrades: flaky autopkgtest

On Fri, May 11, 2018 at 04:41:11PM +0200, Bálint Réczey wrote: > Control: tags -1 wontfix > > Hi Paul, > > 2018-05-08 21:48 GMT+02:00 Paul Gevers : > > Source: unattended-upgrades > > Version: 1.0 > > Severity: important > > User: debian...@lists.debian.org > > Usertags: flaky

Bug#897653: tar 1.30 breaks pristine-tar

Package: tar Version: 1.30+dfsg-1 Severity: grave Justification: causes non-serious data loss Hi, After tar 1.30 arrived in unstabled, pristine-tar can no longer reproduce tarballs that it previously could. For example I just hit this with bundler: $ debcheckout -a bundler declared git

Bug#897279: [DRE-maint] Bug#897279: marked as done (libruby2.5: circular dependency hell)

Control: tag 897279 + wontfix On Wed, May 02, 2018 at 10:45:49AM +0200, Christian Hofstaedtler wrote: > Control: reopen 897279 > > > I have just uploaded fixed versions of rake and ruby-test-unit, therefore > > breaking the cycles. > > But now: > > % rake > zsh: /usr/bin/rake: bad interpreter:

Bug#897200: lists.debian.org: debian-ci archives are broken

Package: lists.debian.org Severity: normal hi, the debian-ci mailing was created a few weeks ago, and the archives from the old corrsponding list (autopkgtest-de...@lists.alioth.debian.org) were imported. However, new messagens sent to the new list are not being published in the web archives:

Bug#897187: RM: ruby2.3 -- ROM; deprecated

Package: ftp.debian.org Severity: normal Please remove ruby2.3 from unstable. It has been superseded by ruby2.5, which is the version that we will ship in Buster. There are a few reverse dependencies remaining, and they fall in two categories: - deprecated binaries in non-release architectures

Bug#681326: pristine-tar: Directly accessing .git directory

On Mon, Apr 23, 2018 at 01:49:29PM +0100, Ian Jackson wrote: > FYI, working trees generated by `git worktree' also have a file rather > than a directory as .git. So this bug in pristine-tar will stop it > working properly in those, too. > > Ie the problem is not limited to submodules. I mention

Bug#871835: systemd-setup-machine-id leaving mount behind? (was "Bug#871835: Call for help: review patches for debootstrap")

:47 -0300 Antonio Terceiro <terce...@debian.org> wrote: > I have also looked at these patches, and they look good to me, and also > work great here. Using a local APT proxy, these patches make debootstrap > complete in ~ 2/3 of the time that debootstrap from unstable takes. >

Bug#871835: Call for help: review patches for debootstrap

On Tue, 17 Apr 2018 10:42:43 +0900 Hideki Yamane wrote: > Hi, > > On Wed, 11 Apr 2018 13:06:22 +0200 > Clément Hermann wrote: > > I had a look today. It looks good to me, at first glance I had concerns > > (like using hash keys in boolean context

Bug#881778: closing 881778

On Sat, Apr 21, 2018 at 12:12:39PM +0200, Samuel Thibault wrote: > close 881778 > thanks ?? I don't see ruby2.5 built on hurd-386 ... https://buildd.debian.org/status/package.php?p=ruby2%2e5 signature.asc Description: PGP signature

Bug#894749: #894749 - libgoogle-perftools4: missing libprofiler.so.0 on ppc64el (was "ruby-grpc: FTBFS on ppc64el: cannot open shared object file: No such file or directory")

Control: reassign -1 libgoogle-perftools4 2.6.90-0.1 Control: retitle -1 libgoogle-perftools4: missing libprofiler.so.0 on ppc64el Control: affects -1 + ruby-grpc On Tue, 03 Apr 2018 22:50:29 +0200 Emilio Pozuelo Monfort wrote: > Source: ruby-grpc > Version: 1.3.2+debian-4 >

Bug#895830: RM: apprecommender -- ROM; unmaintained

Package: ftp.debian.org Severity: normal Please remove apprecommender. It was developed during a GSOC term where I was the mentor, but we were never able to drive it into a state that it can be used comfortably by non-techincal users, which is its goal. The GSOC project itself was very fruitful,

Bug#894754: vagrant: Invalid gemspec in rbnacl-libsodium stack level too deep

Control: reassign -1 ruby-rbnacl Control: retitle -1 ruby-rbnacl: doesn't really provide 'rbnacl-libsodium'? On Wed, Apr 04, 2018 at 11:13:57PM +, Nicholas Capo wrote: > I'm sorry. > It seems I did have additional gems installed. > > After removing all gems, and `ruby*` apt packages (and

Bug#892548: dhelp: /usr/sbin/dhelp_parse broken with ruby 2.5

Control: unmerge 892548 Control: reassign 892548 dhelp On Wed, Apr 04, 2018 at 11:30:11PM +0200, gregor herrmann wrote: > On Wed, 04 Apr 2018 00:48:59 +0300, Коля Гурьев wrote: > > > Unfortunately, I can't reproduce this error. However, I've faced the > > other error related to dhelp's cron

Bug#894754: vagrant: Invalid gemspec in rbnacl-libsodium stack level too deep

Control: tag -1 + moreinfo unreproducible On Tue, Apr 03, 2018 at 04:17:51PM -0500, Nicholas Capo wrote: > Package: vagrant > Version: 2.0.2+dfsg-3 > Severity: normal > > Dear Maintainer, > > When running any `vagrant` command the following is error appears and the > command seems to never

Bug#893002: lists.debian.org: new list: debian-ci

Hi, On Thu, Mar 15, 2018 at 09:51:38AM -0300, Antonio Terceiro wrote: > Package: lists.debian.org > Severity: wishlist > > Hi, I would like to request the creation of a new list, called debian-ci > > This list will replace the list > autopkgtest-de...@lists.alioth.debian.

Bug#893002: lists.debian.org: new list: debian-ci

Hi, On Thu, Mar 15, 2018 at 09:51:38AM -0300, Antonio Terceiro wrote: > Package: lists.debian.org > Severity: wishlist > > Hi, I would like to request the creation of a new list, called debian-ci > > This list will replace the list > autopkgtest-de...@lists.alioth.debian.

Bug#881773: ruby2.5: FTBFS on hppa: recursive once test fails

On Sat, Mar 31, 2018 at 04:42:36PM -0400, John David Anglin wrote: > Source: ruby2.5 > Version: 2.5.x > Followup-For: Bug #881773 > > Dear Maintainer, > > In the 2.5.1 build, test #361 fails as follows: > > #361 test_insns.rb:389:in `block in ' F 0.090 > stderr output is not empty >

Bug#889848: marked as done (ruby2.5: Please include upstream patch to fix FTBFS on ia64)

> Date: Wed, 07 Feb 2018 22:09:23 +0100 > From: John Paul Adrian Glaubitz > To: Debian Bug Tracking System > Subject: ruby2.5: Please include upstream patch to fix FTBFS on ia64 > Message-ID: >

Bug#894478: RM: ruby-debugger-ruby-core-source -- ROM; deprecated, useless

Package: ftp.debian.org Severity: normal Please remove ruby-debugger-ruby-core-source from the Debian archive. The package is is fundamentally useless. ruby-rblineprof, the only package that used to depend on it would only need it if running under Ruby 2.0 or ealier, and we are past that point

Bug#894305: package build-depends on legacy ruby2.3-dev

On Thu, 29 Mar 2018 01:11:20 +0800 Matthias Klose wrote: > Package: src:ruby-debugger-ruby-core-source > Version: 1.3.8+ds-1 > Severity: serious > Tags: sid buster patch > > the package build-depends on legacy ruby2.3-dev which is going to be removed. > Is > there are reason

Bug#893765: transition: ruby2.3

On Tue, Mar 27, 2018 at 01:02:53AM +0200, Emilio Pozuelo Monfort wrote: > Control: tags -1 confirmed > > On 22/03/18 03:38, Antonio Terceiro wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags

Bug#893765: transition: ruby2.3

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition ruby2.5 has been made the default and the ruby2.5 transition has been finished succesfully. there is a pending issue with graphviz on armel, but that is beyond what we can do ATM. So I

Bug#893223: ruby: gem2.5 doesn't find anything on rubygems.org

Control: tag -1 + unreproducible moreinfo Hello, On Sat, Mar 17, 2018 at 12:58:22PM +0100, dimmie wrote: > Package: ruby > Version: 1:2.5.0 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the

Bug#886690: debci: Debci invented tests generate false failure reports

On Thu, Mar 15, 2018 at 10:14:06AM +, Scott Kitterman wrote: > > > On March 15, 2018 10:03:03 AM UTC, Paul Gevers wrote: > >Control: tags -1 moreinfo > >Control: reassign -1 autodep8 > >Control: retitle -1 autodep8 should maybe ignore transitional packages > > > >On Mon,

Bug#886690: debci: Debci invented tests generate false failure reports

On Thu, Mar 15, 2018 at 08:29:29AM -0300, Antonio Terceiro wrote: > On Thu, Mar 15, 2018 at 10:14:06AM +, Scott Kitterman wrote: > > > > > > On March 15, 2018 10:03:03 AM UTC, Paul Gevers <elb...@debian.org> wrote: > > >Control: tags -1 moreinf

Bug#893002: lists.debian.org: new list: debian-ci

Package: lists.debian.org Severity: wishlist Hi, I would like to request the creation of a new list, called debian-ci This list will replace the list autopkgtest-de...@lists.alioth.debian.org as the main point of contact for Debian CI-related matters, and discussion among the members of the

Bug#888531: transition: ruby2.5 - binNMU round #5, and next steps

On Sat, Mar 10, 2018 at 04:26:03AM +0100, Andreas Beckmann wrote: > On Fri, 9 Mar 2018 11:53:17 -0300 Antonio Terceiro <terce...@debian.org> > wrote: > > ruby-pgplot: it's in contrib and has a dependency on a non-free package, > > so it can't be built on buildds. I could

Bug#888531: transition: ruby2.5 - binNMU round #5, and next steps

Hi, Please binNMU: obexftp ruby-bcrypt-pbkdf Now we need to discuss what to do wrt the few pending packages. weechat: #892072 [S|+| ] [src:weechat] weechat: build against ruby2.5 uwsgi: #892074 [S | ] [src:uwsgi] uwsgi: FTBFS with ruby2.5 as default graphviz: is missing on armel, because

Bug#892484: ruby-pgplot: missing ruby2.5 build

Source: ruby-pgplot Version: 0.1.9-3 Severity: serious Justification: ruby2.5 will be the default ruby in buster Tags: buster sid Since ruby-pgplot depends on a package from non-free, it won't be rebuilt on the buildds. So ruby-pgplot needs to be manually rebuilt and uploaded by someone who cares

Bug#888531: transition: ruby2.5 - binNMU round #4

Hi, I just uploaded ruby-defaults 1:2.5.0 making the switch in unstable. Binaries should be available in a few hours from now. Please binNMU the following packages: broccoli-ruby dislocker geos graphviz kross-interpreters libprelude marisa nbdkit ngraph-gtk notmuch redland-bindings

Bug#892074: uwsgi: FTBFS with ruby2.5 as default

Source: uwsgi Version: 2.0.15-10.2 Severity: serious Justification: fails to build from source I am about to upload ruby-defaults to unstable, switching the default Ruby to ruby2.5. With that in place, uwsgi fails to build from source like this: [...] CFLAGS="-g -O2 -fdebug-prefix-map=/<>=.

Bug#892072: weechat: build against ruby2.5

Source: weechat Version: 1.9.1-1 Severity: serious Justification: will FTBFS soon Tags: patch Hi, I am about to upload ruby-defaults to unstable, switching the default Ruby to ruby2.5, and ruby2.3 support will be removed right after that. Please consider applying the attached patch, obtained

Bug#888531: transition: ruby2.5 - binNMU round #3

On Sun, Feb 25, 2018 at 02:57:37PM +0100, Emilio Pozuelo Monfort wrote: > On 25/02/18 14:43, Antonio Terceiro wrote: > > Hi, > > > > On Wed, Feb 21, 2018 at 09:33:44AM +0100, Emilio Pozuelo Monfort wrote: > >> On 07/02/18 01:21, Antonio Terceiro wrote: > >>

Bug#891484: stretch-pu: package vagrant/1.9.1+dfsg-1+deb9u1

On Tue, Feb 27, 2018 at 06:41:01PM +, Adam D. Barratt wrote: > Control: tags -1 -moreinfo +confirmed > > On Mon, 2018-02-26 at 18:36 -0300, Antonio Terceiro wrote: > > On Mon, Feb 26, 2018 at 08:42:56PM +, Adam D. Barratt wrote: > > > Control: tags -1 + moreinfo &

Bug#891484: stretch-pu: package vagrant/1.9.1+dfsg-1+deb9u1

On Mon, Feb 26, 2018 at 08:42:56PM +, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Sun, 2018-02-25 at 22:10 -0300, Antonio Terceiro wrote: > > The platform from where vagrant downloads images has been > > discontinued > > and we need to switch the def

Bug#889873: vagrant: unable to download images (moved from atlas.hashicorp.com to app.vagrantup.com)

Control: tag -1 + pending Control: block -1 by 891484 On Sat, Feb 10, 2018 at 01:39:33PM -0500, James McCoy wrote: > On Thu, Feb 08, 2018 at 09:02:03AM +0100, Lucas Nussbaum wrote: > > It seems that Hashicorp decided to migrate from e.g. > > https://atlas.hashicorp.com/alpine/alpine64 > > to > >

Bug#891484: stretch-pu: package vagrant/1.9.1+dfsg-1+deb9u1

atlas.hashicorp.com (Closes: #889873) -- Antonio Terceiro <terce...@debian.org> Sun, 25 Feb 2018 21:54:18 -0300 Diff against package in stretch attached. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug')

Bug#888788: stretch-pu: package lxc/1:2.0.7-2+deb9u2

On Fri, Feb 23, 2018 at 04:58:11PM +, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Mon, 2018-01-29 at 20:40 -0200, Antonio Terceiro wrote: > > iproute has been a transitional package for a while, but the lxc- > > debian > > template was refering

Bug#890046: ruby-json: disabling jruby support

Control: retitle -1 jruby support broken on several architectures Control: severity -1 normal Hi, ruby-json currently FTBFS, and is blocking the Ruby transition, as reported in bug #890046 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890046) All failures are related to the jruby support,

Bug#891449: jruby: system() does not work on arm64

Package: jruby Version: 9.1.13.0-1 Severity: grave Justification: renders package unusable When debugging #890046 on ruby-json, I realized that I cannot execute any program with system() under jruby on arm64: 8<8<8<-

Bug#890046: no build artifacts included in ruby-json, built for jruby

On Sat, 10 Feb 2018 15:04:25 +0100 Matthias Klose wrote: > there are no build artifacts included in ruby-json, built for jruby. Except > for > an additional README. yes, there are: $ dpkg -L ruby-json | grep jar /usr/lib/ruby/vendor_ruby/json/ext/generator.jar

Bug#888531: transition: ruby2.5 - binNMU round #3

Hi, On Wed, Feb 21, 2018 at 09:33:44AM +0100, Emilio Pozuelo Monfort wrote: > On 07/02/18 01:21, Antonio Terceiro wrote: > > Please binNMU: > > > > libguestfs > > mapserver > > passenger > > nbdkit > > Any update here? Almost all of the the m

Bug#888788: Bug#891221: stretch's lxc fails to create sid container: iproute not found

Control: tags 891221 + confirmed Control: block 891221 by 888788 On Fri, Feb 23, 2018 at 02:12:37PM +, Santiago wrote: > Package: lxc > Version: 1:2.0.7-2+deb9u1 > Severity: important > > Stretch's lxc fails to create a -t debian -- -r sid container, because > it doesn't find the iproute

Bug#888531: transition: ruby2.5 - binNMU round #3

Please binNMU: libguestfs mapserver passenger nbdkit signature.asc Description: PGP signature

Bug#889663: FTBFS: Unable to load the SpatiaLite library extension

Source: djangorestframework-gis Version: 0.12-1 Severity: serious Justification: fails to build from source dh_auto_test -- --system=custom --test-args="{interpreter} ./runtests.py" I: pybuild base:184: python2.7 ./runtests.py Creating test database for alias 'default'... Traceback (most recent

Bug#889174: Please honor http_proxy in autopkgtests

Control: tag -1 + pending Hi Steve, On Fri, Feb 02, 2018 at 03:56:52PM -0800, Steve Langasek wrote: > URL: ["https://vagrantcloud.com/debian/artful64;] > Error: The requested URL returned error: 404 Not Found > + cleanup > + vagrant halt > ==> default: Domain is not created. Please run `vagrant

Bug#888531: transition: ruby2.5 - binNMU round #2

Hi, Please binNMU the following packages: broccoli-ruby hyperestraier libsemanage notmuch ruby-bson ruby-fftw3 ruby-github-markdown ruby-gnome2 ruby-grib ruby-hdfeos5 ruby-hpricot ruby-http-parser.rb ruby-lapack ruby-mpi ruby-msgpack ruby-multibitnums ruby-netcdf ruby-nokogumbo ruby-password

Bug#888531: transition: ruby2.5 - please update tracker

Hi, please update the tracker as follows: Affected: (.depends ~ /ruby2.3 | .depends ~ /ruby2.5/) & !.source ~ /^(ruby2.3|ruby2.5|ruby-defaults)$/) This will exclude the interpreter packages themselves from the list of affected packages. signature.asc Description: PGP signature

Bug#888531: 888531 - transition: ruby2.5 - binNMU round #1

On Thu, Feb 01, 2018 at 10:57:09AM -0200, Antonio Terceiro wrote: > ruby-defaults err, no need to binNMU ruby-defaults signature.asc Description: PGP signature

Bug#888531: 888531 - transition: ruby2.5 - binNMU round #1

Hi, As part of the ruby2.5 transition, please binNMU the following packages: hivex libselinux raspell remctl rrdtool ruby-allocations ruby-atomic ruby-augeas ruby-bcrypt ruby-bert ruby-byebug ruby-cairo ruby-charlock-holmes ruby-concurrent-ext ruby-curb ruby-curses ruby-dataobjects-mysql

Bug#889031: override: ruby-dev:ruby/optional, ruby-all-dev:ruby/optional

Package: ftp.debian.org Severity: normal Hi, please move ruby-dev and ruby-all-dev to section `ruby`. The change in the package control file was just uploaded to unstable. TIA signature.asc Description: PGP signature

Bug#889026: ruby-shadow: FTBFS with ruby2.5: too many arguments to function 'rb_struct_ptr' / subscripted value is neither array nor pointer nor vector

Source: ruby-shadow Severity: serious Justification: Fails to build from source User: debian-r...@lists.debian.org Usertags: ruby2.5 I am filing this at severity serious as I am about to enable building for ruby2.5 in unstable.

Bug#889025: ruby-odbc: FTBFS with ruby2.5: invalid operands to binary / (have 'char *' and 'char *')

Source: ruby-odbc Severity: serious Justification: Fails to build from source User: debian-r...@lists.debian.org Usertags: ruby2.5 I am filing this at severity serious as I am about to enable building for ruby2.5 in unstable.

Bug#889023: ruby-gsl: FTBFS with ruby2.5: 'rb_cFixnum' undeclared

Source: ruby-gsl Severity: serious Justification: Fails to build from source User: debian-r...@lists.debian.org Usertags: ruby2.5 I am filing this at severity serious as I am about to enable building for ruby2.5 in unstable. [...] gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0

Bug#889021: ruby-ffi-yajl: FTBFS with ruby2.5: 'rb_cFixnum' undeclared

Source: ruby-ffi-yajl Severity: serious Justification: Fails to build from source User: debian-r...@lists.debian.org Usertags: ruby2.5 I am filing this at severity serious as I am about to enable building for ruby2.5 in unstable.

Bug#888531: transition: ruby2.5

On Tue, Jan 30, 2018 at 09:33:11AM -0200, Antonio Terceiro wrote: > On Sat, Jan 27, 2018 at 12:37:46AM +0100, Emilio Pozuelo Monfort wrote: > > Control: forwarded -1 > > https://release.debian.org/transitions/html/ruby2.5.html > > > > On 26/01/18 20:36, Antonio Te

Bug#888531: transition: ruby2.5

On Sat, Jan 27, 2018 at 12:37:46AM +0100, Emilio Pozuelo Monfort wrote: > Control: forwarded -1 https://release.debian.org/transitions/html/ruby2.5.html > > On 26/01/18 20:36, Antonio Terceiro wrote: > > Package: release.debian.org > > Severity: normal >

Bug#888788: stretch-pu: package lxc/1:2.0.7-2+deb9u2

the creation of testing and unstable containers after +the iproute binary package was dropped. + + -- Antonio Terceiro <terce...@debian.org> Mon, 29 Jan 2018 20:23:36 -0200 + lxc (1:2.0.7-2+deb9u1) stretch; urgency=medium * 0003-lxc-debian-don-t-hardcode-valid-releases.patch: don'

Bug#888531: transition: ruby2.5

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi, I would like to start the transition to ruby2.5 in unstable. General information about Ruby transitions can be found in: https://wiki.debian.org/Teams/Ruby/InterpreterTransitions

Bug#865588: [Python-modules-team] Bug#865588: Bug#865588: djangorestframework FTBFS with Django 1.11: ERROR collecting tests/test_fields.py

On Wed, Jan 10, 2018 at 05:38:02PM +1100, Brian May wrote: > Thijs Kinkhorst writes: > > > We're half a year on, so has this now changed? (I tried to check out the > > git repo and build it, but that had several problems so I might be missing > > one or two pieces to quickly

Bug#832022: This will be fixed in ruby2.5

Control: reassign -1 ruby2.5 Control: retitle -1 ruby2.5: should not depend on an existing ruby for bootstrapping It is too late already to even try fixing this in ruby2.3, so I am reassigning to ruby2.5 and fixing it there. signature.asc Description: PGP signature

<    4   5   6   7   8   9   10   11   12   13   >