On 2/15/22 02:42, Miro Hrončok wrote:
On 14. 02. 22 18:14, Mamoru TASAKA wrote:
Miro Hrončok wrote on 2022/02/13 22:26:
On 13. 02. 22 13:32, Josef Řídký wrote:
Hi,
first of all, I would like to apologize for the mess I've caused by
the jasper .so name bump in Rawhide. I entirely forgot the s
On 14. 02. 22 18:14, Mamoru TASAKA wrote:
Miro Hrončok wrote on 2022/02/13 22:26:
On 13. 02. 22 13:32, Josef Řídký wrote:
Hi,
first of all, I would like to apologize for the mess I've caused by the
jasper .so name bump in Rawhide. I entirely forgot the side-tag option and
had the old mindset
On Mon, Feb 14, 2022 at 10:32:40AM -0500, Neal Gompa wrote:
> On Mon, Feb 14, 2022 at 3:31 AM Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > On Sun, Feb 13, 2022 at 04:27:36PM -0500, Neal Gompa wrote:
> > > I used to be motivated to write such a bot, but after the rpmautospec
> > > thing, I'm not go
Miro Hrončok wrote on 2022/02/13 22:26:
On 13. 02. 22 13:32, Josef Řídký wrote:
Hi,
first of all, I would like to apologize for the mess I've caused by the jasper .so name
bump in Rawhide. I entirely forgot the side-tag option and had the old mindset of having
rawhide as a "sandbox for new fe
Mamoru TASAKA wrote:
> kdelibs3 also seems to be okay with above, but ppc64le build only failed:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=82799185
> Looking at build.log , it looks like parallel make issue.
Yes, try just resubmitting the build, hopefully it will not hit the race
cond
Your points about why touching dist-git for rebuilds can be problematic are
correct, I think. However, I don’t see an easy way around the fact that a
release bump is required to produce a new build that obsoletes the previous
build, and that interaction with dist-git is required to make this hap
On Mon, Feb 14, 2022 at 3:31 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Sun, Feb 13, 2022 at 04:27:36PM -0500, Neal Gompa wrote:
> > I used to be motivated to write such a bot, but after the rpmautospec
> > thing, I'm not going to bother. I wanted rpmautospec to handle
> > rebuilds without commi
Jos de Kloe wrote on 2022/02/14 15:56:
Hi,
eccodes will need to be adapted upstream. I filed an issue there and they will
try to fix this a.s.a.p. Untill then, if needed, I could remove use of
libjasper since it is an optional feature.
For now, I've pushed:
https://src.fedoraproject.org/rpms
Mamoru TASAKA wrote on 2022/02/14 17:47:
Miro Hrončok wrote on 2022/02/13 22:26:
On 13. 02. 22 13:32, Josef Řídký wrote:
Hi,
first of all, I would like to apologize for the mess I've caused by the jasper .so name
bump in Rawhide. I entirely forgot the side-tag option and had the old mindset o
Thanks, I wasn't aware that fbrnch is so smart.
On Sun, Feb 13, 2022 at 08:09:12PM -, E.N. virgo wrote:
> Here is a proof-of-concept one-liner (split up a bit for readability
> purposes):
>
> ```fish
> #!/usr/bin/fish
>
> function get_dependent_pkgs
> dnf -q repoquery --repo=koji --qf='
Miro Hrončok wrote on 2022/02/13 22:26:
On 13. 02. 22 13:32, Josef Řídký wrote:
Hi,
first of all, I would like to apologize for the mess I've caused by the jasper .so name
bump in Rawhide. I entirely forgot the side-tag option and had the old mindset of having
rawhide as a "sandbox for new fe
On Sun, Feb 13, 2022 at 04:27:36PM -0500, Neal Gompa wrote:
> I used to be motivated to write such a bot, but after the rpmautospec
> thing, I'm not going to bother. I wanted rpmautospec to handle
> rebuilds without commits/changelog bumps, because then we could
> trigger rebuilds more simply (depe
On 2/11/22 21:45, Kevin Kofler via devel wrote:
> Miro Hrončok wrote:
>> It was actually announced:
>>
>>
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/FV53ADNJB5STFN3YAEEXEVHMIA6DMXCN/
>>
>> But for reasons I don't understand, it was pushed to rawhide without
Hi,
eccodes will need to be adapted upstream. I filed an issue there and
they will try to fix this a.s.a.p. Untill then, if needed, I could
remove use of libjasper since it is an optional feature.
grib_api is no longer maintained upstream, so not much can be done there.
Jos.
On 2/13/22 21:5
Kevin Kofler via devel wrote:
> Miro Hrončok wrote:
>> kdelibs
>> kdelibs3
>
> So they both hit this error:
>
> /usr/include/jasper/jas_log.h:122:46: error: expected primary-expression
> before 'int'
> 122 | static inline jas_logtype_t jas_logtype_init(int class, int
> priority)
> |
On 2/13/22 15:29, Kevin Fenzi wrote:
> On Sun, Feb 13, 2022 at 05:46:49PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
>> On Sun, Feb 13, 2022 at 09:43:38AM -0600, Michael Catanzaro wrote:
>>> On Sun, Feb 13 2022 at 02:26:46 PM +0100, Miro Hrončok
>>> wrote:
Considering most of the dependent pac
On 2/13/22 13:40, Miro Hrončok wrote:
On 13. 02. 22 21:19, Orion Poplawski wrote:
On 2/13/22 06:26, Miro Hrončok wrote:
Still in progress:
gdal (already succeeded on some architectures)
Failed twice (13):
LibRaw
OpenSceneGraph
digikam
eccodes
gegl04
grads
grib_api
kdelibs
kdelibs3
ncl
qt5-qtim
On Sun, Feb 13, 2022 at 11:47 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Sun, Feb 13, 2022 at 09:43:38AM -0600, Michael Catanzaro wrote:
> > On Sun, Feb 13 2022 at 02:26:46 PM +0100, Miro Hrončok
> > wrote:
> > > Considering most of the dependent packages failed to rebuild in this
> > > case, I
Miro Hrončok wrote:
> kdelibs
> kdelibs3
So they both hit this error:
/usr/include/jasper/jas_log.h:122:46: error: expected primary-expression before
'int'
122 | static inline jas_logtype_t jas_logtype_init(int class, int priority)
| ^~~
/usr/
On 2/13/22 13:51, devel@lists.fedoraproject.org wrote:
On 2/13/22 13:19, devel@lists.fedoraproject.org wrote:
On 2/13/22 06:26, Miro Hrončok wrote:
Still in progress:
gdal (already succeeded on some architectures)
Failed twice (13):
LibRaw
OpenSceneGraph
digikam
eccodes
gegl04
grads
grib_api
k
On 2/13/22 13:19, devel@lists.fedoraproject.org wrote:
On 2/13/22 06:26, Miro Hrončok wrote:
Still in progress:
gdal (already succeeded on some architectures)
Failed twice (13):
LibRaw
OpenSceneGraph
digikam
eccodes
gegl04
grads
grib_api
kdelibs
kdelibs3
ncl
qt5-qtimageformats
qt6-qtimageformat
On 13. 02. 22 21:40, Miro Hrončok wrote:
On 13. 02. 22 21:19, Orion Poplawski wrote:
On 2/13/22 06:26, Miro Hrončok wrote:
Still in progress:
gdal (already succeeded on some architectures)
Failed twice (13):
LibRaw
OpenSceneGraph
digikam
eccodes
gegl04
grads
grib_api
kdelibs
kdelibs3
ncl
qt5-q
On 13. 02. 22 21:19, Orion Poplawski wrote:
On 2/13/22 06:26, Miro Hrončok wrote:
Still in progress:
gdal (already succeeded on some architectures)
Failed twice (13):
LibRaw
OpenSceneGraph
digikam
eccodes
gegl04
grads
grib_api
kdelibs
kdelibs3
ncl
qt5-qtimageformats
qt6-qtimageformats
wgrib2
I
On Sun, Feb 13, 2022 at 05:46:49PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> On Sun, Feb 13, 2022 at 09:43:38AM -0600, Michael Catanzaro wrote:
> > On Sun, Feb 13 2022 at 02:26:46 PM +0100, Miro Hrončok
> > wrote:
> > > Considering most of the dependent packages failed to rebuild in this
> > > c
I think this will be my last reply on the topic...I think people know my
view and Kevin's here (but if other folks have more questions, happy to answer
them).
On Sat, Feb 12, 2022 at 08:09:34PM +0100, Kevin Kofler via devel wrote:
> Kevin Fenzi wrote:
> > As a release engineer trying to get a rawh
On 2/13/22 06:26, Miro Hrončok wrote:
Still in progress:
gdal (already succeeded on some architectures)
Failed twice (13):
LibRaw
OpenSceneGraph
digikam
eccodes
gegl04
grads
grib_api
kdelibs
kdelibs3
ncl
qt5-qtimageformats
qt6-qtimageformats
wgrib2
If somebody wants to help, build in f37-build-
Here is a proof-of-concept one-liner (split up a bit for readability purposes):
```fish
#!/usr/bin/fish
function get_dependent_pkgs
dnf -q repoquery --repo=koji --qf='%{sourcerpm}' --whatrequires $argv[1]
end
function parse_names
get_dependent_pkgs | rev | cut -d/ -f1 | cut -d- -f3- | re
On Sun, Feb 13, 2022 at 09:43:38AM -0600, Michael Catanzaro wrote:
> On Sun, Feb 13 2022 at 02:26:46 PM +0100, Miro Hrončok
> wrote:
> > Considering most of the dependent packages failed to rebuild in this
> > case, I am
> > not sure how a robot would be supposed to deal with this :(
>
> If the b
On Sun, Feb 13 2022 at 02:26:46 PM +0100, Miro Hrončok
wrote:
Considering most of the dependent packages failed to rebuild in this
case, I am
not sure how a robot would be supposed to deal with this :(
If the bot can handle everything that doesn't require manual
intervention, that's still a
On 13. 02. 22 13:32, Josef Řídký wrote:
Hi,
first of all, I would like to apologize for the mess I've caused by the jasper
.so name bump in Rawhide. I entirely forgot the side-tag option and had the old
mindset of having rawhide as a "sandbox for new features". I wrote to Miro
already as I am
Hi,
first of all, I would like to apologize for the mess I've caused by the
jasper .so name bump in Rawhide. I entirely forgot the side-tag option and
had the old mindset of having rawhide as a "sandbox for new features". I
wrote to Miro already as I am not part of the proven packager group to
ass
Kevin Fenzi wrote:
> As a release engineer trying to get a rawhide compose, I do find this a
> big deal. (Another f37 compose just failed because of this issue).
Well, as I already pointed out more than once, the real issue there is that
the Rawhide compose fails due to a broken dependency. This
On 12. 02. 22 2:42, Miro Hrončok wrote:
I've cc'ed them on all rebuild and received no reply.
*I've cc'ed them on all my emails.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubsc
On 11. 02. 22 21:45, Kevin Kofler via devel wrote:
Miro Hrončok wrote:
It was actually announced:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/FV53ADNJB5STFN3YAEEXEVHMIA6DMXCN/
But for reasons I don't understand, it was pushed to rawhide without using
a
On Fri, Feb 11, 2022 at 09:45:53PM +0100, Kevin Kofler via devel wrote:
> Miro Hrončok wrote:
> > It was actually announced:
> >
> >
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/FV53ADNJB5STFN3YAEEXEVHMIA6DMXCN/
> >
> > But for reasons I don't understand,
Miro Hrončok wrote:
> It was actually announced:
>
>
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/FV53ADNJB5STFN3YAEEXEVHMIA6DMXCN/
>
> But for reasons I don't understand, it was pushed to rawhide without using
> a side tag and without doing rebuilds :(
>
>
Mamoru TASAKA wrote on 2022/02/11 23:41:
Miro Hrončok wrote on 2022/02/11 23:29:
On 11. 02. 22 15:20, Mamoru TASAKA wrote:
Hello, all:
On rawhide (f37) jasper is updated from 2.0.33-2 to 3.0.0-1,
which causes unannounced soname bump from libjasper.so.4 to libjasper.so.6.
What is strange here
./find_unblocked_orphans.py --max_deps 1 --skip-orphans jasper
Depending on: jasper (30),
DevIL (maintained by: jwrdegoede)
DevIL-1.7.8-38.fc36.i686 requires libjasper.so.4
DevIL-1.7.8-38.fc36.src requires jasper-devel = 2.0.33-2.fc36
DevIL-1.7.8-38.fc36.x86_64 requires libjasper.so.4()(64bit)
De
Miro Hrončok wrote on 2022/02/11 23:29:
On 11. 02. 22 15:20, Mamoru TASAKA wrote:
Hello, all:
On rawhide (f37) jasper is updated from 2.0.33-2 to 3.0.0-1,
which causes unannounced soname bump from libjasper.so.4 to libjasper.so.6.
What is strange here is that the committer seems aware of this
On 11. 02. 22 15:20, Mamoru TASAKA wrote:
Hello, all:
On rawhide (f37) jasper is updated from 2.0.33-2 to 3.0.0-1,
which causes unannounced soname bump from libjasper.so.4 to libjasper.so.6.
What is strange here is that the committer seems aware of this change:
https://src.fedoraproject.org/rp
Hello, all:
On rawhide (f37) jasper is updated from 2.0.33-2 to 3.0.0-1,
which causes unannounced soname bump from libjasper.so.4 to libjasper.so.6.
What is strange here is that the committer seems aware of this change:
https://src.fedoraproject.org/rpms/jasper/c/13f23ce40bfeafccd96ecc8872f965e
41 matches
Mail list logo
