Package: sponsorship-requests
Severity: normal
From: Sven Hartge
To: sub...@bugs.debian.org
Subject: RFS: radsecproxy/1.11.1-1 -- RADIUS protocol proxy supporting RadSec
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsec
On 05.08.24 16:52, PICCA Frederic-Emmanuel wrote:
WRT the license checks, I found out that there is an integration with
Salsa CI available to get on the spot lrc reports, just by doing
include:
-
https://salsa.debian.org/debian/licenserecon/raw/main/debian/licenserecon.yml
> and why not act
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.11.0-1~bpo12+1
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License
On 25.07.24 14:51, Phil Wyett wrote:
One to look into at your leisure and not a showstopper.
philwyett@ks-windu:~/Development/builder/debian/mentoring/radsecproxy-1.11.0$
lrc
: Versions: recon 1.12 check 3.3.9-1
Parsing Source Tree
Reading copyright
Running licensecheck
d/
On 25.07.24 15:42, Sven Hartge wrote:
On 25.07.24 14:51, Phil Wyett wrote:
BSD-3-clause | GPL-3+ with Autoconf-2.0~Archive exception
ax_build_date_epoch.m4
Thank you for your review, but I will fix the license issue while I am
at it.
I think lrc has a bug parsing debian/copyright with
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.11.0-1
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.10.1-1
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.10.0-2~bpo12+1
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.10.0-2
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.10.0-1
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
On Mon, 6 Mar 2023 17:02:07 +0100 Sven Hartge wrote:
Changes since the last upload:
radsecproxy (1.9.2-2) unstable; urgency=medium
.
* Improve logcheck patterns to reduce noise
* Make logcheck rules compatible with all syslog timestamp formats
I really would like to get those
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.9.2-2
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.9.2-1~bpo11+1
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.9.2-1
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
w upstream version 1.9.1
Compatible with OpenSSL 3.0
.
[ Faidon Liambotis ]
* Replace myself (Faidon) with Sven as the maintainer
.
[ Sven Hartge ]
* Compatible with Policy 4.6.0.0, no changes needed
* Taking over full maintainership, many thanks to Faidon for his work
i
On 29.08.21 16:40, Baptiste Beauplat wrote:
On 2021/08/26 10:15 PM, Baptiste Beauplat wrote:
On 2021/08/26 02:41 PM, Sven Hartge wrote:
I noticed a little weirdness when uploading a package for multiple
suites, in my case for "bullseye-backports" and
"buster-backports-sloppy&
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy".
Since this is the first upload to buster-backports-sloppy, a full binary
upload will be needed.
* Package name: radsecproxy
Version : 1.9.0-1~bpo10+1
Upstre
Hello .*,
I noticed a little weirdness when uploading a package for multiple
suites, in my case for "bullseye-backports" and
"buster-backports-sloppy".
Reference is https://mentors.debian.net/package/radsecproxy/
I uploaded version 1.9.0-1~bpo10+1 first and then 1.9.0-1~bpo11+1
second.
The latt
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy".
As this is the first upload to "bullseye-backports", a full binary
upload will be necessary.
* Package name: radsecproxy
Version : 1.9.0-1~bpo11+1
Upstream
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.9.0-1
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License : BSD-3
The Wanderer wrote:
> I genuinely do not see what insisting on uninstalling plugins at the
> same time as the main program, for all user accounts, provides as a
> benefit. The only maybe benefit I've seen suggested is cleaning up to
> free disk space, and that seems to me to be so obviously heavi
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.8.2-4~bpo10+1
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.9.0-1~exp1
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.8.2-4
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License : BSD-3
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.9.0~rc1-1~exp1
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License
Jon Gough wrote:
> So, any user installable application extension/plugin which has
> executables and supporting data is left behind on the system when the
> owning application is removed or updated using the system installation
> process? This is accepted behaviour?
Yes, this is accepted b
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.8.2-4~exp1
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.8.2-3
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License : BSD-3
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy".
This version of the package will be the first upload to buster-backports
and a full binary upload is needed for it to clear NEW.
* Package name: radsecproxy
Version
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.8.2-2
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License : BSD-3-
w upstream version 1.8.2
* Upgrade debhelper compat level to 13.
* Remove patches applied upstream
* Move man-pages for radsecproxy[-hash] into section 8 to be compliant
with the FHS.
* Add lintian override for testsuite-autopkgtest-missing.
Regards,
--
Sven Hartge
close 964778
thanks
Newer version will be uploaded to backport later.
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy"
* Package name: radsecproxy
Version : 1.8.1-2~bpo10+1
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
* Bump Standards-Version to 4.5.0, no changes needed.
Regards,
--
Sven Hartge
Tong Sun wrote:
> --
> $ ls -l `dpkg -L dbab` > /dev/null
> ls: cannot access '/usr/share/doc/dbab/README.Debian': No such file or
> directory
> ls: cannot access '/usr/share/doc/dbab/changelog.Debian.gz': No such file
> or directory
> ls: cannot access '/usr/s
Nico Schlömer wrote:
> I'm starting to package Stellar, a tet mesh optimizer [1].
> The package is very basic, but still things are failing. I don't know why.
> 1. The gitlab-ci build [2] fails with
> ```
> Checking cache for default...
> FATAL: file does not exist
> Failed to extract cache
> `
Nico Schlömer wrote:
> From the gmsh repro-build, I'm getting
> ```
> /builds/science-team/gmsh/debian/output: found 38 matching files
> ERROR: Uploading artifacts to coordinator... too large archive
> id=227001 responseStatus=413 Request Entity Too Large status=413
> Request Entity Too Large tok
Mattia Rizzolo wrote:
> On Mon, Mar 05, 2018 at 10:44:13PM +0100, Sven Hartge wrote:
>> I am co-maintaining bacula with Carsten Leonhardt and this problem
>> now occured several times for me. (Most probably because of misuse by
>> me, but I want to understand what went wr
<
foobar (1.0-3) UNRELEASED; urgency=medium
* Third
--
foobar (1.0-2) unstable; urgency=medium
* Second
-- Sven Hartge Mon, 05 Mar 2018 22:31:33 +0100
foobar (1.0-1) unstable; urgency=medium
* Initial release.
-- Sven Hartge Mon, 05 Mar 2018 22:31:03 +0100
-
39 matches
Mail list logo
