stackrpms - Rpm and dpkg build recipes for my custom packages

	Commit message (Collapse)	Author	Age
*	palemoon 28.4.1 dpkg	B Stack	2019-03-29
\|
*	WIP: remove unneeded directories for binary package	B Stack	2019-03-28
\| \| \| \| \|	The dpkg cleans up /usr/share/idl, /usr/lib/palemoon-devel, and /usr/include, and the rpm will try that too.
*	suppress binary stripping on el6	B Stack	2019-03-28
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The official release does not suffer from this, but for some reason the stackrpms release of palemoon fails the binary stripping at the end with messages similar to: + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip /usr/bin/strip + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip BFD: /builddir/build/BUILDROOT/palemoon-stackrpms-28.4.1-1.x86_64/usr/lib64/palemoon-stackrpms-devel/sdk/lib/libxpcomglue.a(PLDHashTable.o): invalid relocation type 42 /usr/bin/strip: PLDHashTable.o: Bad value BFD: /builddir/build/BUILDROOT/palemoon-stackrpms-28.4.1-1.x86_64/usr/lib64/palemoon-stackrpms-devel/sdk/lib/libxpcomglue_s.a(Unified_cpp_xpcom_glue0.o): invalid relocation type 42 /usr/bin/strip: Unified_cpp_xpcom_glue0.o: Bad value BFD: /builddir/build/BUILDROOT/palemoon-stackrpms-28.4.1-1.x86_64/usr/lib64/palemoon-stackrpms-devel/sdk/lib/libmozglue.a(SSE.o): invalid relocation type 42 /usr/bin/strip: SSE.o: Bad value BFD: /builddir/build/BUILDROOT/palemoon-stackrpms-28.4.1-1.x86_64/usr/lib64/palemoon-stackrpms-devel/sdk/lib/libmemory.a(jemalloc_config.o): invalid relocation type 42 /usr/bin/strip: jemalloc_config.o: Bad value BFD: /builddir/build/BUILDROOT/palemoon-stackrpms-28.4.1-1.x86_64/usr/lib64/palemoon-stackrpms-devel/sdk/lib/libunicharutil_external_s.a(chariter.o): invalid relocation type 42 /usr/bin/strip: chariter.o: Bad value BFD: /builddir/build/BUILDROOT/palemoon-stackrpms-28.4.1-1.x86_64/usr/lib64/palemoon-stackrpms-devel/sdk/lib/libcrmf.a(crmfenc.o): invalid relocation type 42 /usr/bin/strip: crmfenc.o: Bad value error: Bad exit status from /var/tmp/rpm-tmp.pudIld (%install)
*	palemoon 28.4.1 rpm rc1	B Stack	2019-03-27
\| \| \| \|	fixes #3 palemoon customization
*	Merge branch 'libdvdcss-dpkg' into 'master'	B Stack	2019-03-20
\|\ \| \| \| \| \| \| \| \| \| \| \| \|	libdvdcss 1.4.2 dpkg rc1 Because I don't like the libdvd-pkg and the interactivity required. The upstream package is very clever and slick, truly. I just want to do an unattended installation, as well as bundle my own addition. See merge request bgstack15/stackrpms!48
\| *	libdvdcss 1.4.2 dpkg rc1	B Stack	2019-03-13
\|/
*	Merge branch 'makemkv-dpkg' into 'master'	B Stack	2019-03-13
\|\ \| \| \| \| \| \| \| \|	Makemkv dpkg See merge request bgstack15/stackrpms!47
\| *	add more lines to conf example	B Stack	2019-03-09
\| \|
\| *	makemkv-oss fix arch problem for config	B Stack	2019-03-02
\| \|
\| *	makemkv 1.14.2	B Stack	2019-03-02
\| \|
* \|	Merge branch 'freefilesync-bump' into 'master'	B Stack	2019-03-13
\|\ \ \| \| \| \| \| \| \| \| \| \| \| \|	Freefilesync 10.10 See merge request bgstack15/stackrpms!46
\| * \|	Freefilesync 10.10	B Stack	2019-03-13
\|/ /
* \|	Merge branch 'move-dpkg' into 'master'	B Stack	2019-03-06
\|\ \ \| \|/ \|/\| \| \| \| \|	dpkg for move-to-next-monitor See merge request bgstack15/stackrpms!45
\| *	dpkg for move-to-next-monitor	B Stack	2019-03-01
\|/
*	Merge branch 'irfanview-dpkg' into 'master'	B Stack	2019-02-27
\|\ \| \| \| \| \| \| \| \|	irfanview split into 32 and 64 bit dpkgs See merge request bgstack15/stackrpms!44
\| *	irfanview split into 32 and 64 bit dpkgs	B Stack	2019-02-26
\| \|
* \|	Merge branch 'freefilesync-dpkg' into 'master'	B Stack	2019-02-27
\|\ \ \| \|/ \|/\| \| \| \| \| \| \| \| \|	freefilesync remove need for desktop-file-install Closes #2 See merge request bgstack15/stackrpms!43
\| *	freefilesync remove need for desktop-file-install	B Stack	2019-02-25
\|/
*	Merge branch 'mdf2iso' into 'master'	B Stack	2019-02-25
\|\ \| \| \| \| \| \| \| \|	add mdf2iso See merge request bgstack15/stackrpms!42
\| *	add mdf2iso	B Stack	2019-02-25
\|/
*	Merge branch 'irfanview-dpkg' into 'master'	B Stack	2019-02-21
\|\ \| \| \| \| \| \| \| \|	irfanview dpkg See merge request bgstack15/stackrpms!41
\| *	irfanview dpkg	B Stack	2019-02-21
\|/
*	Merge branch 'palemoon-bump' into 'master'	B Stack	2019-02-21
\|\ \| \| \| \| \| \| \| \|	palemoon 28.4.0 dpkg See merge request bgstack15/stackrpms!40
\| *	palemoon 28.4.0 dpkg	B Stack	2019-02-21
\|/
*	Merge branch 'palemoon-custom' into 'master'	B Stack	2019-02-19
\|\ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Multiple palemoon builds Split palemoon into official package, and my custom -stackrpms package. Also split palemoon-ublock-origin in same way. Update palemoon to 28.4.0. See merge request bgstack15/stackrpms!39
\| *	split pm-ublock into two dirs	B Stack	2019-02-19
\| \|
\| *	rename pm-stack-ublock spec	B Stack	2019-02-19
\| \|
\| *	pm-stack-ublock	B Stack	2019-02-19
\| \|
\| *	pm ublock origin 1.16.4.8	B Stack	2019-02-19
\| \|
\| *	pm-ublock dpkg for devuan	B Stack	2019-02-19
\| \|
\| *	pm 28.4.0	B Stack	2019-02-19
\| \|
\| *	WIP: pm custom rpm for prefs	B Stack	2019-02-15
\| \|
\| *	split palemoon spec into normal and custom	B Stack	2019-02-14
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The actual spec files are the same except the stackrpms_custom variable. The logic is the same in each one for consistency. If stackrpms_custom is set, it will add my custom patches and prefs.js file. Otherwise, build the officially-endorsed build for Fedora.
\| *	palemoon spec use _libdir for prefs.js	B Stack	2019-02-06
\| \|
\| *	rpm spec mkdir for prefs.js	B Stack	2019-02-06
\| \|
\| *	palemoon dpkg fix version number	B Stack	2019-02-05
\| \|
\| *	palemoon custom part 2	B Stack	2019-02-05
\| \|
\| *	add bgstack15 customizations to rpm spec part 1	B Stack	2019-02-05
\| \|
\| *	palemoon dpkg with customizations	B Stack	2019-02-04
\| \| \| \| \| \| \| \| \| \|	Experimentation with dpkg that bundles in my prefs.js on system level as well as no search bar by default (which is a source patch).
* \|	Merge branch 'freefilesync-c7' into 'master'	B Stack	2019-02-19
\|\ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	FreeFileSync 10.9-2 for CentOS7 and Fedora 28-30 This is the successful release candidate for FreeFileSync on CentOS7 and Fedora 28-30 from the same spec file. On CentOS 7, the package build and install dependencies include libcurl 7.64.0, libssh2 1.8.0, openssl 1.1.0 (openssl-freefilesync), which are available in the [bgstack15/FreeFileSync](https://copr.fedorainfracloud.org/coprs/bgstack15/FreeFileSync) copr. See merge request bgstack15/stackrpms!38
\| * \|	FreeFileSync 10.9-2 for CentOS 7 and Fedora 28-30	B Stack	2019-02-19
\| \| \|
\| * \|	fix %fi to %endif	B Stack	2019-02-19
\| \| \|
\| * \|	WIP: remove the use of %dist to include patches	B Stack	2019-02-19
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	I finally realized that copr builds the srpm in a fedora environment and then uses that srpm everywhere, including the epel-6 and epel-7 chroots, where the el7.patch file was now absent. So now the spec depends on both ffs_fedora.patch and ffs_el.patch
\| * \|	fix distro patch files	B Stack	2019-02-19
\| \| \|
\| * \|	fix typo in Patch2 about %dist	B Stack	2019-02-19
\| \| \|
\| * \|	WIP: fix fc28 libcurl problem and el7 %dist	B Stack	2019-02-19
\| \| \|
\| * \|	WIP freefilesync: add requires: libcurl and libssh	B Stack	2019-02-18
\| \| \|
\| * \|	WIP: fix typo of Build in buildreqs	B Stack	2019-02-18
\| \| \|
\| * \|	WIP: ffs for el7 and fc28 from one spec	B Stack	2019-02-18
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The el7 version depends on the copr bgstack15/FreeFileSync and the fc28 version should be the same as before, but will need to actually be tested.
\| * \|	WIP: FreeFileSync on CentOS 7, part 1	B Stack	2019-02-18
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	In my original dev environment, I can now compile and execute the main binaries. My next commit should include some attempts at static linking so the runtime environment does not need the hacked openssl 1.1.0h packages.