From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/pnglite/
Date: Thu, 25 Nov 2021 14:45:18 +0000 (UTC) [thread overview]
Message-ID: <1637851512.af580119fb0a6eb0b36b04a70b705fc892d64bd9.marecki@gentoo> (raw)
commit: af580119fb0a6eb0b36b04a70b705fc892d64bd9
Author: Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Thu Nov 25 14:43:49 2021 +0000
Commit: Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Thu Nov 25 14:45:12 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=af580119
media-libs/pnglite: update SRC_URI
It actually appeared to work fine without "project/" - but let's do this
properly and use the exact URI to which the old one now gets redirected.
Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>
media-libs/pnglite/pnglite-0.1.17-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/media-libs/pnglite/pnglite-0.1.17-r1.ebuild b/media-libs/pnglite/pnglite-0.1.17-r1.ebuild
index 4b5669ea7d37..fbbb21944154 100644
--- a/media-libs/pnglite/pnglite-0.1.17-r1.ebuild
+++ b/media-libs/pnglite/pnglite-0.1.17-r1.ebuild
@@ -7,7 +7,7 @@ inherit flag-o-matic toolchain-funcs
DESCRIPTION="Small and simple library for loading and writing PNG images"
HOMEPAGE="https://sourceforge.net/projects/pnglite/"
-SRC_URI="mirror://sourceforge/${PN}/${PN}/${PV}/${P}.zip"
+SRC_URI="mirror://sourceforge/project/${PN}/${PN}/${PV}/${P}.zip"
LICENSE="ZLIB"
SLOT="0"
next reply other threads:[~2021-11-25 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 14:45 Marek Szuba [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-16 18:15 [gentoo-commits] repo/gentoo:master commit in: media-libs/pnglite/ Jakov Smolić
2021-12-16 18:06 Jakov Smolić
2021-12-15 16:42 Jakov Smolić
2021-11-25 13:19 Marek Szuba
2021-11-17 2:19 Sam James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1637851512.af580119fb0a6eb0b36b04a70b705fc892d64bd9.marecki@gentoo \
--to=marecki@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox