[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1051299: marked as done (RFS: allegro4.4/2:4.4.3.1-4 -- portable library for cross-platform game and multimedia development)

Your message dated Wed, 6 Sep 2023 08:53:03 +0200
with message-id <20230906085303.0a1a21e0@heffalump.sk2.org>
and subject line Re: RFS: allegro4.4/2:4.4.3.1-4 -- portable library for cross-platform game and multimedia development
has caused the Debian Bug report #1051299,
regarding RFS: allegro4.4/2:4.4.3.1-4 -- portable library for cross-platform game and multimedia development
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 owner@bugs.debian.org
immediately.)


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

Dear mentors,

I am looking for a sponsor for my package "allegro4.4":

I am temporarily without a gpg key, so currently I cannot upload
packages. (I am in the progress to getting the required signatures for
a new key)

 * Package name     : allegro4.4
   Version          : 2:4.4.3.1-4
   Upstream contact : allegro-developers@lists.liballeg.org
 * URL              : http://www.liballeg.org
 * License          : Expat, LGPL-2+, Allegro-gift-ware, Zlib, Zlib or GPL-2+, glut
 * Vcs              : https://salsa.debian.org/games-team/allegro4.4
   Section          : devel

The source builds the following binary packages:

  liballegro4.4 - portable library for cross-platform game and multimedia development
  liballegro4-dev - development files for the Allegro library
  allegro4-doc - documentation for the Allegro library
  liballeggl4.4 - library to mix OpenGL graphics with Allegro routines
  liballeggl4-dev - development files for the allegrogl library
  libjpgalleg4.4 - JPG loading addon for Allegro 4
  libjpgalleg4-dev - development files for the JPG loading addon for Allegro 4
  libloadpng4.4 - PNG loading addon for Allegro 4
  libloadpng4-dev - development files for the PNG loading addon for Allegro 4
  liblogg4.4 - OGG loading addon for Allegro 4
  liblogg4-dev - development files for the OGG loading addon for Allegro 4

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

  https://mentors.debian.net/package/allegro4.4/

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

  dget -x https://mentors.debian.net/debian/pool/main/a/allegro4.4/allegro4.4_4.4.3.1-4.dsc

Changes since the last upload:

 allegro4.4 (2:4.4.3.1-4) unstable; urgency=medium
 .
   * Add a clean dh target to remove CHANGES - fixes building after a
     successful build (Closes: #1043942)
   * Build-dep on libgl-dev instead of libgl1-mesa-dev - Fixes lintian
     warning build-depends-on-obsolete-package
   * Fix watch file
   * Add Upstream-Contact to debian/copyright
   * Upgrade Standards Version to 4.6.2 (No changes required)

Regards,
-- 
  Andreas Rönnquist
  gusnan@debian.org

--- End Message ---
--- Begin Message --- 
On Wed, 6 Sep 2023 00:07:54 +0200, Andreas Rönnquist <gusnan@debian.org>
wrote:
> Changes since the last upload:
> 
>  allegro4.4 (2:4.4.3.1-4) unstable; urgency=medium
>  .
>    * Add a clean dh target to remove CHANGES - fixes building after a
>      successful build (Closes: #1043942)
>    * Build-dep on libgl-dev instead of libgl1-mesa-dev - Fixes lintian
>      warning build-depends-on-obsolete-package
>    * Fix watch file
>    * Add Upstream-Contact to debian/copyright
>    * Upgrade Standards Version to 4.6.2 (No changes required)

Tagged and uploaded, thanks!

Stephen

Attachment: pgpqvmbX6ia0x.pgp
Description: OpenPGP digital signature


--- End Message ---
Reply to: