[Bug 2120537] New: 'bodhi updates new' does not report error/warning when setting karma limit below minimal value for package in critical path
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2120537
Bug ID: 2120537
Summary: 'bodhi updates new' does not report error/warning when
setting karma limit below minimal value for package in
critical path
Product: Fedora
Version: rawhide
Status: NEW
Component: bodhi-client
Assignee: thrcka(a)redhat.com
Reporter: zdohnal(a)redhat.com
CC: aurelien(a)bompard.org,
epel-packagers-sig(a)lists.fedoraproject.org,
lenka(a)sepu.cz, thrcka(a)redhat.com
Target Milestone: ---
Classification: Fedora
Hi,
I was surprised why my bodhi update (
https://bodhi.fedoraproject.org/updates/FEDORA-2022-6f5e420e52 ) doesn't show
an option for pushing into stable or why the update is not in stable already,
because the positive karma limit (1) is reached.
On #fedora-devel IRC channel kalev answered:
(09:34:34 AM) zdohnal: Hi all, do you have an idea what blocks this update
https://bodhi.fedoraproject.org/updates/FEDORA-2022-6f5e420e52 from being
pushed to the stable?
(09:38:32 AM) kalev: zdohnal: looks like it's marked as critical path and
because of that, it needs minimum of +2 karma to be pushed to stable
(09:40:19 AM) GrannyGoose left the room (quit: Quit: Going offline, see ya!
(www.adiirc.com)).
(09:41:00 AM) zdohnal: kalev: aha - good to know. However bodhi-client should
give me error when I set karma below this limit...
According to the conversation, there is karma limit for components in critical
path and it is higher - 2 - than the limit set by me - 1, which causes
confusion.
I use 'bodhi updates new' CLI command for creating updates, and I didn't see
any error/warning regarding setting the karma limit too low.
IMHO CLI command has to fail if user tries to set the limit too low, and bodhi
web UI should handle this in some way as well.
Would you mind looking into it?
Version-Release number of selected component (if applicable):
bodhi-client-6.0.1-4.fc37
How reproducible:
always
Steps to Reproduce:
1. $ bodhi updates new --type bugfix --close-bugs --request testing --autokarma
--autotime --stable-karma 1 --unstable-karma -1 --notes "Update for component
in critical path" <critical-component-1.2.3-1.fc37>
Actual results:
No error or warning, bodhi web ui shows user defined limit and the update has
karma to fulfill the limit, but the update is not pushed into stable.
Expected results:
Give error (in both interfaces - CLI and Web UI) if user wants to set lower
karma limit than it is required on the package.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2120537
1 week, 3 days
[Bug 2093731] New: zbarimg does not read a Code 128 barcode
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2093731
Bug ID: 2093731
Summary: zbarimg does not read a Code 128 barcode
Product: Fedora
Version: 36
Status: NEW
Component: zbar
Severity: high
Assignee: gwync(a)protonmail.com
Reporter: cristian.ciupitu(a)yahoo.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dougsland(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
gwync(a)protonmail.com, mchehab(a)infradead.org,
mr.marcelo.barbosa(a)gmail.com, negativo17(a)gmail.com
Target Milestone: ---
Classification: Fedora
Created attachment 1886898
--> https://bugzilla.redhat.com/attachment.cgi?id=1886898&action=edit
Code 128 barcode
Description of problem:
zbarimg does not read a Code 128 barcode
Version-Release number of selected component (if applicable):
zbar-0.23.90-1.fc36.x86_64
How reproducible:
Every time
Steps to Reproduce:
1. zbarimg barcode.png
Actual results:
scanned 0 barcode symbols from 1 images in 0 seconds
WARNING: barcode data was not detected in some image(s)
Things to check:
- is the barcode type supported? Currently supported symbologies are:
. EAN/UPC (EAN-13, EAN-8, EAN-2, EAN-5, UPC-A, UPC-E, ISBN-10, ISBN-13)
. DataBar, DataBar Expanded
. Code 128
. Code 93
. Code 39
. Codabar
. Interleaved 2 of 5
. QR code
. SQ code
. PDF 417
- is the barcode large enough in the image?
- is the barcode mostly in focus?
- is there sufficient contrast/illumination?
- If the symbol is split in several barcodes, are they combined in one image?
- Did you enable the barcode type?
some EAN/UPC codes are disabled by default. To enable all, use:
$ zbarimg -S*.enable <files>
Please also notice that some variants take precedence over others.
Due to that, if you want, for example, ISBN-10, you should do:
$ zbarimg -Sisbn10.enable <files>
Expected results:
(Code 128) 755897201062022179.73
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2093731
1 week, 3 days
[Bug 2125635] New: [abrt] zbar-qt: XCreateGC(): zbarcam-qt killed by SIGSEGV
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2125635
Bug ID: 2125635
Summary: [abrt] zbar-qt: XCreateGC(): zbarcam-qt killed by
SIGSEGV
Product: Fedora
Version: 37
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:078632a70931f6bcf0d3a737df94c2bb4c797b8b;VAR
IANT_ID=workstation;
Component: zbar
Assignee: gwync(a)protonmail.com
Reporter: remyabel(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dougsland(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
gwync(a)protonmail.com, mchehab(a)infradead.org,
mr.marcelo.barbosa(a)gmail.com, negativo17(a)gmail.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
zbar-qt-0.23.90-5.fc37
Additional info:
reporter: libreport-2.17.2
backtrace_rating: 3
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-3fe4439d-5e15-4c55-880f-64488f2bf4b7.scope
cmdline: zbarcam-qt
crash_function: XCreateGC
executable: /usr/bin/zbarcam-qt
journald_cursor:
s=759f6b6667fc40deb238abf796413863;i=4906;b=8bb2ff6253eb43b991e38d34d1424771;m=ea673b49;t=5e83e9c99f6b5;x=320ffbe6a9d0ebd3
kernel: 5.19.7-300.fc37.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#0 XCreateGC at /usr/src/debug/libX11-1.8.1-2.fc37.x86_64/src/CrGC.c:74
#1 _zbar_window_attach at window/x.c:168
#2 zbar_window_attach at
/usr/src/debug/zbar-0.23.90-5.fc37.x86_64/zbar/window.c:73
#3 zbar::Window::attach at ./include/zbar/Window.h:75
#4 zbar::QZBar::changeEvent at qt/QZBar.cpp:337
#5 QWidget::event at kernel/qwidget.cpp:8975
#6 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3637
#7 QCoreApplication::notifyInternal2 at kernel/qcoreapplication.cpp:1064
#8 QWidget::setParent at kernel/qwidget.cpp:10505
#10 QLayoutPrivate::reparentChildWidgets at kernel/qlayout.cpp:841
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2125635
5 months, 2 weeks
[Bug 2065645] New: Gmime 3.2.9 is available
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2065645
Bug ID: 2065645
Summary: Gmime 3.2.9 is available
Product: Fedora
Version: rawhide
Hardware: All
Status: NEW
Component: gmime30
Severity: medium
Assignee: klember(a)redhat.com
Reporter: mjg(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
klember(a)redhat.com
Target Milestone: ---
Link ID: Github jstedfast/gmime/releases/tag/3.2.9
Classification: Fedora
Description of problem:
Gmime 3.2.7 as packaged is outdated (Mar 2020).
Version-Release number of selected component (if applicable):
3.2.7-5
How reproducible:
always
Steps to Reproduce:
1. dnf list gmime30
Actual results:
gmime30-3.2.7
Expected results:
gmime30-3.2.9
Additional info:
The real upstream has been at https://github.com/jstedfast/gmime/ for quite
some time now (not on gnome any more, and never on gitlab).
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2065645
5 months, 2 weeks
[Bug 2081494] New: CVE-2022-1292 openssl: c_rehash script allows command injection
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2081494
Bug ID: 2081494
Summary: CVE-2022-1292 openssl: c_rehash script allows command
injection
Product: Security Response
Hardware: All
OS: Linux
Status: NEW
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: pdelbell(a)redhat.com
CC: aos-bugs(a)redhat.com, asoldano(a)redhat.com,
bbaranow(a)redhat.com, bdettelb(a)redhat.com,
berrange(a)redhat.com, bmaxwell(a)redhat.com,
bootloader-eng-team(a)redhat.com,
brian.stansberry(a)redhat.com, caswilli(a)redhat.com,
cdewolf(a)redhat.com, cfergeau(a)redhat.com,
chazlett(a)redhat.com, crobinso(a)redhat.com,
crypto-team(a)lists.fedoraproject.org,
csutherl(a)redhat.com, darran.lofthouse(a)redhat.com,
dbelyavs(a)redhat.com, ddepaula(a)redhat.com,
dhalasz(a)redhat.com, dkreling(a)redhat.com,
dkuc(a)redhat.com, dosoudil(a)redhat.com,
dueno(a)redhat.com, elima(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
erik-fedora(a)vanpienbroek.nl, f4bug(a)amsat.org,
fjansen(a)redhat.com, fjuma(a)redhat.com,
fmartine(a)redhat.com, gparvin(a)redhat.com,
gzaronik(a)redhat.com, iweiss(a)redhat.com,
jburrell(a)redhat.com, jclere(a)redhat.com,
jferlan(a)redhat.com, jkoehler(a)redhat.com,
jochrist(a)redhat.com, jramanat(a)redhat.com,
jwong(a)redhat.com, jwon(a)redhat.com, kaycoth(a)redhat.com,
krathod(a)redhat.com, kraxel(a)redhat.com,
ktietz(a)redhat.com, lgao(a)redhat.com,
marcandre.lureau(a)redhat.com,
michal.skrivanek(a)redhat.com, michel(a)michel-slm.name,
micjohns(a)redhat.com, mjg59(a)srcf.ucam.org,
mosmerov(a)redhat.com, mperina(a)redhat.com,
msochure(a)redhat.com, mspacek(a)redhat.com,
msvehla(a)redhat.com, mturk(a)redhat.com,
njean(a)redhat.com, nwallace(a)redhat.com,
pahickey(a)redhat.com, pbonzini(a)redhat.com,
pjindal(a)redhat.com, pjones(a)redhat.com,
pmackay(a)redhat.com, redhat-bugzilla(a)linuxnetz.de,
rfreiman(a)redhat.com, rharwood(a)redhat.com,
rh-spice-bugs(a)redhat.com, rjones(a)redhat.com,
rstancel(a)redhat.com, rsvoboda(a)redhat.com,
sahana(a)redhat.com, sbonazzo(a)redhat.com,
smaestri(a)redhat.com, stcannon(a)redhat.com,
sthirugn(a)redhat.com, szappis(a)redhat.com,
tmeszaro(a)redhat.com, tm(a)t8m.info,
tom.jenkinson(a)redhat.com,
virt-maint(a)lists.fedoraproject.org,
virt-maint(a)redhat.com, vkrizan(a)redhat.com,
vkumar(a)redhat.com, vmugicag(a)redhat.com
Target Milestone: ---
Classification: Other
The c_rehash script does not properly sanitise shell metacharacters to
prevent command injection. This script is distributed by some operating
systems in a manner where it is automatically executed. On such operating
systems, an attacker could execute arbitrary commands with the privileges
of the script.
Use of the c_rehash script is considered obsolete and should be replaced
by the OpenSSL rehash command line tool.
This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0.
OpenSSL 1.0.2 users should upgrade to 1.0.2ze
OpenSSL 1.1.1 users should upgrade to 1.1.1o
OpenSSL 3.0 users should upgrade to 3.0.3
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2081494
6 months, 1 week