Your message dated Wed, 28 Oct 2026 00:47:02 +0100
with message-id <[email protected]>
and subject line Re: Bug#1152322: libaio-dev: Upstream metadata incorrect in 
source tree
has caused the Debian Bug report #1152322,
regarding libaio-dev: Upstream metadata incorrect in source tree
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 [email protected]
immediately.)


-- 
1152322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1152322
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libaio-dev
Version: 0.3.113-9
Severity: normal

Dear Maintainer,
The 'Meta' information as to the location of the upstream source is no
longer correct.

https://pagure.io/libaio.git is a readonly snapshot; pagure.io is deprecated.

I believe the upstream is now at https://pagure.io/libaio.git

A patch might be:

diff -ru debian-old/control debian/control
--- debian-old/control  2026-10-28 08:24:39.398583520 +1100
+++ debian/control      2026-10-28 08:25:58.407519520 +1100
@@ -3,7 +3,7 @@
 Section: libs
 Vcs-Browser: https://git.hadrons.org/cgit/debian/pkgs/libaio.git
 Vcs-Git: https://git.hadrons.org/git/debian/pkgs/libaio.git
-Homepage: https://pagure.io/libaio
+Homepage: https://codeberg.org/jmoyer/libaio
 Standards-Version: 4.7.3
 Build-Depends:
  debhelper-compat (= 13),
diff -ru debian-old/upstream/metadata debian/upstream/metadata
--- debian-old/upstream/metadata        2026-10-28 08:24:39.399461186 +1100
+++ debian/upstream/metadata    2026-10-28 08:26:25.407827399 +1100
@@ -1,4 +1,4 @@
-Repository: https://pagure.io/libaio.git
-Repository-Browse: https://pagure.io/libaio
-Bug-Database: https://pagure.io/libaio/issues
-Bug-Submit: https://pagure.io/libaio/new_issue
+Repository: https://codeberg.org/jmoyer/libaio.git
+Repository-Browse: https://codeberg.org/jmoyer/libaio
+Bug-Database: https://codeberg.org/jmoyer/libaio/issues
+Bug-Submit: https://codeberg.org/jmoyer/libaio/new_issue



-- System Information:
Debian Release: forky/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, i386, arm64

Kernel: Linux 7.2.11+deb14-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 0.3.113-10

Hi!

On Wed, 2026-10-28 at 08:29:05 +1100, Peter Chubb wrote:
> Source: libaio-dev
> Version: 0.3.113-9
> Severity: normal

> The 'Meta' information as to the location of the upstream source is no
> longer correct.
> 
> https://pagure.io/libaio.git is a readonly snapshot; pagure.io is deprecated.
> 
> I believe the upstream is now at https://pagure.io/libaio.git

This had already been fixed in 0.3.113-10 (already in testing and
unstable), with the following changelog:

,---
libaio (0.3.113-10) unstable; urgency=medium

  * Remove build dependency on debhelper (>= 13.10) implied by
    debhelper-compat (= 13) since Debian bookworm.
  * Switch to Standards-Version 4.7.4 (no changes needed).
  * Refactor common description into a source stanza Description field.
  * Switch upstream site from decommissioned pagure.io to codeberg.org.

 -- Guillem Jover <[email protected]>  Sat, 17 Oct 2026 17:57:49 +0200
`---

Including changes to the copyright and watch files. Thus closing.

Thanks,
Guillem

--- End Message ---

Reply via email to