| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
rationale: we don't set any private data with rpmlogSetCallback()
|
|
|
|
|
|
| |
by reverting a bit of commit b0cd1853933d8c68610c9e173721525c6a17e8ce
that should have gone with along:
commit b5249dafb882fbc105f05853c80fd30503d57a3f
|
|
|
|
|
|
|
| |
This message was never displayed:
see commit 66dd07d4237c6ee773c48c4c5a1471fdc25f8828
And anyway urpmi already takes care of warning about import errors
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
previously it was missing on 32bit arches
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
filename"
This reverts commit a4b836dfe43cf1a498e93094d54d498a55142fef.
|
|
|
|
|
| |
RPMPROB_OBSOLETE was added in rpm-4.9.0 (5 years ago) but wasn't handled
until now
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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...
|
| |
|
| |
|
| |
|
|
|
|
| |
(need latest perl_checker)
|
|
|
|
| |
(need latest perl_checker)
|
| |
|
|
|
|
| |
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.
|
| |
|
| |
|