-- 
Gwyn Ciesla
she/her/hers
------------------------------------------------ 
in your fear, seek only peace 
in your fear, seek only love
-d. bowie

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, January 27, 2021 10:50 AM, Vít Ondruch <vondr...@redhat.com> 
wrote:

> You can do this in mock without messing with your system. You can use `mock 
> -i some.rpm`, you can even use `mock --pm-cmd whatever dnf command you want 
> to use`. You can use `mock your.srpm --short-circuit=install` and similar. 
> You can use `mock shell --unpriv` if you want to tinker more. Mock is 
> everything you ever wanted to develop for Fedora.
> 

> So could you please share with us specifics of your workflow which makes it 
> unique and which really requires `fedpkg local`? I can't imaging that 
> intentionally breaking the host system due to testing soname bump is the 
> right thing to do.

Ok, let's say I have to update a library, let's say LibRaw, and the soname 
changes.

I fire up a rawhide VM, and clone the LibRaw repo, update the spec, build, and 
install it. Then I clone the dependant repos, update their specs, and build 
them.  Failures are immediately apparent, and I can quickly work on patches or 
obtain logs of failures for sending upstream. I can easily get into the source 
tree to examine files, quickly test tweaks to build commands, etc. Once it all 
builds, I do a mock chain build, then an srpm koji scratch build, and if all is 
well, I commit, push, and chain-build in koji.

I always use mock for final smoketesting and rooting out missed BuildRequires, 
but being forced to use mock for the whole process would greatly lengthen the 
process.

> Vít
> 

> Dne 27. 01. 21 v 17:37 Radovan Sroka napsal(a):
> 

> > "fedpkg local lets me cycle through build failures faster in the early 
> > stages"
> > 

> > Totally agree.
> > 

> > On Wed, Jan 27, 2021 at 5:34 PM Gwyn Ciesla via devel 
> > <devel@lists.fedoraproject.org> wrote:
> > 

> > > -- 
> > > Gwyn Ciesla
> > > she/her/hers
> > > ------------------------------------------------ 
> > > in your fear, seek only peace 
> > > in your fear, seek only love
> > > -d. bowie
> > > 

> > > Sent with ProtonMail Secure Email.
> > > 

> > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > On Wednesday, January 27, 2021 10:27 AM, Fabio Valentini 
> > > <decatho...@gmail.com> wrote:
> > > 

> > > > On Wed, Jan 27, 2021 at 5:24 PM Gwyn Ciesla via devel
> > > > devel@lists.fedoraproject.org wrote:
> > > >
> > > 

> > > > > It's needed for testing builds against versions of packages not yet 
> > > > > in mock. I use it almost every day. Losing it would make things like 
> > > > > testing solib bumps harder.
> > > >
> > > 

> > > > I've done local test builds for soname bumps and similar things lots
> > > > of times, and I've never used (or thought about using) fedpkg local
> > > > for that.
> > > > I used "mock --chain" or a combination of "mock --postinstall
> > > > --no-clean" for those builds ... which is much closer to what koji
> > > > will do with your builds, and gives every build the clean environment
> > > > it deserves >:-)
> > > 

> > > That's a great thing to do, but fedpkg local lets me cycle through build 
> > > failures faster in the early stages. I'd really hate to see it go; If 
> > > others don't use it, they can keep not using it. :)
> > > 

> > > >
> > > 

> > > > Fabio
> > > >
> > > 

> > > > devel mailing list -- devel@lists.fedoraproject.org
> > > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > > > Fedora Code of Conduct: 
> > > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > > List Archives: 
> > > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> > > 

> > > _______________________________________________
> > > devel mailing list -- devel@lists.fedoraproject.org
> > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > > Fedora Code of Conduct: 
> > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > List Archives: 
> > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> > 

> > --
> > 

> > --
> > ---------------------------------------------------------
> > 

> > Radovan Sroka
> > Software Engineer | Security Technologies | Red Hat, Inc.
> > 

> > _______________________________________________
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: 
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Reply via email to