Re: Is an autogenerated configure shell script non-editable source

[Andreas Tille]

Am Fri, Dec 09, 2022 at 11:58:56AM -0800 schrieb Russ Allbery:
> The real problem in this case is less about the DFSG and more about the
> practical problems of maintaining Debian as a software distribution: if we
> can't regenerate configure using software in Debian, there are a lot of
> porting tasks and some bug-fixing tasks that we can't do, and that's a
> problem for us.  But I'm dubious that it's a *software freedom* problem;
> it's more of a *software maintenance* problem, and thus the bug severity
> should be based on how much of a problem that is in practice.

The situation of hmmer2 is that upstream went to hmmer3 which is despite
its same name something different.  The Debian Med team keeps on
maintaining that old code since scientists need this to have comparable
results with former research.  I guess its simple enough to even craft a
new configure.ac (or backport the one for hmmer3) if needed and the fact
that Helmit stumbled upon it to enhance pkg-config compatibility is a
good reason for a bug report with severity somewhere between wishlist
and important.  We try to fix any bug (no matter what severity) and in
the current Debian Med Advent bug squashing party we try to approach
this.

However, since we can not guarantee that the bug is solved quickly a
serious bug might have the consequence that the package might not be
shipped with bookworm which is definitely not in the interest of our
users.

So far for the actual case (bug report in CC).

For the general case I somehow understand the consensus here on the list
that a missing configure.ac can be considered a bug but the severity
serious is not really rectified.  If I understood this correctly I would
reset the severity to important at the beginning of next week.

Kind regards
   Andreas.

-- 
http://fam-tille.de

Re: looking for debian friendly web app technology

[Jonas Smedegaard]

Quoting Paul Wise (2022-12-10 03:51:20)
> On Fri, 2022-12-09 at 13:12 +0100, Andreas Josef Heil wrote:
> 
> > I'd like to develop a free software web app and I wanne be the debian
> > maintainer for it. It should be fully integrated to debian und freedombox.
> > 
> > What web technology should I use?
> 
> Personally I would suggest to focus on static site generators,
> that only produce web pages that utilise progressive enhancement.
> This sort of web site is more performant for users, more flexible
> for hosting and easier to archive at the end of life of the website.
> 
> https://en.wikipedia.org/wiki/Static_site_generator
> http://en.wikipedia.org/wiki/Progressive_enhancement
> 
> If possible I would consider making it a Linux desktop app instead.

I fully agree with Pabs.

On top of that, I would suggest to consider not only more sustainable
_content_ production and consumption through the above methods, but also
more sustainable _application_ production and consumption: Avoid
reinventing wheels by breaking the task into components that process
content via the Micropub standard and other Indieweb mechanisms, and
then reuse existing components and write only components missing.

E.g. if you like to code in Perl, then write a Micropub plugin for
existing static site generator Ikiwiki already part of FreedomBox, so
that everyone already using Ikiwiki (not only FreedomBox users) can edit
their content natively e.g. using exisitng Android app Indigenous.

Or if you like to code in PHP, then write a Micropub plugin for
Mediawiki, (less sustainable but) also already part of FreedomBox.

Or maybe skip coding from scratch altogether and instead package
existing plugin and theme for Wordpress, (also less sustainable but)
already already part of FreedomBox.

Or if you like to code in Python, then write a Micropub plugin for
Radicale, translating between ical data and Micropub Event data.
Radicale is already in FreedomBox.

Or maybe write a Micropub media endpoint that hooks into Matrix,
enabling Micropub-based editors like Indigenous to reuse images and
videos posted in Matrix rooms.  Matrix server is already in FreedomBox.


https://www.w3.org/TR/micropub/
https://wordpress.org/plugins/micropub/
https://wordpress.org/plugins/indieweb/
https://f-droid.org/en/packages/com.indieweb.indigenous/
http://microformats.org/wiki/h-event
https://www.w3.org/TR/micropub/#media-endpoint


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Re: Is an autogenerated configure shell script non-editable source (Was: Bug#1025739: hmmer2: missing source for configure)

[Andreas Metzler]

On 2022-12-09 Andreas Tille  wrote:
[...]
> Thanks to Alexander Sulfrian who pointed out the Git repository
> featuring old tags that were obviously taken over from SVN I was proven
> wrong with the statement that there is no configure.ac any more.

> Unfortunately this is no simple drop-in with modern autoconf tools
> and my weak attempt in Git to use this failed.[1]
[...]

Hello,

I have given this a a little bit of time. This seems to work:

1. Copy configure.ac from upstream's 2.3.2h2 branch.
2. Add 'export AUTOHEADER = true' to debian/rules.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Re: Is an autogenerated configure shell script non-editable source

[Russ Allbery]

Andreas Tille  writes:

> For the general case I somehow understand the consensus here on the list
> that a missing configure.ac can be considered a bug but the severity
> serious is not really rectified.  If I understood this correctly I would
> reset the severity to important at the beginning of next week.

I think that seems fine baesd on my reading of the thread, although since
we have now found the configure.ac, I would also stuff that in the Debian
package somewhere so that all the pieces are available to someone who has
the Debian source package.

-- 
Russ Allbery (r...@debian.org)  

Bug#1025862: ITP: templated-dictionary -- Dictionary with Jinja2 expansion

[Juri Grabowski]

Package: wnpp
Severity: wishlist
Owner: Juri Grabowski 
X-Debbugs-Cc: debian-devel@lists.debian.org, deb...@jugra.de

* Package name: templated-dictionary
  Version : 1.1
  Upstream Author : Miroslav Suchý 
* URL : https://pypi.org/project/templated-dictionary/
* License : GPLv2+
  Programming Lang: Python
  Description : Dictionary with Jinja2 expansion

  This module provides dictionary where every item is evaluated as a
  Jinja2 expression.

  needed by mock/3.5 and I need a sponsor for this package. See current
  packaging in
  https://salsa.debian.org/python-team/packages/templated-dictionary

Re: Is an autogenerated configure shell script non-editable source

[Paul Wise]

On Sat, 2022-12-10 at 10:28 +0100, Andreas Tille wrote:

> So far for the actual case (bug report in CC).
> 
> For the general case I somehow understand the consensus here on the list
> that a missing configure.ac can be considered a bug but the severity
> serious is not really rectified.  If I understood this correctly I would
> reset the severity to important at the beginning of next week.

Personally I feel that severity serious is the correct one,
but it sounds like the fix for the bug is quite simple:

https://lists.debian.org/msgid-search/y5rir8qidvj4r...@argenau.bebt.de


-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#1025739: Info received (Is an autogenerated configure shell script non-editable source)

[Debian Bug Tracking System]

Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Debian Med Packaging Team 

If you wish to submit further information on this problem, please
send it to 1025...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

-- 
1025739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems