Bug#1003769: RFS: byacc/1.0-2 [ITA] -- public domain Berkeley LALR Yacc parser generator

2022-01-15 Thread Andreas Metzler
On 2022-01-15 Thomas Dickey  wrote:
[...]
> I am looking for a sponsor for my package "byacc":

>  * Package name: byacc
>Version : 1:2.0.20220114-1
>Upstream Author :  (Thomas E. Dickey)
>  * URL : https://invisible-island.net/byacc/
>  * License : GPL-3, public-domain, other-BSD
>  * Vcs : https://salsa.debian.org/debian/byacc
>Section : devel

> It builds those binary packages:

>   byacc - public domain Berkeley LALR Yacc parser generator
>   byacc2 - public domain Berkeley LALR Yacc parser generator, with 
> back-tracking
[...]

Hello Thomas,

I would like to question the introduction of another binary package:
* "byacc2" seems to be a (newly introduced) Debiansm. Googling for
  "byacc2" only finds links related to this RFS.
* The packages are tiny (about 100k) and have no conflicting files.
  /usr/bin/byacc2 and /usr/bin/byacc could be shipped in on binary
  package.
* Is the double compilation/binary necessary? - Is /usr/bin/byacc2
  incompatible with /usr/bin/byacc2? A quick glance at the yacc.1 seems
  to suggests that /usr/bin/byacc2 is a backward compatible extension of
  /usr/bin/byacc the only difference being that it additionally supports
  | -B   create a backtracking parser

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'



Bug#1003770: RFS: luit/2.0.20220111-1 [ITP] -- locale and ISO 2022 support for Unicode terminals

2022-01-15 Thread Thomas Dickey
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "luit":

 * Package name: luit
   Version : 2.0.20220111-1
   Upstream Author : Thomas Dickey 
 * URL : http://invisible-island.net/luit/
 * License : GPL-3, X11
 * Vcs : https://salsa.debian.org/dickey/luit
   Section : utils

It builds those binary packages:

  luit2 - locale and ISO 2022 support for Unicode terminals

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/luit/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/l/luit/luit_2.0.20220111-1.dsc

Changes for the initial release:

 luit (2.0.20220111-1) unstable; urgency=low
 .
   * Initial package release (Closes: #1003130)

Regards,

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature


Bug#1003769: RFS: byacc/1.0-2 [ITA] -- public domain Berkeley LALR Yacc parser generator

2022-01-15 Thread Thomas Dickey
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "byacc":

 * Package name: byacc
   Version : 1:2.0.20220114-1
   Upstream Author :  (Thomas E. Dickey)
 * URL : https://invisible-island.net/byacc/
 * License : GPL-3, public-domain, other-BSD
 * Vcs : https://salsa.debian.org/debian/byacc
   Section : devel

It builds those binary packages:

  byacc - public domain Berkeley LALR Yacc parser generator
  byacc2 - public domain Berkeley LALR Yacc parser generator, with back-tracking

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/byacc/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/b/byacc/byacc_2.0.20220114-1.dsc

Changes since the last upload:

 byacc (1:2.0.20220114-1) unstable; urgency=medium
 .
   * work around git-buildpackage's absence of configurability regarding uscan.
   * fix lintian issues reported in update.

Regards,
-- 
  Thomas Dickey

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature


Bug#1003768: RFS: guerillabackup/0.1.1-1 [ITP] -- resilient, distributed backup and archiving solution

2022-01-15 Thread halfdog
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "guerillabackup":

 * Package name: guerillabackup
   Version : 0.1.1-1
   Upstream Author : m...@halfdog.net
 * URL : https://github.com/halfdog/guerillabackup
 * License : LGPL-3.0+
 * Vcs : https://salsa.debian.org/halfdog-guest/guerillabackup
   Section : misc

It builds those binary packages:

  guerillabackup - resilient, distributed backup and archiving solution

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/guerillabackup/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/g/guerillabackup/guerillabackup_0.1.1-1.dsc

Changes for the initial release:

 guerillabackup (0.1.1-1) unstable; urgency=medium
 .
   * Initial packaging of guerillabackup (Closes: #849714)

Regards,
-- 
  halfdog



Re: cmake: compat 11 vs 13 (-indep)

2022-01-15 Thread Niels Thykier
Niels Thykier:
> Mathieu Malaterre:
>> [cc me please]
>>
>> Symptoms:
>>
>> I've recently discovered the following change in behavior for
>> dh_missing + cmake + -indep. Basically using compat 13 it is now an
>> error when build-indep rule install stuff other than just the -indep
>> files (1).
>>
> 
> The error is not specifically caused by compat 13 but dh_missing
> --fail-missing. This happens to be default in compat 13. However, you
> can use "dh_missing --list-missing" in compat 13 to avoid the error (or
> use --fail-missing in compat 12 or earlier to reproduce the error there).
> 
> Depending on what you are going for, this may be sufficient.  You are
> not required to use debhelper at its default if they do not suit you.
> 
> Obviously, that does not solve the underlying issue with cmake/install.
>  I do not have an answer for that.
> 
> Thanks,
> ~Niels
> 

Having looked a bit more at the packaging involved, perhaps you can
solve this by replacing all the

 dh_install -p$(X) [...]

calls by moving the content into debian/X.install.  In compat 13, you
can do substitutions in debian/X.install now without relying on dh-exec.

This should enable dh_install to record what would have been installed
more reliably and maybe resolve the dh_missing issue you are seeing.

Thanks,
~Niels



Re: cmake: compat 11 vs 13 (-indep)

2022-01-15 Thread Niels Thykier
Mathieu Malaterre:
> [cc me please]
> 
> Symptoms:
> 
> I've recently discovered the following change in behavior for
> dh_missing + cmake + -indep. Basically using compat 13 it is now an
> error when build-indep rule install stuff other than just the -indep
> files (1).
> 

The error is not specifically caused by compat 13 but dh_missing
--fail-missing. This happens to be default in compat 13. However, you
can use "dh_missing --list-missing" in compat 13 to avoid the error (or
use --fail-missing in compat 12 or earlier to reproduce the error there).

Depending on what you are going for, this may be sufficient.  You are
not required to use debhelper at its default if they do not suit you.

Obviously, that does not solve the underlying issue with cmake/install.
 I do not have an answer for that.

Thanks,
~Niels



Bug#1003090: RFS: ffcvt/1.7.5-1

2022-01-15 Thread Nilesh Patra

Hi Tong,

On 1/15/22 2:55 AM, Tong Sun wrote:

Hi,

The situation should have been fixed with the new upload of easygen.

However, the CI build is still failing in salsa. This is something
that I don't understand as it builds OK on github.

Sorry I've run out of ideas why it is happening like this, and am now
thinking to remove the build dependency of easygen, to fix this and to
make things easier...


I still don't have a clue why


I intended to reply earlier, but I was occupied and simply forgot later, sorry 
about that!


it builds OK on github but fails in
salsa CI build, and I still hope that somebody can help.


Okay, so there are two parts to it.

1) Why does github CI pass?
Ok, so there are two reasons about this as well
 + test-all.sh does not seem to run anywhere in your github actions/CI and that 
error stems from this script (in the deb package)
 + `go test -v` in your CI essentially does nothing since there are no _test.go 
files and it is visible
on the CI too

| go test -v ./...
|  shell: /usr/bin/bash -e {0}
|  env:
|GOROOT: /opt/hostedtoolcache/go/1.15.15/x64
| github.com/suntong/ffcvt
| ? github.com/suntong/ffcvt[no test files]

So you probably should update it accordingly there as well.

2) For salsa CI, I thought that it is because of the failing build.
You will find the build failure logs pasted at the end of this email.
The reason for test to be failing is that you have not updated 
"test/ffcvt_test.txt" file in accordance with the
latest manpage/latest ffcvt options upstream.

However, even after I have pushed a patch to fix the build, salsa CI chokes.

@Alois, could you shed some light on the CI thingy?
From the logs, it is hard to figure out what went wrong.
The packages that are shown failing there do not have anything to do with ffcvt 
package, are the failing logs stored somewhere?


I'll wait for one or two weeks more, and if still nobody can help,


It is usually a good idea to ask on #debian-mentors if there is more delay in a 
reply.
Also, feel free to ping me if you think I can be of any help.


I'll remove the build dependency of easygen as planned, as I know for
sure it can fix the issue

I am not sure if that's the problem here. Why would it fix the issue?


Somebody help please.


Hope that helps. Let me know if you need sponsoring.

Regards,
Nilesh


| cd obj-x86_64-linux-gnu/src/github.com/suntong/ffcvt/test && ./test-all.sh
| ffcvt
| Version 1.7.5 built on 2022-01-02
| - Test (config.go) cli help output
| - Test transcoding single file
| - Test -sym control
| - Compare test results
| --- ffcvt_test.txt2022-01-15 07:35:05.137033394 +
| +++ /tmp/ffcvt_test.txt   2022-01-15 07:35:08.193097895 +
| @@ -6,3 +6,3 @@
|
| -  -t target type: webm/x265-opus/x264-mp3/youtube (FFCVT_T)
| +  -t target type: webm/x265-opus/x264-mp3/wx/youtube/copy (FFCVT_T)
|   -vesvideo encoding method set (FFCVT_VES)
| @@ -32,3 +32,8 @@
|   -vssvideo: same size (FFCVT_VSS)
| +  -C,Cut Cut segment(s) out to keep. Specify in the form of start-[end],
| + strictly in the format of hh:mm:ss, and may repeat (FFCVT_C,CUT)
| +  -S,Seg Split video into multiple segments (strictly in format: 
hh:mm:ss) (FFCVT_S,SEG)
| +  -Speed Speed up/down video playback speed (e.g. 1.28) (FFCVT_SPEED)
|   -lang   language selection for audio stream extraction (FFCVT_LANG)
| +  -sel   subtitle encoding language (language picked for reencoded 
video) (FFCVT_SEL)
|   -o  more options that will pass to ffmpeg program (FFCVT_O)
| @@ -49,2 +54,14 @@
|
| +  -C value
| + Cut segment(s) out to keep. Specify in the form of start-[end],
| + strictly in the format of hh:mm:ss, and may repeat
| +  -Cut value
| + Cut segment(s) out to keep. Specify in the form of start-[end],
| + strictly in the format of hh:mm:ss, and may repeat
| +  -S string
| + Split video into multiple segments (strictly in format: hh:mm:ss)
| +  -Seg string
| + Split video into multiple segments (strictly in format: hh:mm:ss)
| +  -Speed string
| + Speed up/down video playback speed (e.g. 1.28)
|   -abr string
| @@ -90,2 +107,4 @@
|   -p  par2create, create par2 files (in work directory)
| +  -sel value
| + subtitle encoding language (language picked for reencoded video)
|   -sep string
| @@ -99,3 +118,3 @@
|   -t string
| - target type: webm/x265-opus/x264-mp3/youtube (default "webm")
| + target type: webm/x265-opus/x264-mp3/wx/youtube/copy (default "webm")
|   -vc
| 1



OpenPGP_signature
Description: OpenPGP digital signature