| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Thus helping cpan-testers to install the proper packages
We need to include {cflags} even if empty on Linux as it contains
-I/usr/local/include on eg: FreeBSD
|
|
|
|
|
| |
technically restoring rpm-4.13 support needs a small patch
We could even still support rpm-4.12 by ifdef-ing the ELEM callback
|
|
|
|
|
|
|
|
| |
This reverts commit 87dbde4f3b078173e53cd45cac000c2d2751b370.
Rationale: rpm got fixed
We could just initialize header to NULL but rpmReadPackageFile() is
supposed to always set a correct value, so keep as it in order to catch
another future perl regression
|
| |
|
|
|
|
|
| |
This is a rpm-4.14 regression where rpmReadPackageFile() no longer
initialize the header when the pkg is corrupted
|
|
|
|
|
| |
This reverts commit 4cb2fcc5bf443de9f3f05fe085c42a317101321b.
This is no more needed as of rpm-4.14.0-0.rc1.3.mga7
|
| |
|
|
|
|
| |
it's now possible since perl-5.26.0-8.mga7
|
|
|
|
| |
This reverts commit 8aceb9b6a318668d0795af52bf9ea9dbb33351d9.
|
| |
|
| |
|
|
|
|
|
| |
which results in the following on exit cleanup:
'panic: free from wrong pool, 0!=6c7010 during global destruction.'
|
| |
|
| |
|
| |
|
|
|
|
|
| |
else we may got total size to overflow (mga#19686)
v2 by Thierry Vignaud: use native int64 on 64bit
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
rationale:
- {debug_URPM} only exists if we're in debug mode
- as this is an actual error, let's just always report it
bug introduced in commit 070f1be3d5c3aa813f61d061c2a0fd38c2477c08
|
|
|
|
| |
use rpmTagGetValue() to get the char* name of the tag
|
| |
|
|
|
|
|
|
| |
thus enabling to report size of >4Gb packages (however insane this is):
rpmlib uses the old small tag for small packages and the new big tag for
big packages (mga#19571)
|
|
|
|
| |
Thus we use 64bit for package size on 32bit too, thanks to Math::Int64
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for at least 12 years, since swiching rpm to 4.2
(see commit 60031191b7012fdfe8e1af6bd43ff9b36b0c5825)
$trans->check() failed to actually report issues
rationale: rpmtsCheck() only actually return !0 if it fails to open
rpmdb...
in order to check if any problem was found by rpmtsCheck(), one must call
retrieving the problem set with rpmtsProblems()
rpmtsCheck() success only means that the resolution was successfully
attempted for all packages in the set, which isn't that usefull...
this might help mga#15350...
|
| |
|
| |
|
|
|
|
| |
that's no more needed...
|
|
|
|
|
| |
This callback will be fired before each pkg being installed/removed
Needs rpm >= rpm-4.13.0-0.rc1.28
|
| |
|
|
|
|
|
|
|
|
| |
sort by ids (like in other places) when promoting (b/c of eg:
conflicts), thus fixing upgrade when the same package is offered in
several media (mga#15350)
see commit 53e38beae4d9638f41b219521b802a2969d68909 for similar issue
|
| |
|
| |
|
| |
|
|
|
|
| |
thus fixing unknown package name on erases (mga#15032)
|
| |
|
|
|
|
| |
fix a warning spot by Angelo Naselli
|
|
|
|
|
|
| |
this is needed after using POPi
bug introduced in commit 4294365db5d78909ae5a490e0714db379502cd80
|
| |
|
|
|
|
| |
unlike recommends_nosense, it returns version too
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fix by Panu Matilainen
When rpmlog() occurs, it now grabs a read/write lock on the log context
depending on whether it needs to save the log or not. The callback
executes while the context lock is held, so when one call
rpmlogMessage() or pretty much any rpmlog-related function from the
callback, it'll try to lock the context again. Which is okay as long as
rpmlog() only needed a read-lock on the context. However if it has a
write-lock then attempting to grab a read-lock for rpmlogMessage()
fails, but due to the largely missing error handling in rpmlog.c it
falls through to crash and burn.
The only reason we need to call rpmlogMessage() is that the callback
does not match the callback function type in rpm >= 4.6:
typedef int (*rpmlogCallback) (rpmlogRec rec, rpmlogCallbackData data);
We shouldn't call that from log callback.
We can avoid the issue by using rpmlogRecMessage() instead of
rpmlogMessage() inside the callback. These are not the same,
rpmlogRecMessage() returns the message of the *current* log event,
whereas rpmlogMessage() returns the last *saved* log event. Which might
not exist, might be from an earlier event or it might be the current
event.
...and it'll not only work in all rpm >= 4.6 versions, but also give
the actual log message at hand, instead of something that might have
happened in the past.
|
| |
|
|
|
|
| |
Veuillez saisir le message de validation pour vos modifications. Les lignes
|
| |
|