Re: [Rpm-maint] [rpm-software-management/rpm] Moving unnecessary notice about empty rpm packages to debug message. (#615)
if the problem is an empty file being queried, why not solve teh problem where the action occurs (before the test), with something simple like: [ -s $ARG ] && ... I don't see that this is the rpm binary's issue -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/615#issuecomment-449471367___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] Make %setup defaults smarter (#371)
> Yes, right. Then you won't have any problem finding hundreds of packages Under the present system, my tooling runs and provides sub-second look-ups on a corpus of (today) 796479 packagings Stop picking a fight -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/371#issuecomment-351754559___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] Make %setup defaults smarter (#371)
No 'quirks' at all ... I have built my tools with the rpm and rpmbuild man pages open, and consulting: rpm --showrc That's how developing in an Unixy (tm) environment works I know what is not a good idea on the Usenet ... ahh, times change so silly me, having been the editor of RPM.ORG during the JBJ maintainer-ship with the almost obsessive attention to preserving backward compatibility, and keeping that documentary content alive out of my own pocket, when RH re-pointed the domain to Seth at Duke, and then pulled it back in house > http://www.oldrpm.org/ silly, in having forgotten your contributions sarcasm probably early onset senility on my part -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/371#issuecomment-351489234___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] Make %setup defaults smarter (#371)
> The probability anyone will create an archive containing a %{name}-%{version}
> topdir while not named %{name}-%{version} is vanishingly smal
My build tools do this 'different %_topdir naming' on ** every ** build
It might make sense to actually use rpmbuild for a decade or so before
proposing changes that break backward compatibility
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/371#issuecomment-351474044___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] WIP/RFE: Hint to users to use ostree/rpm-ostree if we get EROFS (#320)
As I understand the model for rpm-ostree, it assumes a Read Only, and re-located RPMDB Wouldn't a more general fix than the one seemingly already committed about inability to calculate TS disk size requirements, be a simply attempt to connect with the BDB and get a lockfile? this would indicate reliably and early, that RW transactions as called were not going to happen, and once might exit early, and with more information to a admin -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/320#issuecomment-327928478___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] Python macro improvements (#221)
My archive of unpacked .spec file disputes @ignatenkobrain comment above --
backward compatibility matters
[herrold@centos-7 SPECS]$ grep "\%py" *spec | grep -v ":#" | wc
39 1461953
[herrold@centos-7 SPECS]$ grep "\%py" *spec | grep -v ":#"
BitTorrent.spec:%pyrequires_eq python-modules
compat-wxPython.spec:- use %%python_sitelib macro
denyhosts.spec:- Include everything under %%python_sitelib to pick up any
egg-info files that
eric3.spec:%pyrequires_eq python-modules
eric3.spec:%py_comp $RPM_BUILD_ROOT%{py_sitedir}/*
eric3.spec:%py_ocomp $RPM_BUILD_ROOT%{py_sitedir}/*
eric3.spec:- Release 3. STBR for Ac. %pyrequires_eq python-modules -> R:
python-modules. Eric is pure Python app.
gpsd.spec:- Use %%python_sitelib for python site-files stuff.
postgresql.spec:%if %python
postgresql.spec:%if %python
postgresql.spec:Conflicts: python < %pyver, python >= %pynextver
postgresql.spec:%if %python
postgresql.spec:%if %python
postgresql.spec:%if %python
postgresql.spec:%if %python
postgresql.spec:%if %python
postgresql.spec:%if %python
PyKDE-3.7.spec:echo yes | %pythonprog build.py \
PyKDE.spec:- Req: python-abi = %%python_ver
PyQt4.spec:- use %%python_sitearch
PyQt.spec:- Req: python-abi = %%python_ver
PyQt.spec:- use/Require: %%python_sitearch
python-dialog.spec:- Change %%python_sitearch to %%python_sitelib as sitearch
references
python-lazy-object-proxy.spec:%{?python_provide:%python_provide
python2-%{srcname}}
python-lazy-object-proxy.spec:%{?python_provide:%python_provide
python3-%{srcname}}
python-lazy-object-proxy.spec:%py2_build
python-lazy-object-proxy.spec:%py3_build
python-lazy-object-proxy.spec:%py2_install
python-lazy-object-proxy.spec:%py3_install
python-pandas.spec:%py3_build
python-pandas.spec:%py3_install
python-parsimonious.spec:%py2_build
python-parsimonious.spec:%py2_install
python-PyKDE.spec:%pyrequires_eqpython
python-PyKDE.spec:%py_comp $RPM_BUILD_ROOT%{py_sitedir}
python-PyKDE.spec:%py_ocomp $RPM_BUILD_ROOT%{py_sitedir}
python.spec:- add %%python3_version to the rpm macros (rhbz#719082)
python.spec:- add %%py3dir macro to macros.python3 (to be used during unified
python 2/3
rrdtool.spec:- Define %%python_version *before* its needed (#237826)
[herrold@centos-7 SPECS]$
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/221#issuecomment-305812544___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
