Bug#1030528: RFS: mg/20221112-1

2023-02-04 Thread Harald Dunkel

Package: sponsorship-requests
Severity: normal

Hi folks,

I am looking for a new sponsor for my "mg" package, which is already in
Debian and hosted on Salsa. I tried to contact the old sponsor several
times, but I got no response.

 * Package name : mg
   Version  : 20221112-1
   Upstream contact : Han Boetes 
 * URL  : https://github.com/hboetes/mg
 * License  : public-domain
 * Vcs  : https://salsa.debian.org/debian/mg

The source builds the following binary packages:

  mg - microscopic GNU Emacs-style editor

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

  https://salsa.debian.org/debian/mg
  https://packages.debian.org/sid/mg
  https://tracker.debian.org/pkg/mg

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

  none yet

Changes since the last upload:

mg (20221112-1) unstable; urgency=medium

  * new upstream version 20221112

 -- Harald Dunkel   Sat, 19 Nov 2022 19:16:48 +0100


Thank you very much

Harri



Bug#1029186: reply: RFS: libcommons-validator-java/1:1.7-1 [Team] -- ease and speed development and maintenance of validation rules

2023-02-04 Thread min sun

> Hello Min Sun,
>
> is there a particular reason why you opt for / stick to distribution
> `UNRELEASED` for a package already monitored by the tracker?[1]  It is the
> entry e.g., `dch -i` puts into file `/debian/changelog` when you start to work
> on a new version (increment) of a package.  After all other other work on your
> side is done, an eventual change to the string `unstable` (then lower case
> only) is one of the keys necessary to let results of your work enter branch
> `unstable`, and later `testing`, etc.

Thanks for your clarification, Tony,

I did not mean to specify it as `UNRELEASE`, the ‘uscan and uupdate” tools  
insert this keyword to debian/changelog.

I am not clear about the internal mechanism from `UNRELEASED` to `testing` and 
later stage.

I need learn more about Debian policy along with your guideline.

All the best.


Bug#1030390: marked as done (RFS: termpaint/0.3.0-2 -- low level terminal access)

2023-02-04 Thread Debian Bug Tracking System
Your message dated Sat, 4 Feb 2023 16:43:51 +0100
with message-id 
and subject line Re: RFS: termpaint/0.3.0-2 -- low level terminal access
has caused the Debian Bug report #1030390,
regarding RFS: termpaint/0.3.0-2 -- low level terminal access
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : termpaint
   Version  : 0.3.0-2
   Upstream contact : Martin Hostettler 
 * URL  : https://termpaint.namepad.de/
 * License  : 0BSD or BSL-1.0 or MIT-0, BSL-1.0, BSD-3-clause, 
bzip2-1.0.6, BSD-2-clause, BSL-1.0 or Expat

 * Vcs  : https://salsa.debian.org/debian/termpaint
   Section  : libs

The source builds the following binary packages:

  libtermpaint0a - low level terminal access - shared library
  libtermpaint-dev - low level terminal access - headers

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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/t/termpaint/termpaint_0.3.0-2.dsc


Changes since the last upload:

 termpaint (0.3.0-2) unstable; urgency=medium
 .
   * Fix Vcs-Git URL in debian/control
   * Fix mismatched lintian override very-long-line-length-in-source-file
   * Add patch to enable building on armel supplied by upstream
   * Update out-of-date-standards-version to 4.6.2

Regards,
--
  Christoph Hueffelmann
--- End Message ---
--- Begin Message ---

Thanks for the update!--- End Message ---


Re: Bug#1029186: reply: RFS: libcommons-validator-java/1:1.7-1 [Team] -- ease and speed development and maintenance of validation rules

2023-02-04 Thread Soren Stoutner
`UNRELEASED` is used because it will cause a failure if you accidentally try 
to upload it, which prevents accidental releases before they are intended.  At 
the point of release, you should change it to be `unstable` or `experimental` 
or a backports repository.

On Saturday, February 4, 2023 8:18:19 AM MST min sun wrote:
> > Hello Min Sun,
> > 
> > is there a particular reason why you opt for / stick to distribution
> > `UNRELEASED` for a package already monitored by the tracker?[1]  It is the
> > entry e.g., `dch -i` puts into file `/debian/changelog` when you start to
> > work on a new version (increment) of a package.  After all other other
> > work on your side is done, an eventual change to the string `unstable`
> > (then lower case only) is one of the keys necessary to let results of
> > your work enter branch `unstable`, and later `testing`, etc.
> 
> Thanks for your clarification, Tony,
> 
> I did not mean to specify it as `UNRELEASE`, the ‘uscan and uupdate” tools 
> insert this keyword to debian/changelog.
> 
> I am not clear about the internal mechanism from `UNRELEASED` to `testing`
> and later stage.
> 
> I need learn more about Debian policy along with your guideline.
> 
> All the best.


-- 
Soren Stoutner
so...@stoutner.com

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


Bug#1030163: marked as done (RFS: ipmiutil/3.1.8-4 -- IPMI management utilities)

2023-02-04 Thread Debian Bug Tracking System
Your message dated Sat, 4 Feb 2023 17:50:23 +0100
with message-id <72450037-ed99-b6fa-d06a-2a785ce54...@debian.org>
and subject line Re: RFS: ipmiutil/3.1.8-4 -- IPMI management utilities
has caused the Debian Bug report #1030163,
regarding RFS: ipmiutil/3.1.8-4 -- IPMI management utilities
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1030163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

   Package name : ipmiutil
   Version  : 3.1.8-4
   Upstream contact : [fill in name and email of upstream]
   URL  : https://sourceforge.net/projects/ipmiutil/
   License  : GPL-2+, GPL-2+ with OpenSSL exception, Zlib, 
  BSD-3-clause, BSD-2-clause, Artistic-2.0
   Vcs  : https://jff.email/cgit/ipmiutil.git
   Section  : utils

The source builds the following binary packages:

  ipmiutil - IPMI management utilities

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

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

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

 dget -x 
https://mentors.debian.net/debian/pool/main/i/ipmiutil/ipmiutil_3.1.8-4.dsc

or from

 git https://jff.email/cgit/ipmiutil.git/?h=release%2Fdebian%2F3.1.8-4


Changes since the last upload:

 ipmiutil (3.1.8-4) unstable; urgency=medium
 .
   * debian/patches/0705-crontab.patch: Fix typo (Closes: #1030120).
   * debian/control:
 - Remove superseded package lsb-base.
 - Remove version information no longer needed.
   * Declare compliance with Debian Policy 4.6.2.0 (No changes needed).
   * debian/copyright:
 - Add year 2023 to myself.

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---

Thanks for the update.--- End Message ---


Bug#1030307: RFS: posixsignalmanager/0.3-2 -- posix signal handling for qt

2023-02-04 Thread Bastian Germann

Hi Christoph,

Please do not fold the upstream PR into one patch file. That makes tracking it 
very hard.

Thanks,
Bastian



Bug#1030307: RFS: posixsignalmanager/0.3-2 -- posix signal handling for qt

2023-02-04 Thread Christoph Hueffelmann

Hello Bastian,

I am very sorry about that. I will do that next time.

Thank you for your time and effort.

Christoph


Am 04.02.23 um 18:07 schrieb Bastian Germann:

Hi Christoph,

Please do not fold the upstream PR into one patch file. That makes 
tracking it very hard.


Thanks,
Bastian




Bug#1030307: RFS: posixsignalmanager/0.3-2 -- posix signal handling for qt

2023-02-04 Thread Christoph Hueffelmann

Hello Bastian,

sorry, now I understand. I have split the patches, cherry-pick the 
commits from upstream and reupload it.


Thank you for your time and effort.

Christoph



Bug#1030547: RFS: ghostscript/9.53.3~dfsg-7+deb11u3 [NMU] -- interpreter for the PostScript language and for PDF

2023-02-04 Thread Håvard F . Aasen
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : ghostscript
   Version  : 9.53.3~dfsg-7+deb11u3
   Upstream contact : Ghostscript development and discussion 

 * URL  : https://www.ghostscript.com/
 * License  : GPL-2+, public-domain, BSD-3-Clause, NTP~Open, GPL-3+ 
with Autoconf exception, Apache-2.0, none, LGPL-2.1, ZLIB, NTP~WSU, 
BSD-3-Clause~Adobe, AGPL-3+ and custom, AGPL-3+ with font exception, 
GAP~configure, ISC, NTP~Lucent, AGPL-3+, Adobe-2006, GPL, Expat~Ghostgum, 
Expat, AGPL-3+ and FTL, Expat~SunSoft with SunSoft exception
 * Vcs  : https://salsa.debian.org/printing-team/ghostscript
   Section  : text

The source builds the following binary packages:

  ghostscript - interpreter for the PostScript language and for PDF
  ghostscript-x - interpreter for the PostScript language and for PDF - X11 
support
  ghostscript-doc - interpreter for the PostScript language and for PDF - 
Documentation
  libgs9 - interpreter for the PostScript language and for PDF - Library
  libgs9-common - interpreter for the PostScript language and for PDF - common 
files
  libgs-dev - interpreter for the PostScript language and for PDF - Development 
Files

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/ghostscript/ghostscript_9.53.3~dfsg-7+deb11u3.dsc

Changes since the last upload:

 ghostscript (9.53.3~dfsg-7+deb11u3) bullseye; urgency=medium
 .
   * Non-maintainer upload.
   * Cherry-pick upstream patch to fix path for PostScript helper file in
 ps2epsi. Closes: #1003926, #1029541


Upload is confirmed for stable [1].

Regards,
Håvard


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029619