#lintian — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #lintian, aggregated by home.social.
-
@domm: Oh fsck, #mst died? Very sad to hear. 😢 I still remember that he offered help and advise when I took over #Lintian, especially about the web backend (which the previous Lintian maintainer started to rewrite from scratch but never finished) where mst seems to have been involved from the #PostgreSQL side. He was also often present in #Debian's #Perl IRC channels and we chatted occasionally, not always about Perl. I think I also met him IRL once, but I'm no more sure where.
-
@domm: Oh fsck, #mst died? Very sad to hear. 😢 I still remember that he offered help and advise when I took over #Lintian, especially about the web backend (which the previous Lintian maintainer started to rewrite from scratch but never finished) where mst seems to have been involved from the #PostgreSQL side. He was also often present in #Debian's #Perl IRC channels and we chatted occasionally, not always about Perl. I think I also met him IRL once, but I'm no more sure where.
-
@domm: Oh fsck, #mst died? Very sad to hear. 😢 I still remember that he offered help and advise when I took over #Lintian, especially about the web backend (which the previous Lintian maintainer started to rewrite from scratch but never finished) where mst seems to have been involved from the #PostgreSQL side. He was also often present in #Debian's #Perl IRC channels and we chatted occasionally, not always about Perl. I think I also met him IRL once, but I'm no more sure where.
-
@domm: Oh fsck, #mst died? Very sad to hear. 😢 I still remember that he offered help and advise when I took over #Lintian, especially about the web backend (which the previous Lintian maintainer started to rewrite from scratch but never finished) where mst seems to have been involved from the #PostgreSQL side. He was also often present in #Debian's #Perl IRC channels and we chatted occasionally, not always about Perl. I think I also met him IRL once, but I'm no more sure where.
-
@domm: Oh fsck, #mst died? Very sad to hear. 😢 I still remember that he offered help and advise when I took over #Lintian, especially about the web backend (which the previous Lintian maintainer started to rewrite from scratch but never finished) where mst seems to have been involved from the #PostgreSQL side. He was also often present in #Debian's #Perl IRC channels and we chatted occasionally, not always about Perl. I think I also met him IRL once, but I'm no more sure where.
-
An interesting #inxi moment: #Unit193, #Debian inxi packager, told me that #lintian tests had found a typo in the man page. I have no idea how something can go through a code marked up text file containing data and code samples, and determine what is and what is not a typo, yet there it did it, and it was right, a typo. It was however wrong to give an alert to the path /usr/etc or /usr/local/etc which is now, unfortunately, yet another standard. No idea why /etc/[app].d/[app].conf not enough.
-
An interesting #inxi moment: #Unit193, #Debian inxi packager, told me that #lintian tests had found a typo in the man page. I have no idea how something can go through a code marked up text file containing data and code samples, and determine what is and what is not a typo, yet there it did it, and it was right, a typo. It was however wrong to give an alert to the path /usr/etc or /usr/local/etc which is now, unfortunately, yet another standard. No idea why /etc/[app].d/[app].conf not enough.
-
An interesting #inxi moment: #Unit193, #Debian inxi packager, told me that #lintian tests had found a typo in the man page. I have no idea how something can go through a code marked up text file containing data and code samples, and determine what is and what is not a typo, yet there it did it, and it was right, a typo. It was however wrong to give an alert to the path /usr/etc or /usr/local/etc which is now, unfortunately, yet another standard. No idea why /etc/[app].d/[app].conf not enough.
-
-
-
-
-
-
-
-
-
@bololacertus @profoundlynerdy @fuzzix The fact that:
• https://manpages.debian.org/devscripts/checkbashisms.1.en.html exists
• is written in #Perl
• and is used by the #Debian #Linux project (as part of #Lintian) to automatically reject any packages that assume every #shell acts like #bash
…tells me all I need to know about the supportability of shell scripts -
@bololacertus @profoundlynerdy @fuzzix The fact that:
• https://manpages.debian.org/devscripts/checkbashisms.1.en.html exists
• is written in #Perl
• and is used by the #Debian #Linux project (as part of #Lintian) to automatically reject any packages that assume every #shell acts like #bash
…tells me all I need to know about the supportability of shell scripts -
@bololacertus @profoundlynerdy @fuzzix The fact that:
• https://manpages.debian.org/devscripts/checkbashisms.1.en.html exists
• is written in #Perl
• and is used by the #Debian #Linux project (as part of #Lintian) to automatically reject any packages that assume every #shell acts like #bash
…tells me all I need to know about the supportability of shell scripts -
@bololacertus @profoundlynerdy @fuzzix The fact that:
• https://manpages.debian.org/devscripts/checkbashisms.1.en.html exists
• is written in #Perl
• and is used by the #Debian #Linux project (as part of #Lintian) to automatically reject any packages that assume every #shell acts like #bash
…tells me all I need to know about the supportability of shell scripts -
@bololacertus @profoundlynerdy @fuzzix The fact that:
• https://manpages.debian.org/devscripts/checkbashisms.1.en.html exists
• is written in #Perl
• and is used by the #Debian #Linux project (as part of #Lintian) to automatically reject any packages that assume every #shell acts like #bash
…tells me all I need to know about the supportability of shell scripts -
The right mug for working on #Debian's #Lintian — which is written in #Perl.
And yes, I was on the #YAPCE in Munich 2002. It actually was my first Perl conference at all and I just realized that as of now this was over 20 years ago.
And sad that the Perl conferences are no more called #YAPC (or YAPCE if in Europe), but #TPC instead — which is unpronounceable and always reminds me of "Transports Publics du Chablais". (TPG, Transports Publics Genevois, is probably more well-known. 😉)
-
The right mug for working on #Debian's #Lintian — which is written in #Perl.
And yes, I was on the #YAPCE in Munich 2002. It actually was my first Perl conference at all and I just realized that as of now this was over 20 years ago.
And sad that the Perl conferences are no more called #YAPC (or YAPCE if in Europe), but #TPC instead — which is unpronounceable and always reminds me of "Transports Publics du Chablais". (TPG, Transports Publics Genevois, is probably more well-known. 😉)
-
The right mug for working on #Debian's #Lintian — which is written in #Perl.
And yes, I was on the #YAPCE in Munich 2002. It actually was my first Perl conference at all and I just realized that as of now this was over 20 years ago.
And sad that the Perl conferences are no more called #YAPC (or YAPCE if in Europe), but #TPC instead — which is unpronounceable and always reminds me of "Transports Publics du Chablais". (TPG, Transports Publics Genevois, is probably more well-known. 😉)
-
The right mug for working on #Debian's #Lintian — which is written in #Perl.
And yes, I was on the #YAPCE in Munich 2002. It actually was my first Perl conference at all and I just realized that as of now this was over 20 years ago.
And sad that the Perl conferences are no more called #YAPC (or YAPCE if in Europe), but #TPC instead — which is unpronounceable and always reminds me of "Transports Publics du Chablais". (TPG, Transports Publics Genevois, is probably more well-known. 😉)
-
The right mug for working on #Debian's #Lintian — which is written in #Perl.
And yes, I was on the #YAPCE in Munich 2002. It actually was my first Perl conference at all and I just realized that as of now this was over 20 years ago.
And sad that the Perl conferences are no more called #YAPC (or YAPCE if in Europe), but #TPC instead — which is unpronounceable and always reminds me of "Transports Publics du Chablais". (TPG, Transports Publics Genevois, is probably more well-known. 😉)
-
Finally! #Lintian's test suite passes #autopkgtest again on all architectures since Lintian version 2.116.1 — which I've released and uploaded to #Debian Unstable 1.5 days ago! https://qa.debian.org/excuses.php?package=lintian
-
Finally! #Lintian's test suite passes #autopkgtest again on all architectures since Lintian version 2.116.1 — which I've released and uploaded to #Debian Unstable 1.5 days ago! https://qa.debian.org/excuses.php?package=lintian
-
Finally! #Lintian's test suite passes #autopkgtest again on all architectures since Lintian version 2.116.1 — which I've released and uploaded to #Debian Unstable 1.5 days ago! https://qa.debian.org/excuses.php?package=lintian
-
Finally! #Lintian's test suite passes #autopkgtest again on all architectures since Lintian version 2.116.1 — which I've released and uploaded to #Debian Unstable 1.5 days ago! https://qa.debian.org/excuses.php?package=lintian
-
Finally! #Lintian's test suite passes #autopkgtest again on all architectures since Lintian version 2.116.1 — which I've released and uploaded to #Debian Unstable 1.5 days ago! https://qa.debian.org/excuses.php?package=lintian
-
@zhenech well, yes, I do have #shellcheck wired in a bunch of builds, just not for all packages I'm touching today, from multiple machines, not all of them having proper editors/hooks/confs deployed. That's why I'm enjoying #lintian as the last line of defense before wasting time. 🙃
-
@zhenech well, yes, I do have #shellcheck wired in a bunch of builds, just not for all packages I'm touching today, from multiple machines, not all of them having proper editors/hooks/confs deployed. That's why I'm enjoying #lintian as the last line of defense before wasting time. 🙃
-
@zhenech well, yes, I do have #shellcheck wired in a bunch of builds, just not for all packages I'm touching today, from multiple machines, not all of them having proper editors/hooks/confs deployed. That's why I'm enjoying #lintian as the last line of defense before wasting time. 🙃
-
@zhenech well, yes, I do have #shellcheck wired in a bunch of builds, just not for all packages I'm touching today, from multiple machines, not all of them having proper editors/hooks/confs deployed. That's why I'm enjoying #lintian as the last line of defense before wasting time. 🙃
-
@zhenech well, yes, I do have #shellcheck wired in a bunch of builds, just not for all packages I'm touching today, from multiple machines, not all of them having proper editors/hooks/confs deployed. That's why I'm enjoying #lintian as the last line of defense before wasting time. 🙃
-
I must reckon that I like #lintian very much sometimes: caught at least two instances of stupid shell syntax errors in various scripts, before I threw those udebs into debian-installer then debian-cd builds. ❤️
-
I must reckon that I like #lintian very much sometimes: caught at least two instances of stupid shell syntax errors in various scripts, before I threw those udebs into debian-installer then debian-cd builds. ❤️
-
I must reckon that I like #lintian very much sometimes: caught at least two instances of stupid shell syntax errors in various scripts, before I threw those udebs into debian-installer then debian-cd builds. ❤️
-
I must reckon that I like #lintian very much sometimes: caught at least two instances of stupid shell syntax errors in various scripts, before I threw those udebs into debian-installer then debian-cd builds. ❤️
-
I must reckon that I like #lintian very much sometimes: caught at least two instances of stupid shell syntax errors in various scripts, before I threw those udebs into debian-installer then debian-cd builds. ❤️