Sites I visit, or should visit, periodically

bgstack15 — Sun, 12 Dec 2021 13:38:11 GMT

I find some random netizens quite amusing. Some, I find informative. Some, I am friends with. Other sites are less personal.

I intend for this to be a living list, so check this page on occasion!

These pages are listed under headings, but those are more like guidelines.

Daily

Weekly

Sporadically

Dedoimedo's blog
Homo Ludditus. This guy's willingness to speak his mind is inspiring! I even agree with some of what he says. I can only read the English parts.

Packaging utilities

OBS
copr

Forums

Some of these are more frequent than others.

Found: OBS service documentation

bgstack15 — Mon, 24 Feb 2020 14:20:04 GMT

For some unknown reason, it is really hard to find good documentation on how to use the _service file for the Open Build Service. The Open Build Service (OBS) is a project from the openSUSE team, and they run a public instance at https://build.opensuse.org/. This server application provides a build environment for many distributions' package methods. I use it for my public Devuan packages (see my "OBS" link in the links section of this site, usually a sidebar on each page). The _service file has some generic documentation in the main obs online man pages. I find this documentation extremely lacking in explaining how to use a service file fully. And I've learned by examples extant on the public OBS instance already. So, just to be clear, a _service file is a file in an obs project, that defines a number of steps for the server to take. By default, each service runs for each commit, or whenever you select the "trigger services" button on the web page for a project. I finally found a list of available service names to use! And the links take you to the projects on the Internet where they live and are fully documented. There are quite a few I plan on using in the future... like regex_replace.

Example _service file

With my service file set up to pull down the source debian/ directory as debian.tar.xz, and the entire source as a tar.gz, and extract out my .dsc file from that source, I can manage my OBS project way easier.

<services>
   <service name="tar_scm">
      <param name="scm">git</param>
      <param name="url">https://gitlab.com/bgstack15/fluxbox-themes-stackrpms.git</param>
      <param name="subdir">debian</param>
      <param name="filename">debian</param>
      <param name="revision">local-dsc-file</param>
      <param name="version">_none_</param>
   </service>
   <service name="recompress">
      <param name="file">*.tar</param>
      <param name="compression">xz</param>
   </service>
   <service name="tar_scm">
      <param name="scm">git</param>
      <param name="url">https://gitlab.com/bgstack15/fluxbox-themes-stackrpms.git</param>
      <param name="revision">local-dsc-file</param>
      <param name="version">_none_</param>
   </service>
   <service name="recompress">
      <param name="file">*.tar</param>
      <param name="compression">gz</param>
   </service>
   <service name="extract_file">
      <param name="archive">*.tar.gz</param>
      <param name="files">*/*.dsc</param>
   </service>
</services>

The .dsc file is modified from the output from a proper debuild -us -uc locally. I learned the trick of zeroing out the checksums from another OBS project, waterfox-classic- kpe.

Format: 3.0 (quilt)
Source: fluxbox-themes-stackrpms
Binary: fluxbox-themes-stackrpms
Architecture: all
Version: 0.0.1-1+devuan
Maintainer: Ben Stack 
Homepage: /posts/
Standards-Version: 4.1.4
Build-Depends: debhelper (>= 12~)
Package-List:
 fluxbox-themes-stackrpms deb x11 optional arch=all
Files:
 00000000000000000000000000000000 1 fluxbox-themes-stackrpms_0.0.1.orig.tar.gz
 00000000000000000000000000000000 1 fluxbox-themes-stackrpms_0.0.1-1+devuan.debian.tar.xz

And since the filenames do not match, I think that section is not even necessary. Thankfully OBS figures out what tarballs to use where for the debuild. To quote my original distro (Korora): "Standing on the shoulders of giants."

Conclusion

I can control my osc package with only one file in the obs source control: the _service file! This reduces the need to pass multiple assets, which can be large.

References

Internet searches

How I actually found the main weblink open build service services recompress

Weblinks

https://en.opensuse.org/openSUSE:Build_Service_Concept_SourceService#All_OBS_services_available

My best practice for html links

bgstack15 — Sat, 20 Jan 2018 14:25:42 GMT

Don't use target="_blank" because that forces only one behavior, opening in a new tab. I should expect the user to open a link in a new tab if he wants to.
Don't omit the referrer, which is done by including rel="noreferrer". I want other sites to know who is linking to them, in the hopes of getting cross-traffic.
Do include rel="noopener" to protect users (reference 1).

Knowledge Base (Posts about links)

Sites I visit, or should visit, periodically

Daily

Weekly

Sporadically

Packaging utilities

Forums

Found: OBS service documentation

Example _service file

Conclusion

References

Internet searches

Weblinks

My best practice for html links

References

Weblinks