On Sun, Apr 21, 11:51, Andreas Metzler wrote
> On 2024-04-08 Andre Noll wrote:
> > On Sun, Apr 07, 22:02, Peter Michael Green wrote:
>
> > > After being rebuilt for the time64 transition, tfortune
> > > depends on both liblopsub1 and liblopsub1t64. As a
&g
[Cc Steve]
On Sun, Apr 07, 22:02, Peter Michael Green wrote:
> After being rebuilt for the time64 transition, tfortune
> depends on both liblopsub1 and liblopsub1t64. As a
> result it is uninstallable on architectures that are undergoing
> the time64 transition (armel, armhf and some
On Sun, Mar 03, 11:47, Steve Langasek wrote
> > Below it what I've just applied. The patch looks different to what
> > you've sent, but the resulting tree is identical. Please let me know
> > if you're OK with the commit message.
>
> No objections.
Merged and pushed out to the public repo.
a5c8, replacing it with
the version that has been uploaded to unstable.
It adds a versioned build-dependency on dpkg-dev to guard against
accidental backports with a wrong ABI.
Signed-off-by: Andre Noll
diff --git a/debian/changelog b/debian/changelog
index 44bbaeb.
On Thu, Feb 01, 21:13, Steve Langasek wrote:
> > * The tfortune package depends on liblopsub and currently has
>
> > Depends: ${shlibs:Depends}, liblopsub1, ${misc:Depends}
>
> > in its own debian/control file. When would be the best time to replace
> > liblopsub1 by liblopsub1t64?
>
> You
https://bugs.debian.org/1037136), it is important that libraries
affected by this ABI change all be uploaded close together in time.
Therefore I have prepared a 0-day NMU for liblopsub which will
initially be uploaded to experimental if possible, then to unstable
after packages have
On Thu, Jun 29, 19:45, Andre Noll wrote
> > It also needs someone to upload to Debian. Looks like Adam Borowski
> > has sponsored in the past, but if you need someone
> > else to sponsor the upload, I could too.
>
> Yes, Adam uploaded all previous versions so far. But of
On Thu, Jun 29, 08:27, Vagrant Cascadian wrote
> >> Given that this change was accepted in 2019, would you consider
> >> uploading a version with the fixes applied to Debian, either by making a
> >> new upstream version, or applying the patches to an older version?
> >
> > Will do. FWIW: There are
On Tue, Jun 27, 14:55, Vagrant Cascadian wrote
> > This issue was addressed already four years ago when Chris Lamb (CC)
> > submitted an analogous patch, see below. His patch has been part of the
> > master branch since then, although no new version has been released.
> >
> > I therefore assume
On Tue, Jun 27, 14:46, Vagrant Cascadian wrote
> >> The attached patch fixes this by passing the -ffile-prefix-map argument
> >> to the compiler in the upstream Makefile.
> >>
> >> According to my local tests, with this patch and the recently submitted
> >> timestamp patches applied, liblopsub
this modified patch?
Thanks
Andre
---
commit 0a3588cdf56966a58decbbf62793dcc90217651c
Author: Vagrant Cascadian
Date: Tue Jun 27 23:04:56 2023 +0200
Makefile: Add -ffile-prefix-map to CC to avoid embedding build paths.
Signed-off-by: Andre Noll
diff --git a/Makefile b/Makefile
index 548c96f.
On Tue, Jun 27, 12:57, Vagrant Cascadian wrote:
> The attached two patches (one patching the upstream Makefile, the other
> patching debian/rules) fix this by passing -n to the gzip calls used to
> compress changelog.Debian and the various manpages.
>
> According to my local tests, with these
On Wed, Mar 01, 18:23, Helmut Grohne wrote
> On Wed, Mar 01, 2023 at 05:27:04PM +0100, Andre Noll wrote:
> > If you are OK with the commit message shown below, I'll merge the
> > commit into the master branch and push it out to the public repo.
>
> Sure.
The public
On Wed, Mar 01, 01:12, Helmut Grohne wrote
> On Tue, Feb 28, 2023 at 11:13:24PM +0100, Andre Noll wrote:
> > > The immediate failure is failing to find the lopsub library since it
> > > configures for the build architecture. This happens as no --build nor
> > > --ho
On Tue, Feb 28, 06:04, Helmut Grohne wrote
> Source: tfortune
> Version: 1.0.1-1
> Tags: patch
> User: debian-cr...@lists.debian.org
> Usertags: ftcbfs
>
> tfortune fails to cross build from source.
First of all, thanks for pointing this out and for providing a
patch. Most likely, nobody has
On Thu, Sep 10, 08:11, Chris Lamb wrote
> Chris Lamb wrote:
>
> > Would you consider applying this patch and uploading?
>
> Friendly ping on this? Seems like there hasn't been any update on this bug in
> 281 days now (!). As you mention, you may have already fixed it.
Yes, this was was fixed by
On Fri, Nov 29, 09:12, Chris Lamb wrote
> Whilst working on the Reproducible Builds effort [0] we noticed that
> liblopsub could not be built reproducibly.
>
> This is because it calls "gzip" manually without the -n flag. This should
> have been reported by lintian via the
On Sun, Jul 14, 14:56, Adam Borowski wrote
> On Sun, Jul 14, 2019 at 12:28:33PM +0200, Andre Noll wrote:
> > On Sat, Jul 13, 22:48, Adam Borowski wrote
> > > I would gladly upload your updates, but I don't know what upstream tarball
> > > to use. There's no watch fi
On Sat, Jul 13, 22:48, Adam Borowski wrote
> On Sat, Jul 13, 2019 at 03:09:49PM +0200, Andre Noll wrote:
> > I've merged the commit and bumped the Debian version number. Adam:
> > would you please upload lopsub-1.0.3-2? This version corresponds to
> > the current master bran
On Fri, Jul 12, 10:30, Chris Lamb wrote
> > > Whilst working on the Reproducible Builds effort [0], we noticed
> > > that liblopsub generates output that is not reproducible.
> […]
> > Good catch. I've applied your patch and made some minor edits to
> > improve code readability and to fix the typo
ilds.org/specs/source-date-epoch/
Signed-off-by: Andre Noll
diff --git a/lsg.c b/lsg.c
index 54b7816..83a72da 100644
--- a/lsg.c
+++ b/lsg.c
@@ -610,7 +610,7 @@ static char *get_output_path(const char *suffix, const char
*arg,
static void gen_man(struct lls_parse_result *lpr
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 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 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
> > >
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.
Hi Chris,
On Wed, Jun 05, 15:04, Chris Lamb wrote
> > Indeed: FreeBSD-12's date(1) has
> >
> > -r seconds
> > Print the date and time represented by seconds, where seconds is
> > the number of seconds since the Epoch (00:00:00 UTC, January 1,
> > 1970; see
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
On Tue, Jun 04, 18:16, Chris Lamb wrote
> Andre Noll wrote:
>
> > Then I don't grok the purpose of the
> >
> > LC_ALL=C date -u -r '$(SOURCE_DATE_EPOCH)' '$(DATE_FMT)'
> >
> > command. After all, at least GNU date(1) expects a filename as the
> >
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
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
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:
>
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 packagi
On Fri, May 31, 17:05, Chris Lamb wrote
> > Also DATE_FMT should be a singly expanded make variable.
>
> (Singly, as in ":=" vs "=" ?)
Yes.
> > Care to provide a commit message which explains why we try to
> > pass $(SOURCE_DATE_EPOCH) as an argument to both -d and -r, who
> > sets
On Fri, May 31, 09:44, Chris Lamb wrote
> Whilst working on the Reproducible Builds effort [0], we noticed
> that liblopsub could not be built reproducibly.
No general objection from my side. However,
> -DATE := $(shell date '+%B %Y')
> +DATE_FMT = '+%B %Y'
> +ifdef SOURCE_DATE_EPOCH
> +
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/
On Mon, Apr 22, 17:30, Andre Noll wrote
> > But in general, the package already seems to be in a releasable state.
> > Could you please change "UNRELEASED" to "unstable" so it can be uploaded?
>
> Done. Please have a final look. If everything is fine, I
On Sun, Apr 21, 22:25, Adam Borowski wrote
> On Sun, Apr 21, 2019 at 05:11:05PM +0200, Andre Noll wrote:
> > That's just because I misread section 8.1 of the Debian Policy Manual.
> > I've renamed the -dev package to liblopsub-dev.
>
> Not sure if you'd want the _source_ pac
On Sun, Apr 14, 15:41, Adam Borowski wrote
> On Sat, Apr 06, 2019 at 09:52:53PM +0200, Andre Noll wrote:
> > > > I see a static library installed by the package. Those shouldn't
> > > > generally
> > > > be used unless you're doing something special -
On Sat, Apr 06, 21:52, Andre Noll wrote
> On Mon, Apr 01, 00:57, Andre Noll wrote
>
> > > I see a static library installed by the package. Those shouldn't
> > > generally
> > > be used unless you're doing something special -- static linking makes
> >
On Mon, Apr 01, 00:57, Andre Noll wrote
> > I see a static library installed by the package. Those shouldn't generally
> > be used unless you're doing something special -- static linking makes
> > security and bugfix updates extremely tedious. Libraries should also be
>
On Sat, Mar 30, 23:58, Adam Borowski wrote
> On Thu, Mar 28, 2019 at 11:41:45AM +0100, Andre Noll wrote:
> > * Package name: lopsub
> >Version : 1.0.2
>
> Such a version means a native package; only software written specifically
> for Debian which makes no
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "lopsub":
* Package name: lopsub
Version : 1.0.2
Upstream Author : Andre Noll
* URL : http://people.tuebingen.mpg.de/maan/lopsub/
* License
42 matches
Mail list logo
