Bug#1046037: marked as done (jool: Fails to build source after successful build)

2024-01-03 Thread Alberto Leiva
For the record: The problem was that the Makefiles not managed by autotools were missing the "distclean" target. Therefore, dh_auto_clean was falling back to `make clean` (when it actually wanted to run `make distclean`), which skipped the removal of a bunch of files generated by `configure`: -

Bug#1041311: marked as done (jool: please drop superfluous B-D: dkms)

2023-12-22 Thread Alberto Leiva
Sorry, Andreas. As mentioned in the other bug, I struggle to notice these bug reports among the Debian notifications. Removing dkms from Build-Depends results in a Lintian error: E: jool source: missing-build-dependency-for-dh_-command dh_dkms => dkms N: E:

Bug#1057703: Please stop build-depending on mime-support

2023-12-22 Thread Alberto Leiva
Sorry; I struggle to notice these bug reports among the Debian notifications. Thank you; I will have this fixed by version 4.1.11, which should be released tomorrow at the latest. On Tue, Dec 12, 2023 at 8:29 AM Charles Plessy wrote: > > Le Thu, Dec 07, 2023 at 08:14:30PM +0900, Charles Plessy

Bug#1001060: jool-tools: joold state syncer fails on linux >= 5.10

2021-12-03 Thread Alberto Leiva
Ok. You're right; I should release 4.1.6 already. I've scheduled to do it next week. It should be out by next Friday. (But 4.1.6-1 will migrate to testing later, of course.) On Fri, Dec 3, 2021 at 6:15 AM Philipp S. Tiesel < ph...@in-panik.de> wrote: > Package: jool-tools > Version: 4.1.5-1 >

Bug#946681: jool: Fix FTBFS with kernel >= 5.4

2019-12-16 Thread Alberto Leiva
Thank you. I'll have this upstreamed by version 4.0.7, which will hopefully be released tomorrow. On Fri, Dec 13, 2019 at 10:24 AM Paolo Pisati wrote: > > Package: jool > Version: 4.0.6-1 > Severity: important > Tags: patch > User: ubuntu-de...@lists.ubuntu.com > Usertags: origin-ubuntu focal

Bug#883393: jool Debian packaging

2019-07-19 Thread Alberto Leiva
y get ConditionPathExists. It doesn't seem to do anything. Even if the file doesn't exist, it still attempts to start the service, and fails during the ExecStart. On Fri, Jul 19, 2019 at 1:07 PM Alberto Leiva wrote: > > https://mentors.debian.net/package/jool > How do I assign bug 931960 to this package?

Bug#883393: jool Debian packaging

2019-07-19 Thread Alberto Leiva
https://mentors.debian.net/package/jool How do I assign bug 931960 to this package?

Bug#883393: jool Debian packaging

2019-07-15 Thread Alberto Leiva
> > Hi @all > > Am Sat, 13 Jul 2019 schrieb Vincent Bernat: > > > ❦ 13 juillet 2019 12:29 -05, Alberto Leiva : > > > I sent him another email on 2018-05-28, and then another one two days > > > ago. Both of them have gone unanswered as of now. > > > &

Bug#883393: jool Debian packaging

2019-07-13 Thread Alberto Leiva
Thank you for your review! > - d/changelog: do you have any contact with Bjoern Buerger, the > original author of the ITP? We talked up to 2018-05-10. I sent him another email on 2018-05-28, and then another one two days ago. Both of them have gone unanswered as of now. > - d/copyright: as

Bug#931960: RFS: jool/4.0.2-1 [ITP] -- IP/ICMP Translators

2019-07-12 Thread Alberto Leiva Popper
ckage/jool Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/j/jool/jool_4.0.2-1.dsc Regards, Alberto Leiva Popper

Bug#883393:

2019-07-12 Thread Alberto Leiva
Looking for a sponsor... https://mentors.debian.net/package/jool On Thu, Jul 11, 2019 at 1:22 PM Alberto Leiva wrote: > > > Hello. upstream author (and perhaps future upstream maintainer as well) > > here. > > Derp. I meant "Hello. Upstream author, upstream maintain

Bug#883393: ITP: jool -- Open Source SIIT and NAT64 Translator for Linux

2019-07-11 Thread Alberto Leiva
> Any progress on this? Do you need help packaging? Hello. upstream author (and perhaps future upstream maintainer as well) here. I've been working on this since June 17 (2019). I have Jool packages seemingly working properly, and recently finished scanning the Debian Policy Manual, making sure