Bug#1064837: Can closed

2024-02-29 Thread Jörg Frings-Fürst 
Hi, 

closed.

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


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


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

Skype:jff-skype@jff.email
Jami: joergfringsfuerst
Telegram: @joergfringsfuerst
Matrix:   @joergff:matrix.snct-gmbh.de

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






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

Bug#1064837: marked as done (RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions)

2024-02-29 Thread Debian Bug Tracking System 
Your message dated Fri, 01 Mar 2024 08:38:02 +0100
with message-id <14e9798ceeb8d1be6f070b62e23f1afd8a5a9e2e.camel@jff.email>
and subject line Can closed
has caused the Debian Bug report #1064837,
regarding RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and 
utility functions
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.)


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

Dear mentors,

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

 * Package name : libhx
   Version  : 4.23-1
   Upstream contact : Jan Engelhardt 
 * URL  : https://inai.de/projects/libhx/
 * License  : LGPL-2.1+, WTFPL-2+, GPL-2+
 * Vcs  : https://git.jff.email/cgit/libhx.git
   Section  : libs

The source builds the following binary packages:

  libhx32t64 - C library providing queue, tree, I/O and utility functions
  libhx-dev - Development files for libhx
  libhx-doc - Documentation files for libhx

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

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

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

 dget -x https://mentors.debian.net/debian/pool/main/libh/libhx/libhx_4.23-1.dsc

or from

 git https://git.jff.email/cgit/libhx.git?h=release%2Fdebian%2F4.23-1



Changes since the last upload:

 libhx (4.23-1)  experimental; urgency=medium
 .
   * New upstream release (Closes: #1064734).
   * Rename libraries for 64-bit time_t transition (Closes: #1062369).
 - Thanks to Steve Langasek .
   * Add debian/.gitignore
   * Remove not longer needed debian/libhx-dev.lintian-overrides.
   * Fix debian/libhx32t64.lintian-overrides.
   * debian/copyright:
 - Add 2024 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


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


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

Skype:jff-skype@jff.email
Jami: joergfringsfuerst
Telegram: @joergfringsfuerst
Matrix:   @joergff:matrix.snct-gmbh.de

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 ---
Hi, 

closed.

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


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


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

Skype:jff-skype@jff.email
Jami: joergfringsfuerst
Telegram: @joergfringsfuerst
Matrix:   @joergff:matrix.snct-gmbh.de

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 ---

Re: Bug#1065078: Question about the debian group on Salsa

2024-02-29 Thread Soren Stoutner 
Generally you should create the repository under the debian namespace unless 
you really don’t want anyone else making any changes to it, even if the 
changes are urgent and you are AFK for some reason.

I have created a repository named planner under debian and have granted you 
Developer access.  :)

On Thursday, February 29, 2024 7:28:59 AM MST Shriram Ravindranathan wrote:
> Dear mentors,
> 
> I'm curious about the guidelines for putting a package under the debian 
> namespace on Salsa . I wasn't able to 
> find much discourse about this online.
> 
> This package didn't have a salsa repository created for it, I am unsure 
> whether I should create a repository under my own namespace or if the 
> package should be placed under the debian namespace.
> 
> Thank you,
> 
> -- 
> Shriram Ravindranathan
> 


-- 
Soren Stoutner
so...@debian.org

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

Bug#1065102: RFS: serioussam/1.10.6d+dfsg-1 [ITP]

2024-02-29 Thread Alexander Pavlov 
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name : serioussam
   Version  : 1.10.6d+dfsg-1
   Upstream contact : https://github.com/tx00100xt/SeriousSamClassic/issues
 * URL  :
https://www.croteam.com/serious-sam-source-code-released/
 * License  : GPL-2
 * Vcs  : https://salsa.debian.org/tx00100xt/serioussam
   Section  : contrib/games

The source code builds a binary package for games::

  Serious Sam - The First Encounter
  Serious Sam - The Second Encounter

All files are located as indicated here:

  https://wiki.debian.org/Games/Checklist

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/contrib/s/serioussam/serioussam_1.10.6d-+dfsg-1.dsc

Changes for the initial release:

 serioussam (1.10.6d+dfsg-1) unstable; urgency=low
 .
   * Initial release. Closes: #1065096


This package alone isn't of any use; it only contains the game engine,
an engine that has no Free data and therefore is in contrib.
You will need a copy of the original game for this package to be
useful.

Best Regards,
Alexander Pavlov.

Bug#1065078: Question about the debian group on Salsa

2024-02-29 Thread Shriram Ravindranathan 

Dear mentors,

I'm curious about the guidelines for putting a package under the debian 
namespace on Salsa . I wasn't able to 
find much discourse about this online.


This package didn't have a salsa repository created for it, I am unsure 
whether I should create a repository under my own namespace or if the 
package should be placed under the debian namespace.


Thank you,

--
Shriram Ravindranathan



OpenPGP_0xFC7E951A7BEF0836.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065078: RFS: planner/0.14.92-1 [ITA] -- project management application

2024-02-29 Thread Shriram Ravindranathan 

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : planner
   Version  : 0.14.92-1
   Upstream contact : [fill in name and email of upstream]
 * URL  : https://wiki.gnome.org/action/show/Apps/Planner
 * License  : GPL-2+, GPL-2, BSD-like
 * Vcs  : [fill in URL of packaging vcs]
   Section  : gnome

The source builds the following binary packages:

  planner - project management application
  planner-doc - Documentation for planner
  planner-data - Data files for planner

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/planner/planner_0.14.92-1.dsc

Changes since the last upload:

 planner (0.14.92-1) unstable; urgency=medium
 .
   * New upstream version 0.14.92
   * New Maintainer (Closes: #892919)
   * d/control:
 - Bump Standards-Version to 4.6.2
 - Bump debhelper-compat version to 13
 - Add new maintainer's name to maintainer field.
   * d/copyright:
 - Change source url to use https
 - Add new authors' copyright details
 - Update copyright years
 - Add new maintainer to copyright field
   * d/watch:
 - Bump watch version to 4
   * Add d/upstream/metadata
   * Add libplanner-*.so symlink to not-installed
   * Add usr/share/GConf to planner-data.install
   * Add planner.lintian-override (unnecessary ldconfig activation)
   * Add planner-data.lintian-override (missing desktop command)
 .
   [Helmut Grohne]
   * d/rules: Fix FTCBFS, skip gtkdoc in arch-only build (Closes: #1062785)
 .
   [Marriott NZ]
   * d/planner.mime: Remove quoted placeholder from mailcap entry. Fixes
 lintian warning (Closes: #987406)

Regards,
--
  Shriram Ravindranathan



OpenPGP_0xFC7E951A7BEF0836.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Remove package from unstable?

2024-02-29 Thread Gianfranco Costamagna 
Did we ever implement the "bump epoch should go to new queue"?

I would like to see packages going in some new queue, this way ftpmasters can 
check if the epoch bump was a mistake or not.
(and I can't just test by myself, I don't want to risk bumping epoch on my 
packages!)

G.






Il giovedì 29 febbraio 2024 alle ore 01:15:59 CET, Dominik George 
 ha scritto: 





Hi,


> a) The version numbering rules provide for a '1:' prefix to be used to
>deal with version numbering mistakes. A version number starting with
>'1:' counts as higher than any without such a prefix; a '2:' counts as
>higher than '1:', etc. So you could re-upload 2.10.08+ds-1 with version
>number '1:2.10.08+ds-1' to supplant 2.11.01+ds-3. However the downside
>to this approach is that you're forevermore committed to having that
>prefix in the version numbering.


Don't do this.

Using am epoch has to be agreed on in the project, and for good reasons. First 
and foremost, the epoch is not encoded into the package file name, thus causing 
trouble when in the future you get to upload 1:2.11.01.

-nik