Le mar. 22 juin 2021 à 14:37, Panu Matilainen a
écrit :
>
> More or less in planned schedule for a change, here goes 4.17.0 beta1.
> We're not actually planning for a second beta, the 1 is there just in
> case because there are some unusual changes between alpha and beta:
>
>* Debuginfo
Le lun. 26 avr. 2021 à 11:34, Panu Matilainen a
écrit :
>
> The beginning of this year has gone nothing like planned, and
> consequently we had to postpone and even revert some things originally
> planned for 4.17. But what the hey, there's plenty of good stuff here as
> it is, and there will
Le mar. 15 sept. 2020 à 12:51, Thierry Vignaud
a écrit :
> Le mar. 15 sept. 2020 à 12:40, Thierry Vignaud
> a écrit :
>
>> Not sure if it's related to 4.16.0 but for some time, when looking at
>>> some (successful) builds, I see several objcopy error messages duri
Le mar. 15 sept. 2020 à 12:40, Thierry Vignaud
a écrit :
> Not sure if it's related to 4.16.0 but for some time, when looking at some
>> (successful) builds, I see several objcopy error messages during late build
>> stages.
>> eg:
>> objcopy: unable to copy file
&g
Le mar. 15 sept. 2020 à 12:25, Thierry Vignaud
a écrit :
> Le lun. 31 août 2020 à 11:30, Panu Matilainen a
> écrit :
>
>>
>> Very little has changed since beta3, there are a handful of bugfixes
>> across the board to various older issues but no regressions wer
Le lun. 31 août 2020 à 11:30, Panu Matilainen a
écrit :
>
> Very little has changed since beta3, there are a handful of bugfixes
> across the board to various older issues but no regressions were found
> in beta3 so none of the sort fixed either.
>
> Barring any unexpected disasters, this should
Le mer. 24 juin 2020 à 10:47, Panu Matilainen a écrit :
>
>
> This fixes multiple dependency generator related regressions introduced
> beta2, by reverting the "fail build on dependency generator failure"
> change introduced there.
>
> We don't usually release new tarballs just because an issue
Le mar. 23 juin 2020 à 14:41, Panu Matilainen a
écrit :
>
> Some fairly important fixes cropped up in the last few weeks so we
> decided to go with a second beta for a change. The highlights since
> beta1 include:
>
> - fix hardlink breakage on upgrade when minimize_writes is enabled
> - fix
Le mer. 24 juin 2020 à 11:02, Thierry Vignaud a
écrit :
>
>> This fixes multiple dependency generator related regressions introduced
>>> beta2, by reverting the "fail build on dependency generator failure"
>>> change introduced there.
>>>
>>
Le mer. 24 juin 2020 à 10:59, Thierry Vignaud a
écrit :
>
> This fixes multiple dependency generator related regressions introduced
>> beta2, by reverting the "fail build on dependency generator failure"
>> change introduced there.
>>
>> We don't u
Le mer. 24 juin 2020 à 10:47, Panu Matilainen a
écrit :
>
> This fixes multiple dependency generator related regressions introduced
> beta2, by reverting the "fail build on dependency generator failure"
> change introduced there.
>
> We don't usually release new tarballs just because an issue
Le mar. 23 juin 2020 à 14:41, Panu Matilainen a
écrit :
>
> Some fairly important fixes cropped up in the last few weeks so we
> decided to go with a second beta for a change. The highlights since
> beta1 include:
>
> - fix hardlink breakage on upgrade when minimize_writes is enabled
> - fix
Le ven. 29 mai 2020 à 09:57, Panu Matilainen a écrit :
>
> The gap between alpha and beta was longer than usual because we were
> waiting for bug reports for the new sqlite backend from wider exposure
> in Fedora. After two months, we figured we can't wait forever. Zero
> filed bugs is almost
Le lun. 23 mars 2020 à 15:47, Panu Matilainen a
écrit :
>
> On 3/23/20 3:22 PM, Panu Matilainen wrote:
> >
> > So soon you say? Well, its almost a year since 4.15 alpha and annual
> > release schedule isn't *that* fast. More like trying to get back on
> > track with this release stuff after some
Le mar. 7 avr. 2020 à 12:08, Thierry Vignaud a
écrit :
> > So soon you say? Well, its almost a year since 4.15 alpha and annual
>
>> > release schedule isn't *that* fast. More like trying to get back on
>> > track with this release stuff after some erratic years.
Le lun. 23 mars 2020 à 15:47, Panu Matilainen a
écrit :
>
> On 3/23/20 3:22 PM, Panu Matilainen wrote:
> >
> > So soon you say? Well, its almost a year since 4.15 alpha and annual
> > release schedule isn't *that* fast. More like trying to get back on
> > track with this release stuff after some
2001
From: Thierry Vignaud
Date: Mon, 23 Dec 2019 16:51:49 +0100
Subject: [PATCH] fix zstd magic
I spot it while adding support for zstd compressed metadata in
URPM/urpmi, which was broken by this typo
typo introduced in commit 3684424fe297c996bb05bb64631336fa2903df12
---
rpmio/rpmfileutil.c | 2
Le sam. 31 août 2019 à 13:00, Thierry Vignaud a
écrit :
> A wee bit late from the original schedule but at least in the same month
>
>> still, here comes the first and hopefully last release candidate for
>> 4.15.0.
>>
>> The main highlights since beta are:
>&g
Le mer. 28 août 2019 à 12:28, Panu Matilainen a
écrit :
> A wee bit late from the original schedule but at least in the same month
> still, here comes the first and hopefully last release candidate for
> 4.15.0.
>
> The main highlights since beta are:
> - Fixed out of order build output
> -
ping?
Le lun. 10 sept. 2018 à 08:16, Thierry Vignaud
a écrit :
>
> Hi
> This patch documents the %__NAME_namespace added in 2011 on the website.
> See you
___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/
Le mer. 12 sept. 2018 à 19:15, Neal Gompa a écrit :
> > >> In Mageia, we eg had:
> > >> 1) manual "requires(post)" or "requires(posttrans): info-install"
> > >> (info-install being the package containing /sbin/ /sbin/install-info
> > >> 2) plus manual %post or %posttrans calling install-info
Le mer. 12 sept. 2018 à 14:30, Igor Gnatenko
a écrit :
>> In Mageia, we eg had:
>> 1) manual "requires(post)" or "requires(posttrans): info-install"
>> (info-install being the package containing /sbin/ /sbin/install-info
>> 2) plus manual %post or %posttrans calling install-info
>>
>> This
really is "requires(posttrans): info-install"
The patch enables to emit requires for scriptlets or filetriggers.
See you
Le mer. 12 sept. 2018 à 10:34, Igor Gnatenko
a écrit :
>
> What is the point of this? I just don't get the use-case..
>
> On Wed, Sep 12, 2018 at 10:3
Le sam. 8 sept. 2018 à 09:10, Thierry Vignaud
a écrit :
>
> Hi
>
> The attached patch adds support for scriptlet deps in generated deps.
> Eg on Mageia, there's a file trigger for automatically
> installing/removing info pages from /usr/share/info index
>
> Having
Hi
This patch documents the %__NAME_namespace added in 2011 on the website.
See you
From 87a129401c77dfe21e1da480459c3c199f606da7 Mon Sep 17 00:00:00 2001
From: Thierry Vignaud
Date: Mon, 10 Sep 2018 08:07:17 +0200
Subject: [PATCH] document %__NAME_namespace added in 2011
---
user_doc
mageia/info-file.req
%__info_scriptlet posttrans
%__info_path^%{_datadir}/info/.*\\.info.*$
See you
From c70b34df68cedc93c2a77fd92ceed3e78cc06651 Mon Sep 17 00:00:00 2001
From: Thierry Vignaud
Date: Sat, 8 Sep 2018 08:30:45 +0200
Subject: [PATCH] add support for scriptlet deps in generated de
Hi
The attached patch adds -C/O aliases for --conflicts/obsoletes
Mirroring the -P/R aliases we've for provides/requires
Thx
From b5cb6a1526e07e4eb8eb943c41fba5536ae25521 Mon Sep 17 00:00:00 2001
From: Thierry Vignaud
Date: Thu, 14 Jun 2018 00:43:25 +0200
Subject: [PATCH] add -C/O aliases
Hi
The attached patch adds support for --whatobsoletes
Mirroring the other --what* options, it's useful when debugging some
upgrade issues.
Tested on rpm-4.14.1, cherry-picked on top of master.
Thx
From f0ee48f525772b032eba92c7d6707e2482d9520a Mon Sep 17 00:00:00 2001
From: Thierry Vignaud
Date
On 8 November 2017 at 10:27, Panu Matilainen wrote:
> In worst-case scenarios (packages with lots of binaries but little
> else), the build-id entries can dominate the query output to the
> point its hard to see the actual content. Marking these things as
> %artifact entries
On 12 October 2017 at 11:22, Panu Matilainen wrote:
>
> In short, RPM 4.14.0 is out now. It's not quite what we originally had in
> mind - some things we planned for didn't make it, but perhaps more
> importantly, it's actually a whole lot MORE than we ever could've
>
On 5 October 2017 at 13:27, Thierry Vignaud <thierry.vign...@gmail.com> wrote:
>>>>>>>>> Yeah, I'm getting segfaults all the way to rpm 4.11.x, didn't test
>>>>>>>>> earlier because this already shows it's not a regression in 4.14.
On 5 October 2017 at 12:03, Panu Matilainen wrote:
Yeah, I'm getting segfaults all the way to rpm 4.11.x, didn't test
earlier because this already shows it's not a regression in 4.14.x
but
something else. A bug in perl-RPM4 perhaps, as
On 5 October 2017 at 11:40, Panu Matilainen wrote:
>> Yeah, I'm getting segfaults all the way to rpm 4.11.x, didn't test
>> earlier because this already shows it's not a regression in 4.14.x but
>> something else. A bug in perl-RPM4 perhaps, as compiling it with
On 5 October 2017 at 10:15, Panu Matilainen wrote:
Yeah, I'm getting segfaults all the way to rpm 4.11.x, didn't test
earlier because this already shows it's not a regression in 4.14.x but
something else. A bug in perl-RPM4 perhaps, as compiling it with -Og
On 4 October 2017 at 17:59, Thierry Vignaud <thierry.vign...@gmail.com> wrote:
>>>>>>>>> The urpmi issue is when checking bogus pkgs.
>>>>>>>>> The RPM4 issue is when traversing the transaction (not the rpmdb)
>>>>>>>
On 4 October 2017 at 14:17, Thierry Vignaud <thierry.vign...@gmail.com> wrote:
>>>>>>>>> Also this new rpm introduced segfault regressions in both RPM4 &
>>>>>>>>> urpmi
>>>>>>>>> testsuites
>>>&g
On 4 October 2017 at 13:26, Panu Matilainen wrote:
Also this new rpm introduced segfault regressions in both RPM4 &
urpmi
testsuites
See attached gdb traces in BUG*.txt
valgrind seems to hint about invalid writes/reads
See
On 3 October 2017 at 09:12, Panu Matilainen wrote:
>> Also this new rpm introduced segfault regressions in both RPM4 & urpmi
>> testsuites
>> See attached gdb traces in BUG*.txt
>> valgrind seems to hint about invalid writes/reads
>> See you
>
>
On 4 October 2017 at 09:41, Panu Matilainen wrote:
> Also this new rpm introduced segfault regressions in both RPM4 & urpmi
> testsuites
> See attached gdb traces in BUG*.txt
> valgrind seems to hint about invalid writes/reads
> See you
On 3 October 2017 at 07:34, Panu Matilainen wrote:
>>> Also this new rpm introduced segfault regressions in both RPM4 & urpmi
>>> testsuites
>>> See attached gdb traces in BUG*.txt
>>> valgrind seems to hint about invalid writes/reads
>>> See you
>>
>>
>> The urpmi issue is
On 3 October 2017 at 09:23, Panu Matilainen <pmati...@redhat.com> wrote:
> On 10/02/2017 11:54 PM, Thierry Vignaud wrote:
>>
>> On 2 October 2017 at 15:08, Panu Matilainen <pmati...@redhat.com> wrote:
>>>>>>
>>>>>> perl-RPM4's testsui
On 3 October 2017 at 08:00, Thierry Vignaud <thierry.vign...@gmail.com> wrote:
> On 3 October 2017 at 07:34, Panu Matilainen <pmati...@redhat.com> wrote:
>>>> Also this new rpm introduced segfault regressions in both RPM4 & urpmi
>>>> testsuit
On 3 October 2017 at 07:34, Panu Matilainen wrote:
>>> Also this new rpm introduced segfault regressions in both RPM4 & urpmi
>>> testsuites
>>> See attached gdb traces in BUG*.txt
>>> valgrind seems to hint about invalid writes/reads
>>> See you
>>
>>
>> The urpmi issue is
On 2 October 2017 at 23:06, Thierry Vignaud <thierry.vign...@gmail.com> wrote:
> Also this new rpm introduced segfault regressions in both RPM4 & urpmi
> testsuites
> See attached gdb traces in BUG*.txt
> valgrind seems to hint about invalid writes/reads
> See you
The urp
On 28 September 2017 at 16:06, Panu Matilainen wrote:
> There aren't that many changes since rc1, but enough to warrant a second
> release candidate instead of going for final. The important ones being:
>
> - Fix a bug of file triggers failing on some packages (MgBug:18797,
On 2 October 2017 at 15:50, Thierry Vignaud <thierry.vign...@gmail.com> wrote:
>>>> It's probably this:
>>>>
>>>> https://github.com/rpm-software-management/rpm/commit/816c7cf3fdae5c45de02a42a2245549778e2ca80
>>>>
>>>> If s
On 2 October 2017 at 15:04, Panu Matilainen wrote:
>>> It's probably this:
>>>
>>> https://github.com/rpm-software-management/rpm/commit/816c7cf3fdae5c45de02a42a2245549778e2ca80
>>>
>>> If so, the following in the spec should work around it:
>>> %undefine
On 2 October 2017 at 12:05, Panu Matilainen wrote:
>> It looks like some dep generators are no more run:
>> We've one dep generator carried by another pkg (so unchanged).
>> But since we upgrade to 4.14, those deps are no more run:
>>
>> $ cat
On 2 October 2017 at 12:34, Panu Matilainen <pmati...@redhat.com> wrote:
> On 10/02/2017 12:20 PM, Thierry Vignaud wrote:
>>
>> On 28 September 2017 at 16:06, Panu Matilainen <pmati...@redhat.com>
>> wrote:
>>>
>>>
>>> There aren't
On 28 September 2017 at 16:06, Panu Matilainen wrote:
>
> There aren't that many changes since rc1, but enough to warrant a second
> release candidate instead of going for final. The important ones being:
>
> - Fix a bug of file triggers failing on some packages (MgBug:18797,
On 28 September 2017 at 16:06, Panu Matilainen wrote:
>
> There aren't that many changes since rc1, but enough to warrant a second
> release candidate instead of going for final. The important ones being:
>
> - Fix a bug of file triggers failing on some packages (MgBug:18797,
On 4 March 2017 at 10:28, Panu Matilainen wrote:
>> From: Mark Wielaard
>>
>> debugedit --base to --dest rewriting of debug source file paths only
>> supported dest paths that were smaller or equal than the base path
>> (and the size should differ more
Hi
All of http://rpm.org/api/* content has disappeared
eg old links such as http://rpm.org/api/4.4.2.2/ldebug_8h.html result
in 404 not found
Also books, eg: http://rpm.org/max-rpm/index.html
Could you restore the doc contents?
___
Rpm-maint mailing
On 21 October 2016 at 11:33, Panu Matilainen wrote:
>>> Ah, I did run the test-suite but not from the created tarball. One more
>>> thing to remember when cutting releases. Or rather *cough* to document
>>> *cough*.
>>>
>>> Applied (with a slightly expanded comments).
>>
>>
html &
> http://lists.rpm.org/pipermail/rpm-maint/2016-October/004604.html
>
> P.S. We'll try to figure out what to do with rpm.org and its content in the
> next few months, and things might be a bit muddy before they get better. Try
> to bear with us.
>
> P.P.S. It's
On 19 October 2016 at 12:35, Panu Matilainen wrote:
>>> Anyway, the list above is not set in stone, otherwise there'd be little
>>> point in posting it here. If you think something absolutely critical is
>>> missing from that list, or that something should not be there,
On 14 October 2016 at 15:33, Panu Matilainen wrote:
> Time to get rpm 4.13.0 out of the door. But in order to do that, we'll need
> to cut -rc2 first, there's just too much change to jump right into final.
>
> The idea is to get -rc2 out next week (ie by Oct 21st at
On 17 October 2016 at 11:42, Panu Matilainen <pmati...@laiskiainen.org> wrote:
> On 10/17/2016 12:30 PM, Thierry Vignaud wrote:
>>
>> On 17 October 2016 at 10:10, Panu Matilainen <pmati...@laiskiainen.org>
>> wrote:
>>>>
>>>> What is the
On 17 October 2016 at 12:06, Vít Ondruch <vondr...@redhat.com> wrote:
> Dne 17.10.2016 v 11:30 Thierry Vignaud napsal(a):
>> On 17 October 2016 at 10:10, Panu Matilainen <pmati...@laiskiainen.org>
>> wrote:
>>>> What is the chance to get [1, 2] into the rel
On 14 October 2016 at 15:33, Panu Matilainen wrote:
> Time to get rpm 4.13.0 out of the door. But in order to do that, we'll need
> to cut -rc2 first, there's just too much change to jump right into final.
>
> The idea is to get -rc2 out next week (ie by Oct 21st at
On 23 September 2016 at 08:44, Panu Matilainen wrote:
> Also generally it's preferred to avoid magic numbers when it can be easily
> expressed with defined names, (S_IXUSR|S_IXGRP|S_IXOTH) is easier for the
> reader than 0111.
That actually depends on the reader :-)
On 6 June 2016 at 23:00, Mark Wielaard wrote:
> Some old tools might still use the .gnu_debuglink section to find
> separate debuginfo files instead of build-id style lookups. When
> dwz has compresses the .debug files the original CRC in the main
> ELF file will no longer match.
On 6 June 2016 at 23:00, Mark Wielaard wrote:
> Support for dwz compression has been in Fedora since a couple of years.
> https://fedoraproject.org/wiki/Features/DwarfCompressor
And in some other distros as well (eg: Mageia).
So if this this lands upstream, we'll be happy too
On 11 May 2016 at 22:35, Thierry Vignaud <thierry.vign...@gmail.com> wrote:
>> This patch modifies rpmSign to include file signatures in the header.
>> Since the header is altered, the package digest and package+archive
>> digest need to be recalculated and updated
On 9 January 2016 at 02:56, Thierry Vignaud <thierry.vign...@gmail.com> wrote:
> On 6 January 2016 at 12:42, Thierry Vignaud <thierry.vign...@gmail.com> wrote:
>> Sadly, the current filetriggers doesn't honour rpm's chroot.
>> Thus it works fine with our rpm front-end (
On 6 January 2016 at 12:42, Thierry Vignaud <thierry.vign...@gmail.com> wrote:
> Sadly, the current filetriggers doesn't honour rpm's chroot.
> Thus it works fine with our rpm front-end (urpmi which is like yum/dns
> for FC) for online updates.
>
> But not with our installer (
On 21 November 2015 at 17:50, Neal Gompa (ニール・ゴンパ) wrote:
> Per the recommendation of Nick Coghlan and Toshio Kuratomi, pythonXegg(M)
> is being renamed to pythonX.Ydist(M).
>
I disagree.
This deps script is widely used
by one rpm.org user for years: Mageia Linux.
Hi
We've some spec files that fail to build under some locales, when %doc
is used with glob
See eg:
%build
touch author AUTHORS Ch cha
(...)
%files
%doc [A-Z]*
Which results in:
LANG=fr LC_COLLATE=fr LC_ALL=fr rpmbuild -ba SPECS/null.spec
(...)
error: Installed (but unpackaged) file(s) found:
On 18 September 2015 at 11:50, Dimitri John Ledkov
wrote:
> So this %autopatch thing is a bit useless to me at the moment,
> specifically because of the requirement to have patches in
> rpmbuild/SOURCES/.
Uh?
Patches can be anywhere.
They're found where %patch is
Hi
The attached patch fixes %autopatch (& thus %autosetup too) when a
patch doesn't actually exist.
Indeed, unlike Mageia's %apply_patches which inspired it, %autopatch
continues instead of exiting when it fails to apply a patch because it
doesn't exists. Eg:
+ /usr/bin/cat
Hi
I see that you've merged pythoneggs generator in rpm.org:
http://rpm.org/gitweb?p=rpm.git;a=log;h=ce15157774833c81f9610693b1473556f8cd
I would suggests merging Mageia's one instead:
http://gitweb.mageia.org/software/rpm/rpm-setup/plain/pythoneggs.attr
Hi
This patch prevents bytecompiling python scripts in docdir (which is useless)
See you
0001-do-not-bytecompile-python-scripts-in-docdir.patch
Description: Binary data
___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
On 28 August 2015 at 14:30, Thierry Vignaud thierry.vign...@gmail.com wrote:
Objectives of this patch is to speed up the compression in rpmbuild. To
achieve this, the patch implements support for a new compressor, functioning
as an interface against external (multi-threaded) compressors
Hi
This old patch from TurboLinux makes rpm treat Transmeta Crusoe as i686:
Crusoe CPUs say that their CPU family is 5 but they have enough
features for i686.
See you
0006-Transmeta-Crusoe-is-i686.patch
Description: Binary data
___
Rpm-maint mailing
Hi
This patchs makes rpm skip plain, regular comments when computing perl deps
See you
0003-skip-plain-regular-comments.patch
Description: Binary data
___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
Hi
This patchs makes rpm ignores perl provides from non module perl files
rationale:
Don't search perl files for provides if they don't end with .pm (because
if they don't, the perl interpreter won't look them up in @INC)
See you
0002-ignore-non-module-perl-files-for-provides-if.patch
On 28 August 2015 at 13:42, fredrik fred...@skri.net wrote:
Objectives of this patch is to speed up the compression in rpmbuild. To
achieve this, the patch implements support for a new compressor, functioning
as an interface against external (multi-threaded) compressors. The main
issue with
On 25 August 2015 at 13:11, Thierry Vignaud thierry.vign...@gmail.com wrote:
The problem is when you upgrade distro N to N+2 both triggers should
be run but only one was run, which was confusing so we disallowed
triggers fired by the same package with overlapping version intervals
On 4 August 2015 at 15:43, Lubos Kardos lkar...@redhat.com wrote:
The problem is when you upgrade distro N to N+2 both triggers should
be run but only one was run, which was confusing so we disallowed
triggers fired by the same package with overlapping version intervals.
And initscripts = 4.72
On 25 August 2015 at 13:41, Thierry Vignaud thierry.vign...@gmail.com wrote:
The problem is when you upgrade distro N to N+2 both triggers should
be run but only one was run, which was confusing so we disallowed
triggers fired by the same package with overlapping version intervals
On 17 August 2015 at 09:22, Lubos Kardos lkar...@redhat.com wrote:
Hi,
the best way how to contribute to translations is to modify strings in rpm
project on www.transifex.com. We pull our translations from there. In future
we plan to remove translations from git completely and just pull them
On 9 August 2015 at 21:34, Olav Vitters o...@vitters.nl wrote:
import rpm._rpmb
ImportError: /usr/lib64/python3.4/site-packages/rpm/_rpmb.cpython-34m.so:
undefined symbol: PyString_FromString
The attached patch fixes it.
Lubos, can you commit this?
Thanks
Hi
Could you apply those translations updates?
Thanks
0003-typo-fix.patch
Description: Binary data
0013-unfuzzy.patch
Description: Binary data
___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
On 4 August 2015 at 20:53, Thierry Vignaud thierry.vign...@gmail.com wrote:
The problem is when you upgrade distro N to N+2 both triggers should
be run but only one was run, which was confusing so we disallowed
triggers fired by the same package with overlapping version intervals
On 24 July 2015 at 13:48, Florian Festi ffe...@redhat.com wrote:
Time to wrap things up and stabilize all that changes to a new release.
There are two big new features that we hope to get feedback on:
* Boolean (aka Rich) Dependencies
* File triggers
Beside that there are many other
On 17 September 2014 09:35, Panu Matilainen pmati...@laiskiainen.org wrote:
The attached patch drops the drop rtld(GNU_HASH) hack
The patch does much more than drop a couple of lines:
$ diffstat no-rtld_GNU_HASH_req.diff
lib/tagexts.c | 54
On 17 September 2014 10:39, Panu Matilainen pmati...@laiskiainen.org wrote:
Mageia just switched to internal deps generator (at least).
In the process, I unforked as most scripts as possible.
Here's some old fixes:
skip-plain-regular-comments.diff:
just skip plain, regular perl comments...
next rebuild.
See you
commit 12d6f89719c06e05ca186ade116608f7ba60c8ae
Author: Thierry Vignaud thierry.vign...@gmail.com
Date: Tue Sep 16 14:52:06 2014 +0200
drop rtld(GNU_HASH) hack
Drop automatically generated rtld(GNU_HASH) dependencies.
It's been provided by glibc for 7 years
Author: Thierry Vignaud thierry.vign...@gmail.com
Date: Tue Sep 16 15:00:23 2014 +0200
drop interpreter deps when already handled
Drop automatically generated dependencies on interpreters we either
don't need dependencies on or that we have other dedicated dependency
Hi
Mageia just switched to internal deps generator (at least).
In the process, I unforked as most scripts as possible.
Here's some old fixes:
skip-plain-regular-comments.diff:
just skip plain, regular perl comments...
support-for-_-in-perl-module-version.diff:
support for _ in perl module
Hi
We've recently switched to internal deps generator.
However one of the deps scripts we use [1] is very slow b/c of this[2]:
+for path in \
+$(for tlpath in \
+$(find ${RPM_BUILD_ROOT}/usr/lib64 ${RPM_BUILD_ROOT}/usr/lib
/usr/lib64 /usr/lib -name '*.typelib'); do
+dirname
On 27 August 2014 08:44, Panu Matilainen pmati...@redhat.com wrote:
As usual, the full details download info are at
http://rpm.org/wiki/Releases/4.12.0
Hi
It looks like the following requires is no more emitted:
rpmlib(PayloadIsXz) = 5.2-1
Note that I care much but is that intended?
On 9 September 2014 12:07, Panu Matilainen pmati...@laiskiainen.org wrote:
It looks like the following requires is no more emitted:
rpmlib(PayloadIsXz) = 5.2-1
Note that I care much but is that intended?
Sigh, that'd be yet another regression from the dependency refactoring
between alpha
On 5 September 2014 14:56, Panu Matilainen pmati...@redhat.com wrote:
This is a bugfix maintenance release to the 4.11.x series for an
assortment of issues. Download information and further details are
available at
http://rpm.org/wiki/Releases/4.11.2
Argh. That's what you get from
On 27 August 2014 08:44, Panu Matilainen pmati...@redhat.com wrote:
The beta turned out to be a bit of a disaster with several new regressions
introduced, and then fixes to those regressions actually causing different
As usual, the full details download info are at
On 27 August 2014 12:06, Panu Matilainen pmati...@laiskiainen.org wrote:
That change went into rpm 4.10 already, http://rpm.org/wiki/Releases/4.10.0
mentions:
* %pretrans scriptlet failure now fails the install of the package
(similarly to %pre and %preun semantics)
The %pretrans change in
On 26 August 2014 11:47, Panu Matilainen pmati...@laiskiainen.org wrote:
Right... changing the error handling in Fclose() closer to what it was
previously fixes this thing:
Thanks, I'll test.
Could you add a test to rpm's testsuite BTW?
However AFAICS the original is broken for a different
On 18 August 2014 10:44, Panu Matilainen pmati...@redhat.com wrote:
As usual, the full details download info are at
http://rpm.org/wiki/Releases/4.12.0
The attached program shows a regression that is affecting URPM.
Now Fclose() returns -2 in the same code path where rpm-4.11.x returned
On 30 June 2014 15:52, Ales Kozumplik akozu...@redhat.com wrote:
Hello people,
this is about [1], i.e. the fact that DNF currently doesn't support an
upgrade path where a package is split into several new packages. It would be
better suited for yum-devel but I'm posting it here since Michael
On 18 August 2013 17:19, Kamil Rytarowski n...@gmx.com wrote:
There are two main implementations of basename() in the GNU system, one is
libgen.h and one from string.h (being accessible here as _GNU_SOURCE).
Currently we do not support systems other than with GNU Lib C (except
possible
1 - 100 of 121 matches
Mail list logo