On Wed, May 20, 2020 at 05:56:23PM +0200, Igor Raits wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> I think you might have cache of buildroot which was populated using BDB
> backend, so I guess if you clean mock caches, the problem should go
> away.
Thanks, the issue went away
On Wed, May 20, 2020 at 11:31:37 -0400,
Neal Gompa wrote:
On Wed, May 20, 2020 at 11:06 AM Zbigniew Jędrzejewski-Szmek
wrote:
I'm seeing this when running fedora-review:
$ fedora-review -b 1838033
INFO: Processing bugzilla bug: 1838033
...
INFO: Installing built package(s)
warning: Found
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I think you might have cache of buildroot which was populated using BDB
backend, so I guess if you clean mock caches, the problem should go
away.
On Wed, 2020-05-20 at 15:04 +, Zbigniew Jędrzejewski-Szmek wrote:
> I'm seeing this when running
On Wed, May 20, 2020 at 11:06 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> I'm seeing this when running fedora-review:
>
> $ fedora-review -b 1838033
> INFO: Processing bugzilla bug: 1838033
> ...
> INFO: Installing built package(s)
> warning: Found bdb Packages database while attempting sqlite
I'm seeing this when running fedora-review:
$ fedora-review -b 1838033
INFO: Processing bugzilla bug: 1838033
...
INFO: Installing built package(s)
warning: Found bdb Packages database while attempting sqlite backend: using bdb
backend.
INFO: Active plugins: Generic, Shell-api, Java
warning:
On Thu, Mar 26, 2020, at 8:35 AM, Zbigniew Jędrzejewski-Szmek wrote:
>
> Relying on the target distro management stack sound nice, but is
> actually problematic: how do you run the next version before you
> install the next version? Sure, you can install stuff to some temporary
> location and
On Mon, Apr 20, 2020 at 02:40:36PM +0300, Panu Matilainen wrote:
> On 4/20/20 1:07 PM, Zbigniew Jędrzejewski-Szmek wrote:
> >On Mon, Apr 20, 2020 at 10:38:18AM +0300, Panu Matilainen wrote:
> >>On 4/17/20 5:09 PM, Zbigniew Jędrzejewski-Szmek wrote:
> >>>[Service]
> >>>Type=oneshot
>
On 4/20/20 1:07 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Mon, Apr 20, 2020 at 10:38:18AM +0300, Panu Matilainen wrote:
On 4/17/20 5:09 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Fri, Apr 17, 2020 at 04:48:11PM +0300, Panu Matilainen wrote:
On 3/26/20 1:32 PM, Zbigniew Jędrzejewski-Szmek
On Mon, Apr 20, 2020 at 10:38:18AM +0300, Panu Matilainen wrote:
> On 4/17/20 5:09 PM, Zbigniew Jędrzejewski-Szmek wrote:
> >On Fri, Apr 17, 2020 at 04:48:11PM +0300, Panu Matilainen wrote:
> >>On 3/26/20 1:32 PM, Zbigniew Jędrzejewski-Szmek wrote:
> >>>On Thu, Mar 26, 2020 at 01:16:22PM +0200,
On 4/17/20 5:09 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Fri, Apr 17, 2020 at 04:48:11PM +0300, Panu Matilainen wrote:
On 3/26/20 1:32 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Mar 26, 2020 at 01:16:22PM +0200, Panu Matilainen wrote:
Right. I realize %posttrans is not a good idea. But
On Fri, Apr 17, 2020 at 04:48:11PM +0300, Panu Matilainen wrote:
> On 3/26/20 1:32 PM, Zbigniew Jędrzejewski-Szmek wrote:
> >On Thu, Mar 26, 2020 at 01:16:22PM +0200, Panu Matilainen wrote:
> >
> >Right. I realize %posttrans is not a good idea. But *some* mechanism
> >is necessary, because without
On 3/26/20 1:32 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Mar 26, 2020 at 01:16:22PM +0200, Panu Matilainen wrote:
Right. I realize %posttrans is not a good idea. But *some* mechanism
is necessary, because without that the change will mostly be a noop
for most users. So I think this needs
On Tue, Mar 31, 2020 at 02:46:01PM +0300, Panu Matilainen wrote:
>
> The soname doesn't change and no dependencies on any rawhide
> latest-and-greatest otherwise, so from that side there shouldn't be any
> issues.
>
> The only real incompatibility should be on the spec parse side - the bare
>
On Tue, Mar 31, 2020 at 8:53 AM Panu Matilainen wrote:
>
> On 3/31/20 2:46 PM, Panu Matilainen wrote:
> > On 3/30/20 7:45 PM, Kevin Fenzi wrote:
> >> On Mon, Mar 30, 2020 at 12:41:08PM +0300, Panu Matilainen wrote:
> >> ...snip...
> >>>
> >>> No such things needed at this time. The database
On 3/31/20 2:46 PM, Panu Matilainen wrote:
On 3/30/20 7:45 PM, Kevin Fenzi wrote:
On Mon, Mar 30, 2020 at 12:41:08PM +0300, Panu Matilainen wrote:
...snip...
No such things needed at this time. The database change is a separate
change
and does NOT come bundled with RPM 4.16, we'll only even
On 3/30/20 7:45 PM, Kevin Fenzi wrote:
On Mon, Mar 30, 2020 at 12:41:08PM +0300, Panu Matilainen wrote:
...snip...
No such things needed at this time. The database change is a separate change
and does NOT come bundled with RPM 4.16, we'll only even consider switching
that once 4.16 has had a
On Mon, Mar 30, 2020 at 02:40:03PM +0200, Miroslav Suchý wrote:
> Dne 27. 03. 20 v 8:55 Zbigniew Jędrzejewski-Szmek napsal(a):
> > In current "offline upgrade" scheme, the upgrade
> > tools are running on the real system, with udev active.
>
This thread has mostly died, but I didn't want to
On Mon, Mar 30, 2020 at 12:46 PM Kevin Fenzi wrote:
>
> On Mon, Mar 30, 2020 at 12:41:08PM +0300, Panu Matilainen wrote:
> > If it was up to us only, I recon we'd be looking to switch over to sqlite
> > somewhere between 2-4 weeks from the time 4.16 lands in rawhide but our
> > schedule is
On Mon, Mar 30, 2020 at 12:41:08PM +0300, Panu Matilainen wrote:
...snip...
>
> No such things needed at this time. The database change is a separate change
> and does NOT come bundled with RPM 4.16, we'll only even consider switching
> that once 4.16 has had a proper shakedown.
ok, great.
> >
Dne 27. 03. 20 v 8:55 Zbigniew Jędrzejewski-Szmek napsal(a):
> In current "offline upgrade" scheme, the upgrade
> tools are running on the real system, with udev active.
How the "offline upgrade" works under hood? Do I understand correctly that even
"offline ugprade" will have problem with
On 3/28/20 2:01 AM, Kevin Fenzi wrote:
So, my concern here is timeline vs the upcoming datacenter move. ;(
Do you have any ideas when rpm 4.16 will be released? I don't see any
dates on the change. Or perhaps I guess the question is when it will
land in rawhide?
RPM 4.16 alpha was released
On 28. 03. 20 1:01, Kevin Fenzi wrote:
Do you have any ideas when rpm 4.16 will be released? I don't see any
dates on the change. Or perhaps I guess the question is when it will
land in rawhide?
From the ticket https://pagure.io/fesco/issue/2360
My understanding is that 4.16 could be shipped
On Fri, Mar 27, 2020 at 8:01 PM Kevin Fenzi wrote:
>
> So, my concern here is timeline vs the upcoming datacenter move. ;(
>
> Do you have any ideas when rpm 4.16 will be released? I don't see any
> dates on the change. Or perhaps I guess the question is when it will
> land in rawhide?
>
Panu
So, my concern here is timeline vs the upcoming datacenter move. ;(
Do you have any ideas when rpm 4.16 will be released? I don't see any
dates on the change. Or perhaps I guess the question is when it will
land in rawhide?
As soon as it lands in rawhide we need to upgrade the builders to the
On Fri, Mar 27, 2020 at 1:56 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> Where would mock be executing from? The same filesystem it is modifying?
> Somehow it seems that this doesn't change much, but just brings
> in another layer. Or will a complete copy of the system be made in
> memory to
On Fri, Mar 27, 2020 at 09:04:53AM +0200, Panu Matilainen wrote:
> On 3/26/20 2:35 PM, Zbigniew Jędrzejewski-Szmek wrote:
> >On Thu, Mar 26, 2020 at 02:00:49PM +0200, Panu Matilainen wrote:
> >>> previous-release-blocker(s) and previous-previous-release-blockers(s),
> >>> since the changes
On 3/26/20 2:35 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Mar 26, 2020 at 02:00:49PM +0200, Panu Matilainen wrote:
previous-release-blocker(s) and previous-previous-release-blockers(s),
since the changes would need to be deployed in F32 and F31. Also
note that the last time when
On 3/26/20 6:12 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Mar 26, 2020 at 11:41:56AM -0400, Stephen John Smoogen wrote:
On Thu, 26 Mar 2020 at 10:54, Tomasz Torcz wrote:
On Thu, Mar 26, 2020 at 02:08:57PM +, Zbigniew Jędrzejewski-Szmek
wrote:
On Thu, Mar 26, 2020 at 03:29:50PM
On Thu, Mar 26, 2020 at 1:11 PM Panu Matilainen
wrote:
>
> On 3/26/20 4:08 PM, Zbigniew Jędrzejewski-Szmek wrote:
> > On Thu, Mar 26, 2020 at 08:44:47AM -0400, Neal Gompa wrote:
> >> On Thu, Mar 26, 2020 at 8:22 AM Zbigniew Jędrzejewski-Szmek
> >> wrote:
> >>>
> >>> On Thu, Mar 26, 2020 at
On 3/26/20 4:08 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Mar 26, 2020 at 08:44:47AM -0400, Neal Gompa wrote:
On Thu, Mar 26, 2020 at 8:22 AM Zbigniew Jędrzejewski-Szmek
wrote:
On Thu, Mar 26, 2020 at 07:38:33AM -0400, Neal Gompa wrote:
On Thu, Mar 26, 2020 at 7:33 AM Zbigniew
On Thu, Mar 26, 2020 at 11:41:56AM -0400, Stephen John Smoogen wrote:
> On Thu, 26 Mar 2020 at 10:54, Tomasz Torcz wrote:
>
> > On Thu, Mar 26, 2020 at 02:08:57PM +, Zbigniew Jędrzejewski-Szmek
> > wrote:
> > > On Thu, Mar 26, 2020 at 03:29:50PM +0200, Panu Matilainen wrote:
> > > > No, rpm
On Thu, 26 Mar 2020 at 10:54, Tomasz Torcz wrote:
> On Thu, Mar 26, 2020 at 02:08:57PM +, Zbigniew Jędrzejewski-Szmek
> wrote:
> > On Thu, Mar 26, 2020 at 03:29:50PM +0200, Panu Matilainen wrote:
> > > No, rpm doesn't use many Linux-specific calls and this is no
> > > exception. In fact it
On Thu, Mar 26, 2020 at 02:08:57PM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Mar 26, 2020 at 03:29:50PM +0200, Panu Matilainen wrote:
> > No, rpm doesn't use many Linux-specific calls and this is no
> > exception. In fact it doesn't use any of the *at() family calls
> > directly either.
On Thu, Mar 26, 2020 at 08:44:47AM -0400, Neal Gompa wrote:
> On Thu, Mar 26, 2020 at 8:22 AM Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > On Thu, Mar 26, 2020 at 07:38:33AM -0400, Neal Gompa wrote:
> > > On Thu, Mar 26, 2020 at 7:33 AM Zbigniew Jędrzejewski-Szmek
> > > wrote:
> > > >
> > > > -
On 3/26/20 2:20 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Mar 26, 2020 at 07:38:33AM -0400, Neal Gompa wrote:
Since RPM 4.14, RPM creates a new directory, writes the database
content there, then renames the directory when it's done.
Does it use renameat2(RENAME_EXCHANGE)?
No, rpm
On 3/26/20 2:35 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Mar 26, 2020 at 02:00:49PM +0200, Panu Matilainen wrote:
[cutting to the chase]
- a one-shot service: this is easier to implement, it just needs to
happen in one place. The hard part is making sure that the machine
does not
On Thu, Mar 26, 2020 at 8:22 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Thu, Mar 26, 2020 at 07:38:33AM -0400, Neal Gompa wrote:
> > On Thu, Mar 26, 2020 at 7:33 AM Zbigniew Jędrzejewski-Szmek
> > wrote:
> > >
> > > - a one-shot service: this is easier to implement, it just needs to
> > >
On Thu, Mar 26, 2020 at 02:00:49PM +0200, Panu Matilainen wrote:
> >>I left it open on purpose (note the "probably" in there) as there
> >>would be any number of ways to achieve the rebuild with varying
> >>degrees of automation and opt-out opportunities, depending on what
> >>is actually
On Thu, Mar 26, 2020 at 07:38:33AM -0400, Neal Gompa wrote:
> On Thu, Mar 26, 2020 at 7:33 AM Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > On Thu, Mar 26, 2020 at 01:16:22PM +0200, Panu Matilainen wrote:
> > > On 3/26/20 1:02 PM, Zbigniew Jędrzejewski-Szmek wrote:
> > > >On Mon, Mar 16, 2020 at
On 3/26/20 1:32 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Mar 26, 2020 at 01:16:22PM +0200, Panu Matilainen wrote:
On 3/26/20 1:02 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Mon, Mar 16, 2020 at 11:22:47AM -0400, Ben Cotton wrote:
=== Upgrading ===
* Ability to upgrade is not affected
*
On Thu, Mar 26, 2020 at 7:33 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Thu, Mar 26, 2020 at 01:16:22PM +0200, Panu Matilainen wrote:
> > On 3/26/20 1:02 PM, Zbigniew Jędrzejewski-Szmek wrote:
> > >On Mon, Mar 16, 2020 at 11:22:47AM -0400, Ben Cotton wrote:
> > >>=== Upgrading ===
> > >>*
On Thu, Mar 26, 2020 at 01:16:22PM +0200, Panu Matilainen wrote:
> On 3/26/20 1:02 PM, Zbigniew Jędrzejewski-Szmek wrote:
> >On Mon, Mar 16, 2020 at 11:22:47AM -0400, Ben Cotton wrote:
> >>=== Upgrading ===
> >>* Ability to upgrade is not affected
> >>* After upgrade completes, manual action
On 3/26/20 1:02 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Mon, Mar 16, 2020 at 11:22:47AM -0400, Ben Cotton wrote:
=== Upgrading ===
* Ability to upgrade is not affected
* After upgrade completes, manual action (rpmdb --rebuilddb) will
probably be needed to convert to sqlite. Alternatively user
On Mon, Mar 16, 2020 at 11:22:47AM -0400, Ben Cotton wrote:
> === Upgrading ===
> * Ability to upgrade is not affected
> * After upgrade completes, manual action (rpmdb --rebuilddb) will
> probably be needed to convert to sqlite. Alternatively user can change
> configuration to stay on BDB.
Do I
On 3/20/20 9:25 PM, Neal Gompa wrote:
On Tue, Mar 17, 2020 at 6:06 AM Panu Matilainen wrote:
On 3/16/20 6:25 PM, Neal Gompa wrote:
I'm glad to *finally* see this happen, so congratulations to the RPM
team for finally making this a reality! I look forward to trying this
out in Rawhide as
On Tue, Mar 17, 2020 at 6:06 AM Panu Matilainen wrote:
>
> On 3/16/20 6:25 PM, Neal Gompa wrote:
> >
> > I'm glad to *finally* see this happen, so congratulations to the RPM
> > team for finally making this a reality! I look forward to trying this
> > out in Rawhide as soon as possible.
>
> FWIW,
On 3/16/20 6:25 PM, Neal Gompa wrote:
On Mon, Mar 16, 2020 at 11:24 AM Ben Cotton wrote:
https://fedoraproject.org/wiki/Changes/Sqlite_Rpmdb
== Summary ==
Change format of the RPM database from Berkeley DB to a new Sqlite format.
== Owner ==
* Name: [[User:pmatilai| Panu Matilainen]]
On Mon, Mar 16, 2020 at 11:24 AM Ben Cotton wrote:
>
> https://fedoraproject.org/wiki/Changes/Sqlite_Rpmdb
>
> == Summary ==
> Change format of the RPM database from Berkeley DB to a new Sqlite format.
>
> == Owner ==
> * Name: [[User:pmatilai| Panu Matilainen]] [[User:ffesti|Florian Festi]]
> *
https://fedoraproject.org/wiki/Changes/Sqlite_Rpmdb
== Summary ==
Change format of the RPM database from Berkeley DB to a new Sqlite format.
== Owner ==
* Name: [[User:pmatilai| Panu Matilainen]] [[User:ffesti|Florian Festi]]
* Email: pmati...@redhat.com ffe...@redhat.com
== Detailed
https://fedoraproject.org/wiki/Changes/Sqlite_Rpmdb
== Summary ==
Change format of the RPM database from Berkeley DB to a new Sqlite format.
== Owner ==
* Name: [[User:pmatilai| Panu Matilainen]] [[User:ffesti|Florian Festi]]
* Email: pmati...@redhat.com ffe...@redhat.com
== Detailed
50 matches
Mail list logo
