Source of older package version?
John McNulty
johnmcn1 at gmail.com
Mon Nov 3 16:29:25 UTC 2025
Thanks Petr. I'm deploying onto AlmaLinux 9.
On Mon, 3 Nov 2025 at 16:09, Petr Menšík via bind-users <
bind-users at lists.isc.org> wrote:
> I do not have builds for every version. I think copr allows to serve
> multiple versions from the same repository. It depends on copr owner how
> many builds he keeps there.
>
> https://copr.fedorainfracloud.org/coprs/pemensik/bind-9.20/
>
> I try them only sometime. Not every release is there. You did not even
> specify your distribution. It would be relatively easy with Fedora to make
> your own rebuilds even with versions I have missing.
>
> Source:
> https://src.fedoraproject.org/fork/pemensik/rpms/bind/tree/rawhide-9.20
>
> How to rebuild:
>
> git clone https://src.fedoraproject.org/fork/pemensik/rpms/bind
> git checkout rawhide-9.20
>
> dnf install fedpkg
> dnf builddep *.spec
>
> edit version in spec file # find Version: and change it.
>
> spectool -g *.spec # downloads new sources
> fedpkg --release f42 local # consider using mockbuild.
>
> That would allow you to build any version not present in the repo. On
> Centos similar package is centpkg. --release would accept values like c9s
> or c10s in it. rpmbuild needs a bit modified directory structure.
>
> But in general, git bisect is amazing tool and you would likely want to
> know which commit or merge request it was related to in the end. That is
> much easier to find from original isc bind9 git repository, as you were
> advised before. But I admit it is not so simple to start and especially
> uninstall such test builds. You can configure the parameters with the same
> flags as the package does. named -V will print flags used in configure, use
> named from package to get values used by your distribution, then pass them
> to ./configure on your git checkout. You can use dnf builddep *.spec trick
> to get dependencies needed to build it from upstream sources git later.
>
> If bind 9.18 version would be enough, fedora should have almost all
> versions:
>
> https://koji.fedoraproject.org/koji/packageinfo?packageID=314
>
> But 9.20 is available from my or ISC copr only, because we still do not
> have 9.20 in official Fedora repos.
>
> Hope that helps,
> Petr
> On 03/11/2025 16:15, John McNulty wrote:
>
> Thanks, but I was looking for binary / rpm packages rather than source.
>
> Are sources my only option ?
>
> On Mon, 3 Nov 2025 at 14:45, Victoria Risk <vicky at isc.org> wrote:
>
>>
>>
>> On Nov 3, 2025, at 9:24 AM, Bjørn Mork via bind-users <
>> bind-users at lists.isc.org> wrote:
>>
>> John McNulty <johnmcn1 at gmail.com> writes:
>>
>> I'd like to step back through the versions to find out which release after
>> 9.20.7 introduced the change in behaviour before filing a bug report. But
>> I've not been successful in locating a source that contains them. Copr
>> only holds the latest release.
>>
>>
>> They're available as tags in git at least. Makes easier to bisect the
>> issue.
>>
>>
>> And just FYI, every release since the dawn of time is available somewhere
>> on downloads.isc.org. Look in https://downloads.isc.org/isc/bind9/
>> for versions since 2000…..
>>
>>
>>
>> --
>> Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
>> from this list.
>>
>
> --
> Petr Menšík
> Senior Software Engineer, RHEL
> Red Hat, https://www.redhat.com/
> PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
>
> --
> Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
> from this list.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20251103/29cbbd64/attachment-0001.htm>
More information about the bind-users
mailing list