Bug#856827: marked as done (RFS: xfce4-equake-plugin/1.3.8.1-2 [RC])

2017-03-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Mar 2017 19:39:28 -0700 with message-id <20170319023928.g225qfqwao22u...@iris.silentflame.com> and subject line Re: Bug#856827: RFS: xfce4-equake-plugin/1.3.8.1-2 [RC] has caused the Debian Bug report #856827, regarding RFS: xfce4-equake-plugin/1.3.8.1-2 [RC] to be marked

Bug#858155: RFS: stenc/1.0.7-1 [ITP]

2017-03-18 Thread Denys Berkovskyy
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "stenc" * Package name: stenc Version : 1.0.7-1 Upstream Author : John Coleman * URL : https://sourceforge.net/projects/stenc/ * License : GPLv2 Section

Bug#856827: RFS: xfce4-equake-plugin/1.3.8.1-2 [RC]

2017-03-18 Thread Jeroen van Aart
> Dear Jeroen, > > Please be sure to CC the RFS bug! Forgot the "reply all". I did send it to the RFS bug separately. > On Wed, Mar 15, 2017 at 10:49:27PM -0700, Jeroen van Aart wrote: > You still haven't noted that you updated the copyright years. And you > haven't documented updating the Home

Re: What option should I now use to do source only builds

2017-03-18 Thread Sean Whitton
Hello Andreas, On Fri, Mar 17, 2017 at 11:32:25PM +0100, Andreas Tille wrote: > I have understood from NEWS.debian of pbuilder 0.228 that the '-S' > option does not work any more. Unfortunately I did not understood what > I need to do now to do a source only build (nor what the problem of this >

Re: What option should I now use to do source only builds

2017-03-18 Thread Mattia Rizzolo
On Sat, Mar 18, 2017 at 03:45:30PM +0100, Johannes Schauer wrote: > how would the unpacked source directory become unclean if I'm using pbuilder > or > sbuild to build my packages? The developer might drop in debian/ (or in ./ in the case of a native package) any kind of file and that would be pa

Re: What option should I now use to do source only builds

2017-03-18 Thread Johannes Schauer
Quoting Mattia Rizzolo (2017-03-18 08:53:21) > On Sat, Mar 18, 2017 at 08:22:36AM +0100, Johannes Schauer wrote: > > So just as with sbuild I don't see why anybody would want to *only* build > > the > > source package inside a chroot. Since the source package is the *input* to > > the > > whole o

Re: What option should I now use to do source only builds

2017-03-18 Thread Mattia Rizzolo
On Sat, Mar 18, 2017 at 08:22:36AM +0100, Johannes Schauer wrote: > So just as with sbuild I don't see why anybody would want to *only* build the > source package inside a chroot. Since the source package is the *input* to the > whole operation, you would just get back what you already put in. The

Re: What option should I now use to do source only builds

2017-03-18 Thread Johannes Schauer
Hi, Quoting Andrey Rahmatullin (2017-03-18 07:58:56) > On Sat, Mar 18, 2017 at 07:25:32AM +0100, Andreas Tille wrote: > > > James Clarke wrote in https://bugs.debian.org/853886#10: > > > > > > "For source-only builds, I don't understand why you would want to > > > perform the build in a chroot. >

Bug#858089: RFS: ubertooth/2017.03.R2-1~exp1 and libbtbb/2017.03.R2-1~exp1

2017-03-18 Thread Ruben Undheim
Package: sponsorship-requests Severity: wishlist Dear mentors, These two packages both have backwards-incompatible ABI changes. This leads to 2 new binary packages: libbtbb1 and libubertooth1 As a DM I cannot upload new binary packages. Can anyone help me out? You will find the packages here:

Re: What option should I now use to do source only builds

2017-03-18 Thread Andrey Rahmatullin
On Sat, Mar 18, 2017 at 07:25:32AM +0100, Andreas Tille wrote: > > James Clarke wrote in https://bugs.debian.org/853886#10: > > > > "For source-only builds, I don't understand why you would want to > > perform the build in a chroot. > > Since Build-Depends are requested on my local machine anyway