On Wed, Jun 19, 14:01, Adam Borowski wrote
> > Both issues have been fixed in v2 of the t/tfortunes branch which
> > I've just pushed out. This branch also contains two new commits
> > which fix a gcc warning and a harmless memory leak.
>
> Uploaded, with some changes.
Thanks a bunch for fixing
On Wed, Jun 19, 2019 at 11:45:08AM +0200, Andre Noll wrote:
> On Tue, Jun 18, 17:48, Adam Borowski wrote
> > Looks good.
> >
> > However, version 1.0.0-1 is already in NEW, thus unless it's REJECTed, the
> > version number cannot be reused.
> >
> > There's also a typo: "considerd".
>
> Thanks
On Tue, Jun 18, 17:48, Adam Borowski wrote
> > Here we go. The public repo now contains the t/tfortunes branch with
> > the following four commits on top of master:
>
> Looks good.
>
> However, version 1.0.0-1 is already in NEW, thus unless it's REJECTed, the
> version number cannot be reused.
>
On Tue, Jun 18, 2019 at 02:01:08PM +0200, Andre Noll wrote:
> On Fri, Jun 07, 10:39, Andre Noll wrote
>
> > > What about tfortune-data that ships as many good epigrams as you have,
> > > that's Recommended: by tfortune?
> >
> > Sounds good. I've merged and pushed out the t/debian branch so
> >
On Fri, Jun 07, 10:39, Andre Noll wrote
> > > OK. Do you think it makes sense to provide another package which
> > > installs a few tagged epigrams in, say, /usr/share/games/tfortunes
> > > and make tfortune fall back to this directory if ~/.tfortune does
> > > not exist?
> >
> > That'd be nice.
On Thu, Jun 06, 12:56, Adam Borowski wrote
> > > The RFS and ITP are unrelated.
> >
> > IDGI. For an RFS email one needs to provide the source package with
> > a debian/ directory, correct? If so, the debian/changelog file must
> > contain a line of the form
> >
> > * Initial Release.
On Thu, Jun 06, 2019 at 12:42:48PM +0200, Andre Noll wrote:
> On Wed, Jun 05, 15:49, Adam Borowski wrote
> > On Wed, Jun 05, 2019 at 02:31:09PM +0200, Andre Noll wrote:
> > > That's the old hen and egg problem: One needs to provide a bug number
> > > in debian/changelog for the initial RFS, i.e.
On Wed, Jun 05, 01:40, Adam Borowski wrote
> On Tue, Jun 04, 2019 at 05:06:00PM +0200, Andre Noll wrote:
> > v3 is pushed out now and contains
> > a simple debian/rules file which fully relies on dh. Besides
> > dh_auto_configure I also had to override dh_autoreconf for reasons
> > explained in
On Wed, Jun 05, 10:41, wf...@niif.hu wrote
> > I also had to override dh_autoreconf for reasons explained in the
> > commit message.
>
> It isn't a packaging issue, I just wonder: why do you wrap configure?
> The usual approach to making it available is distributing it (and not
> requiring
Andre Noll writes:
> I also had to override dh_autoreconf for reasons explained in the
> commit message.
It isn't a packaging issue, I just wonder: why do you wrap configure?
The usual approach to making it available is distributing it (and not
requiring Autoconf to build the software from the
On Tue, Jun 04, 2019 at 05:06:00PM +0200, Andre Noll wrote:
> v3 is pushed out now and contains
> a simple debian/rules file which fully relies on dh. Besides
> dh_auto_configure I also had to override dh_autoreconf for reasons
> explained in the commit message.
The package looks almost good now.
On Sun, Jun 02, 22:57, Adam Borowski wrote
> On Sat, Jun 01, 2019 at 11:17:53PM +0200, Andre Noll wrote:
> > Adam, do you want me to provide v3 with debian/rules changed to
> > something like the above?
>
> v2 still suffers from the non-standard perms on usr/ and so on, thus I guess
> it'd be
On Sat, Jun 01, 2019 at 11:17:53PM +0200, Andre Noll wrote:
> Adam, do you want me to provide v3 with debian/rules changed to
> something like the above?
v2 still suffers from the non-standard perms on usr/ and so on, thus I guess
it'd be simpler to move to the dh workflow rather than to fix what
On Sat, Jun 01, 16:46, Alexis Murzeau wrote
> I think Adam meant to not implement low level makefile targets yourself,
> but use dh like this:
> ```
> #!/usr/bin/make -f
>
> export DEB_BUILD_MAINT_OPTIONS = hardening=+all
> %:
> dh $@
>
> override_dh_auto_configure:
>
Hi,
Le 01/06/2019 à 13:36, Andre Noll a écrit :> On Fri, May 31, 17:32, Adam
Borowski wrote
>> On Fri, May 24, 2019 at 08:57:49AM +0200, Andre Noll wrote:
>>> * Package name: tfortune
>>>Version : 1.0.0
>>
>>> git clone git://git.tuebingen.mpg.de/tfortune/
>>
>> Hi!
>> I'm
On Fri, May 31, 17:32, Adam Borowski wrote
> On Fri, May 24, 2019 at 08:57:49AM +0200, Andre Noll wrote:
> > * Package name: tfortune
> >Version : 1.0.0
>
> > git clone git://git.tuebingen.mpg.de/tfortune/
>
> Hi!
> I'm afraid your packaging unnecessarily reinvents a good
On Fri, May 24, 2019 at 08:57:49AM +0200, Andre Noll wrote:
> * Package name: tfortune
>Version : 1.0.0
> git clone git://git.tuebingen.mpg.de/tfortune/
Hi!
I'm afraid your packaging unnecessarily reinvents a good part of usual
tools, and does this wrong. For example:
*
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "tfortune":
* Package name: tfortune
Version : 1.0.0
Upstream Author : Andre Noll
* URL : http://people.tuebingen.mpg.de/maan/tfortune/
* License :
18 matches
Mail list logo
