Created attachment 408564 [details] package history * Package: net-dialup/martian-modem-20100123-r1 * Repository: gentoo * Maintainer: rogerx.oss@gmail.com pacho@gentoo.org,proxy-maint@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU * FEATURES: preserve-libs sandbox userpriv usersandbox * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/4.1.3-gentoo/build * Found sources for kernel version: * 4.1.3-gentoo * Checking for suitable kernel configuration options... [ ok ] >>> Unpacking source... >>> Unpacking martian-full-20100123.tar.gz to /var/tmp/portage/net-dialup/martian-modem-20100123-r1/work >>> Source unpacked in /var/tmp/portage/net-dialup/martian-modem-20100123-r1/work >>> Preparing source in /var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123 ... * Applying martian-modem-20100123-makefile.patch ... [ ok ] * Applying martian-modem-20100123-linux-3.8.patch ... [ ok ] * Applying martian-modem-20100123-linux-3.10.patch ... [ ok ] >>> Source prepared. >>> Configuring source in /var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123 ... ln: failed to create symbolic link ‘Module.symvers’: File exists * Preparing martian_dev module make -j1 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' KERNEL_DIR=/usr/src/linux SUBLEVEL=3 all make -C kmodule/ modules make[1]: Entering directory '/var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123/kmodule' make -C /usr/src/linux M="/var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123/kmodule" modules make[2]: Entering directory '/usr/src/linux-4.1.3-gentoo' CC [M] /var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123/kmodule/martian.o /var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123/kmodule/martian.c: In function ‘martian_isr’: /var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123/kmodule/martian.c:135:27: warning: value computed is not used [-Wunused-value] process_stream (mdev) && (rd7 &= ~4); ^ /var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123/kmodule/martian.c: In function ‘martian_add’: /var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123/kmodule/martian.c:726:17: error: ‘IRQF_DISABLED’ undeclared (first use in this function) IRQF_SHARED | IRQF_DISABLED, ^ /var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123/kmodule/martian.c:726:17: note: each undeclared identifier is reported only once for each function it appears in scripts/Makefile.build:258: recipe for target '/var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123/kmodule/martian.o' failed make[3]: *** [/var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123/kmodule/martian.o] Error 1 Makefile:1383: recipe for target '_module_/var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123/kmodule' failed make[2]: *** [_module_/var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123/kmodule] Error 2 make[2]: Leaving directory '/usr/src/linux-4.1.3-gentoo' Makefile:20: recipe for target 'modules' failed make[1]: *** [modules] Error 2 make[1]: Leaving directory '/var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123/kmodule' Makefile:9: recipe for target 'all' failed make: *** [all] Error 2 * ERROR: net-dialup/martian-modem-20100123-r1::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=net-dialup/martian-modem-20100123-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=net-dialup/martian-modem-20100123-r1::gentoo'`. * The complete build log is located at '/var/log/portage/net-dialup:martian-modem-20100123-r1:20150808-190017.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/net-dialup/martian-modem-20100123-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-dialup/martian-modem-20100123-r1/temp/environment'. * Working directory: '/var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123' * S: '/var/tmp/portage/net-dialup/martian-modem-20100123-r1/work/martian-full-20100123' ----------------------------------------------------------------- This is an unstable amd64 chroot image (named amd64-desktop-unstable_20150802-115040) at a hardened host acting as a tinderbox. Portage 2.2.20 (python 3.4.3-final-0, default/linux/amd64/13.0/desktop, gcc-4.9.3, glibc-2.21-r1, 4.0.8-hardened x86_64) ================================================================= System uname: Linux-4.0.8-hardened-x86_64-Intel-R-_Core-TM-_i7-3770_CPU_@_3.40GHz-with-gentoo-2.2 KiB Mem: 16164692 total, 5485304 free KiB Swap: 0 total, 0 free Timestamp of repository gentoo: Sat, 08 Aug 2015 17:45:01 +0000 sh bash 4.3_p39 ld GNU ld (Gentoo 2.25.1 p1.0) 2.25.1 ccache version 3.2.2 [disabled] app-shells/bash: 4.3_p39::gentoo dev-java/java-config: 2.2.0::gentoo dev-lang/perl: 5.22.0::gentoo dev-lang/python: 2.7.10::gentoo, 3.4.3::gentoo dev-util/ccache: 3.2.2::gentoo sys-apps/baselayout: 2.2::gentoo sys-apps/openrc: 0.17::gentoo sys-apps/sandbox: 2.6-r1::gentoo sys-devel/autoconf: 2.13::gentoo, 2.69-r1::gentoo sys-devel/automake: 1.9.6-r4::gentoo, 1.10.3-r1::gentoo, 1.11.6-r1::gentoo, 1.12.6::gentoo, 1.13.4::gentoo, 1.14.1::gentoo, 1.15::gentoo sys-devel/binutils: 2.25.1::gentoo sys-devel/gcc: 4.2.4-r1::gentoo, 4.8.4::gentoo, 4.9.3::gentoo sys-devel/gcc-config: 1.8::gentoo sys-devel/libtool: 2.4.6-r1::gentoo sys-devel/make: 4.1-r1::gentoo sys-kernel/linux-headers: 4.1::gentoo (virtual/os-headers) sys-libs/glibc: 2.21-r1::gentoo Repositories: local location: /usr/local/portage masters: gentoo gentoo location: /usr/portage sync-type: rsync sync-uri: rsync://rsync.gentoo.org/gentoo-portage priority: 9999 ACCEPT_KEYWORDS="amd64 ~amd64" ACCEPT_LICENSE="*" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=native -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /etc/stunnel/stunnel.conf /usr/share/config /var/spool/torque /var/yp/Makefile" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo" CXXFLAGS="-O2 -pipe" DISTDIR="/var/tmp/distfiles" EMERGE_DEFAULT_OPTS="--nospinner --tree --quiet-build --accept-properties=-interactive --accept-restrict=-fetch" FCFLAGS="-O2 -pipe" FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync network-sandbox news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync" FFLAGS="-O2 -pipe" GENTOO_MIRRORS="http://ftp.uni-erlangen.de/pub/mirrors/gentoo rsync://mirror.netcologne.de/gentoo/ ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gor.bytemark.co.uk/gentoo/ rsync://ftp.snt.utwente.nl/gentoo" LANG="en_US.utf8" LDFLAGS="-Wl,-O1 -Wl,--as-needed" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" USE="X a52 aac acl acpi alsa amd64 apache2 berkdb bluetooth branding bzip2 cairo cdda cdr clang cli consolekit corefonts cracklib crypt cups curl custom-cflags cxx dbus dot dri dts dvd dvdr ecc elp emboss encode exif fam ffmpeg firefox flac fontconfig fortran fpm freetds gd gdbm gif glamor gnome-keyring gpm gtk gudev h hpn iconv inifile ipv6 jadetex jpeg kde kvm lcms ldap libnotify logrotate mad mbox minizip mmx mmxext mng modules mp3 mp4 mpeg multilib mysql mysqli ncurses nls nptl obj odbc offensive ogg opengl openmp pam pango pax_kernel pcre pdf pdo png policykit postgres ppds pwquality qemu qml qt3support qt4 qt5 readline sdl session sockets spell sqlite3 sse sse2 sse4 sse4_1 ssl ssse3 startup-notification svg system-jpeg system-sqlite tcl tcpd tiff tk truetype udev udisks unicode upower usb vorbis wxwidgets x264 xa xcb xml xmp xscreensaver xv xvid xvmc zenmap zlib" ABI_X86="64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="aes avx mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ublox ubx" INPU T_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LINGUAS="en en_GB" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-5" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_4" RUBY_TARGETS="ruby19 ruby20" USERLAND="GNU" VIDEO_CARDS="fbdev glint intel mach64 mga nouveau nv r128 radeon savage sis tdfx trident vesa via vmware dummy v4l" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CPPFLAGS, CTARGET, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON
The following is the critical error: /kmodule/martian.c:726:17: error: ‘IRQF_DISABLED’ undeclared (first use in this function) IRQF_SHARED | IRQF_DISABLED, I do not get this using "<=sys-kernel/gentoo-sources-4.0.5" I suspect this is a restriction when using hardened kernel sources. Obviously, "Shared IRQ" seems to be something with kernel ACPI drivers? Searching Google for "IRQF_DISABLED undeclared" does show some results for using "+#include <linux/interrupt.h>", and also ensuring omitting any possible parental IFDEF's from including this interrupt.h file during compile. You'll have to search (or grep) the martian build yourself and scan/read some of the code to see if you can fix. Then you need to verify the fix does not break anything. If the above is a workaround or other similar, you could likely avert any possible unknown (or known) breakage by including something within the ebuild to check for users using hardened sources, and then include your patch only when users have hardened sources. This will omit possibly breaking users using other kernels without having this bug. My background: 1) I do not use hardened sources. 2) I have this package installed, and only routinely build against sys-kernel/gentoo-sources, ensuring trivial bugs are fixed. 3) I have no dial-up services to test against, and only buggy hardware on a laptop. (My other ISA modems are not CONUS with my currently location.) Hope this helps!
To also put you at ease, I'm routinely compiling on a " Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz" 64 bit architecture as well. I also get some of those other warnings as well, and they all appear harmless in my opinion. Warnings listed below: ln: failed to create symbolic link 'Module.symvers': File exists marsio.c:358:11: warning: 'mars_read_register_rem' defined but not used [-Wunused-function] marsio.c:371:13: warning: 'mars_write_register_rem' defined but not used [-Wunused-function] martian.c:135:27: warning: value computed is not used [-Wunused-value]
Well, I'm not fully convinced that it is a hardened issue - b/c the chroot image itself is an amd64-desktop-unstable and I do not found anything in the host syslog in pax.log and grsec.log. Hhm - any chance that this is 4.1.3-gentoo kernel related ?
=sys-kernel/gentoo-sources-4.1.3 is masked by keywords. I have little time to unmask, configure, compile, and test the kernel against a compile of martian-modem against the masked kernel version. It's quite frequent kernel versions are never marked stable. Since I schedule my time on a need basis, I don't see this as currently a need basis. But I'll duly note this as a possible pending issue. This bug maybe very likely related to 4.1.3. I would imagine you (yourself) already have a previous stable kernel version configured and compiled? It could also be an upstream kernel bug. Please continue noting anything you find relevant for possibly fixing within the near future.
builds fine with linux-4.0.8-gentoo
So somewhere between linux-4.0.8 and linux-4.1.3 this bug occurs. From the looks of it after searching Google, seeing we need to define a IRQF_DISABLED if kernel version is >=4.1.0 OR MAYBE kernel version is <4.1.0. ie. https://www.virtualbox.org/ticket/14081 http://cvs.rpmfusion.org/viewvc/rpms/catalyst-kmod/devel/kernel_4.1-remove-IRQF_DISABLED.patch?revision=1.1&root=nonfree&view=markup There really isn't much explanation on the Internet forums, aside from people just pushing patches around and saying this fixes it. Digging around within the Linux kernel I can see a commit in 2011 which apparently added the following IRQF_DISABLED definition. Line 67 of linux-4.0.5-gentoo/include/linux/interrupt.h #define IRQF_DISABLED 0x00000020 Maybe this line is deleted within linux-4.1 kernels?
seems to me this IRQF_DISABLED definition has been dropped for w/e reason from kernels 4.1.0. Therefore I would think a border version of <sys-kernel/gentoo-sources-4.1.0 or thereabouts (< linux-4.1.3) would serve as a fix. 1. Setting a single border version of < is discouraged however here it might just work. 2. It is a more comprehensive fix to return the IRQF_DISABLED back into the kernel making it a bug needing fixing for the kernel project / herd. Feel free to CC them and or make a bug accordingly assigning to them.
Let me rephrase that: 1) Restrict this package to only using kernels < (less than) linux-4.1.3 kernels. 2) I tend to agree with fixing, instead of merrily hacking using the above #1 option. I think I noticed somewhere within the forums, people were merrily defining IRQF_DISABLED. (ie. #define IRQF_DISABLED) This would seem to avoid the compile error in my opinion too? A patch would then be simple, with needing just to find which source header (.h) file to add this line to.
well yes, I would be looking to find the entry in the kernels < linux-4.1.3, re-add, make the patch and submit upstream. However upstream should be able to do the same from a simple textual description for something so fundamental to them. I can set a border version but first can you indicate re action re a patch of filing upstream.
net-dialup/martian-modem hasn't seen a release since 2008. Google results has indicted nothing so far from the upstream kernel.org concerning this declaration drop, nor fixes. Every result or possible fix seems to be from 3rd party developers. Another good idea is to search Debian archives for fixes, but looks there too they haven't seen a change to their martian-modem Debian package change log since 2008. (Most civilized areas of countries utilize DSL/Cable including Wi-Fi for roaming.) You might consider emailing the Gentoo kernel maintainers concerning this dropped declaration, to gain their insight for the best possible method of fixing this bug before possibly wasting time with an initial effort. There's quite a few other driver packages, and would imagine this issue has surfaced elsewhere! ;-) Bingo. Again, looks like they're just defining a null variable/definition. I think Dahdi looks to be building their own kernel too? This Dahdi patch isn't within the Portage tree, and is only downloaded through a dist mirror. net-misc/dahdi http://packages.gentoo.org/package/net-misc/dahdi 31 Jul 2015; Tony Vroon (chainsaw) -dahdi-2.10.1-r1.ebuild, dahdi-2.10.2-r2.ebuild: Patching to address upstream kernel deprecation of IRQF_DISABLED as reported by Toralf Förster and tested by Jaco Kroon. Gentoo Mirror /pub/gentoo/distfiles/gentoo-dahdi-patchset-1.2.3.tar.bz File: dahdi-patchset/04-dahdi-irq-shared.diff diff -uNr dahdi-linux-2.10.2.ORIG/include/dahdi/kernel.h dahdi-linux-2.10.2/include/dahdi/kernel.h --- dahdi-linux-2.10.2.ORIG/include/dahdi/kernel.h 2015-06-15 21:37:29.000000000 +0200 +++ dahdi-linux-2.10.2/include/dahdi/kernel.h 2015-06-30 06:19:42.000000000 +0200 @@ -76,6 +76,10 @@ #define HAVE_NET_DEVICE_OPS #endif +#define DAHDI_IRQ_SHARED IRQF_SHARED +#define DAHDI_IRQ_DISABLED IRQF_DISABLED +#define DAHDI_IRQ_SHARED_DISABLED IRQF_SHARED | IRQF_DISABLED + #if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 26) # ifdef RHEL_RELEASE_VERSION # if RHEL_RELEASE_CODE < RHEL_RELEASE_VERSION(5, 6)
I should also note, the following is not apparently showing many, if any, results as well. # fgrep /usr/portage/* -r -e "IRQF_DISABLED" -i # fgrep /usr/portage/* -r -e "IRQF DISABLED" -i
Odd all round. The patch in Comment 10 appears to patch a file kernel.h in the package net-misc/dahdi which is fine for that package. I think the easiest path here is to set a border version on the kernel, however it is a temporary solution. Somewhen in the future the kernels list <= will be purged form portage and the package will again break. But then the package is from 2008. I wonder should we be thinking the tree cleaners? I do not care to cast a final decision with this. Kernels are not my usual field. Perhaps CC Chainsaw.
Ian Delaney: "I wonder should we be thinking the tree cleaners?" Could always just toss the baby out with the bath water. (Anybody can simply delete a problem.) However I too realize it's a package which hasn't seen an update since 2010, and if this is an upstream kernel issue, then it's needless to fight the inevitable. However there are still working stable kernels that may work for the at least next six months or so. (I misspoke earlier, there's a release of martian_modem during 2010 as well.) 1) Set the border version, or the maximum kernel this package will work with. (ie. <linux-4.1.0 or <linux-4.1.3 kernels, think we need verification which kernel drops IRQF_DISABLED.) 2) Put a WARNING within the build (elog) printf notes that this package breaks against >=linux-4.1.0 or >=linux-4.1.3 kernels, due to upstream kernels dropping IRQF_DISABLED definition. (If we do not get verification of the kernel versions here, I'll see the build failure here as I do have martian_modem installed & building against stable kernels weekly. Note, there may not be a failure at all.) Lastly, we have not ruled-out defining IRQF_DISABLED within the martian-modem sources ourselves as a fix. From what I'm seeing, it maybe as simple "#define IRQF_DISABLED" within one of the martian_modem sources. If I have to write in some code, others need to test the patch which is applied to the martian_modem sources for kernels >linux-4.10/>linux-4.1.3. Personally, I would just rather perform 1 & 2 for now. I'm never a fan of just dropping packages unless they're too broken. (I can think of one proprietary package at this moment, but even it's very popular amongst some users.) Instead of just dropping packages, just pushing to sunrise overlay maybe advisable. This preserves the work done, and can be researched later if need be. And, creating a separate overlay titled "cleaned" may just lead to everybody, again, inevitably adding the titled "cleaned" overlay. Warning/noting within the elog/printf of the ebuild, masking, and then pushing to the Sunrise overlay is probably best. I still have my laptop which uses this hardware, but the mini-PCI hardware isn't installed as I do not have dial-up. No dial-up, can only test FAX.
irq: remove IRQF_DISABLED http://lwn.net/Articles/321386/ According to this patches notes, I quote the following: ---SNIP--- People are playing odd games with IRQF_DISABLED, remove it. Its not reliable, since shared interrupt lines could disable it for you, and its possible and allowed for archs to disable IRQs to limit IRQ nesting. Therefore, simply mandate that _ALL_ IRQ handlers are run with IRQs disabled. ---SNIP--- Hence, simply "#defining IRQF_DISABLED" should resolve the issue transparently with no ill effects.
Yeah, probably the same approach as taken by dahdi would be the best option now
(In reply to Pacho Ramos from comment #15) > Yeah, probably the same approach as taken by dahdi would be the best option > now It appears in dahdi the source has a file kernel.h under include in the source. If this package has a similar file then fine you can use the option of making an equivalent patch. One cannot patch the kernels already installed. Personally I thought dialup was all but dead. I don't mind which way it's done. By your own admission a, setting a border might last several months. Options of patching vs setting a border both work. Making a patch will ofcourse provide extended longevity and in that sense is a better option. Either way, provide a patch to either set a border version or simply "#defining IRQF_DISABLED" and I can commit it, then set it to RESOLVED TEST-REQUEST which itself assumes someone else will test it. I have doubts over that too. While I sympathise with "I'm never a fan of just dropping packages", the outdatedness of this package and hence the lesser need or demand for it cannot be ignored. Tree cleaners will readily drop a package for being broken or having a dead upstream, and a few others. If anything the latter might apply here. Still, they don't like dropping working or workable packages just because they're old. Pros and cons. The notion of storing in sunrise has merit, except sunrise is only just breathing. Perhaps some other overlay. Awaiting a patch.
# Michał Górny <mgorny@gentoo.org> (05 Jun 2017) # (on behalf of Treecleaner project) # Discontinued blob driver. Fails to build against modern kernels. # Removal in 30 days. Bug #574026. net-dialup/martian-modem
commit da2e04fbf392af1991fae5b1925845952be0e349 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: Wed Jul 5 15:24:46 2017 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: Wed Jul 5 15:35:40 2017 net-dialup/martian-modem: Remove last-rited pkg, #574026
