LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Requests for -current (14.2-->15.0) (https://www.linuxquestions.org/questions/slackware-14/requests-for-current-14-2-15-0-a-4175620463/)

gmgf 11-01-2018 12:47 AM

glibmm-2.56.1:

http://ftp.gnome.org/pub/gnome/sourc...mm-2.56.1.news
http://ftp.gnome.org/pub/gnome/sourc...-2.56.1.tar.xz

mesa-1.8.2.4:

https://www.mesa3d.org/relnotes/18.2.4.html
https://mesa.freedesktop.org/archive/mesa-18.2.4.tar.xz

Jeebizz 11-01-2018 09:39 AM

Audacious OpenGL Spectrum Analyzer issue
 
Quote:

Originally Posted by Jeebizz (Post 5921494)
I am wondering if this issue is addressed in the next Slackware / Audacious inclusion. I made a thread about this (which escapes me in trying to find it for more info), but the gist of it was when I would choose the OpenGL Spectrum Analyzer in Audacious - it would crash. It had something to do with NVIDIA drivers, and the solution was to recompile audacious with qt I think? Well anyways here is a clue - this is from Slackware64-14.2 , trying to use the OpenGL spectrum analyzer in Audacious:

Code:

slackuser@slackmachine:~$ audacious
The program 'audacious' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 10285 error_code 8 request_code 153 minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
  that is, you will receive the error a while after causing it.
  To debug your program, run it with the --sync command line
  option to change this behavior. You can then get a meaningful
  backtrace from your debugger if you break on the gdk_x_error() function.)
WARNING main.cc:320 [main_cleanup]: exit() called unexpectedly; skipping normal cleanup.


Found my original post: https://www.linuxquestions.org/quest...er-4175592761/

From that thread, workaround:

Quote:

Quote:

Originally Posted by chris.willing (Post 5626361)
I downloaded & built the latest version (3.8) using the existing build scripts for xap/audacious & xap/audacious-plugins. At first the result was exactly the same when clicking the OpenGL Spectrum Analyzer checkbox - crashed audacious. However, I had noticed on their website that an optional Qt interface could be enabled by adding '--enable-qt' to the configure line of the build script. I rebuilt with --enable-qt and ran it as 'audacious --qt' and in that mode, the OpenGL Spectrum Analyzer checkbox worked as expected - no crash and nice looking opengl visualization.

I then went back to see if the existing version (3.7.2) would work the same way but the audacious-plugins-3.7.2 would not compile with --enable-qt.

So, short of fixing the actual bug, the workaround is to build version 3.8 with the --enable-qt option and always use the --qt option at runtime.

chris



upnort 11-01-2018 12:04 PM

I was considering a test run with updating a 14.2 system to Current. Reviewing CHANGES_AND_HINTS.TXT, NEW USERS/GROUPS SINCE 14.2, I read "postdrop user and group, UID and GID 92." I noticed no such user in /etc/passwd in my Current VM. The postfix package doinst.sh only adds a postdrop group and no postdrop user.

Looks like either the doinst.sh script or CHANGES_AND_HINTS.TXT should be corrected. :)

Also, the UPGRADE.TXT file, step 4, has not yet been updated to reflect which old packages to remove:

Code:

removepkg ash bigreqsproto compositeproto damageproto dirmngr dmxproto \
dri2proto dri3proto eject evieext fixesproto fontcacheproto fontsproto \
gcc-java glproto gnu-cobol herqq idnkit inputproto intel-gpu-tools \
kbproto libXfont libart_lgpl libmcs libmowgli libmsn libtermcap \
libva-intel-driver libwmf-docs man mplayerplug-in notify-python \
presentproto printproto pth pyrex randrproto recordproto renderproto \
resourceproto rfkill rxvt sc scrnsaverproto sendmail sendmail-cf \
slocate tetex tetex-doc transfig trn videoproto wireless-tools \
workbone xcmiscproto xextproto xf86-video-xgi xf86-video-xgixp \
xf86bigfontproto xf86dgaproto xf86driproto xf86miscproto \
xf86vidmodeproto xineramaproto xproto


lougavulin 11-01-2018 02:01 PM

It seems kde-runtime package would need to be updated to solve this issue with konqueror.

Or the patch provided can be add to patch/kde-runtime/kde-runtime-4.14.3.nm.diff.gz.

USUARIONUEVO 11-02-2018 04:12 PM

cmake-3.12.4
https://cmake.org/files/v3.12/cmake-3.12.4.tar.gz

USUARIONUEVO 11-02-2018 10:23 PM

python-urllib3-1.24.1
https://files.pythonhosted.org/packa...-1.24.1.tar.gz

pyparsing-2.3.0
https://files.pythonhosted.org/packa...g-2.3.0.tar.gz


---------------
Im not sure if can upgrade this , without updating gobject

pygobject3-3.30.1
https://files.pythonhosted.org/packa...-3.30.1.tar.gz

cwizardone 11-03-2018 06:12 AM

ffmpeg-4.0.3

The tarball, http://ffmpeg.org/releases/ffmpeg-4.0.3.tar.xz

gmgf 11-03-2018 06:22 AM

ethtool-4.19:

https://git.kernel.org/pub/scm/netwo...htool.git/log/
https://mirrors.edge.kernel.org/pub/...ol-4.19.tar.xz

gmgf 11-04-2018 12:52 PM

btrfs-progs-v4.19:

https://git.kernel.org/pub/scm/linux...progs.git/log/
https://mirrors.edge.kernel.org/pub/...s-v4.19.tar.xz

gmgf 11-04-2018 12:56 PM

xapian-core-1.4.9:

https://xapian.org/docs/xapian-core-1.4.9/NEWS
https://oligarchy.co.uk/xapian/1.4.9...e-1.4.9.tar.xz

USUARIONUEVO 11-04-2018 06:12 PM

This three are outdated in perl package.

DBD-mysql-4.048
https://cpan.metacpan.org/authors/id...l-4.048.tar.gz

DBI-1.642
https://cpan.metacpan.org/authors/id...I-1.642.tar.gz

IO-Socket-SSL-2.060
https://cpan.metacpan.org/authors/id...L-2.060.tar.gz

USUARIONUEVO 11-04-2018 07:28 PM

xmms can be upgraded to xmms2 ?

https://github.com/xmms2/wiki/wiki

gmgf 11-05-2018 12:34 PM

lvm2-2.0.02.182:

ftp://sources.redhat.com/pub/lvm2/LVM2.2.02.182.tgz

lougavulin 11-05-2018 03:22 PM

tmux 2.8 has been released (Aug 17) with improvements and few fixes.

tmux-2.8.tar.gz

CHANGES file.

cwizardone 11-05-2018 08:38 PM

Quote:

Originally Posted by cwizardone (Post 5922396)

Well, that was fast. Two days later and we have 4.1.

https://ffmpeg.org/download.html

gmgf 11-06-2018 06:49 AM

util-linux-2.33:

https://git.kernel.org/pub/scm/utils...linux.git/log/
https://mirrors.edge.kernel.org/pub/...ux-2.33.tar.xz

igadoter 11-06-2018 08:56 AM

Removed! python-xdg is script written in 2005!

drumz 11-06-2018 08:57 AM

Vim now includes icons and *.desktop files (installed during "make install"), so I make the following changes to the build scripts (I grab current's Vim SlackBuild and build it on Slackware 14.2 here):

vim.SlackBuild.patch:
Code:

--- vim.orig.SlackBuild        2018-09-18 15:04:14.000000000 -0700
+++ vim.SlackBuild        2018-11-06 07:26:16.723429626 -0700
@@ -156,6 +156,9 @@
 # Add patched vimrc to the package:
 cat runtime/vimrc.new > $PKG/usr/share/vim/vimrc.new
 
+# Remove gvim.desktop - it will be included in vim-gvim
+rm $PKG/usr/share/applications/gvim.desktop
+
 # Fix manpage symlinks:
 if [ -d $PKG/usr/man ]; then
  ( cd $PKG/usr/man

vim-gvim.SlackBuild.patch:
Code:

--- vim-gvim.orig.SlackBuild        2018-09-18 15:04:14.000000000 -0700
+++ vim-gvim.SlackBuild        2018-11-06 07:36:18.654409021 -0700
@@ -194,10 +194,10 @@
 # Perhaps we would be better off without this - forcing folks to run kappfinder
 # or something.  It seems better than starting with nothing, but might force
 # people into defaults they don't want.  Another nifty catch-22...
-mkdir -p $PKG/usr/share/applications
-cp -a $CWD/gvim.desktop $PKG/usr/share/applications
-mkdir -p $PKG/usr/share/pixmaps
-cp -a $CWD/gvim.png $PKG/usr/share/pixmaps
+#mkdir -p $PKG/usr/share/applications
+#cp -a $CWD/gvim.desktop $PKG/usr/share/applications
+#mkdir -p $PKG/usr/share/pixmaps
+#cp -a $CWD/gvim.png $PKG/usr/share/pixmaps
 
 # Remove empty directories:
 find $PKG -type d -exec rmdir -p {} \; 2> /dev/null

- Erich

Xsane 11-07-2018 05:16 PM

Pat, I'd hold off for 2.33.1 coming soon (agetty got hosed again).

volkerdi 11-07-2018 05:56 PM

Quote:

Originally Posted by Xsane (Post 5923853)
Pat, I'd hold off for 2.33.1 coming soon (agetty got hosed again).

Is there any online discussion about the issue that you could link to? I'm afraid "hosed" isn't very specific.

Xsane 11-07-2018 09:29 PM

Quote:

Originally Posted by volkerdi (Post 5923861)
Quote:

Originally Posted by Xsane (Post 5923853)
Pat, I'd hold off for 2.33.1 coming soon (agetty got hosed again).

Is there any online discussion about the issue that you could link to? I'm afraid "hosed" isn't very specific.

Well, hosed is too strong a word; I was shootin' from the hip on that one.

I was just trying to save you from building and distributing 2.33 when 2.33.1
will likely be released within days. I didn't think you'd care about the details.

So, there has been an ongoing design issue revolving around agetty initially
inputting the 'user' name and then handing it off to 'login' while maintaining
line editing capabilities between the two.

There have been several solutions tried and each seem to expose some problem.
It has come up here on lq at least once before.

The last cycle spawned yet another solution, which introduce some regressions.

The discussion is spread out over years. For the 2.33 to 2.33.1 issues see:
https://marc.info/?t=154150402600001&r=1&w=2
https://marc.info/?t=154159602900006&r=1&w=2

If you want more go here:
https://marc.info/?l=util-linux-ng&r=1&w=2
and search 'agetty' in the last three months.

For example this thread:
https://marc.info/?t=153967424900001&r=1&w=2

teoberi 11-08-2018 01:54 AM

PHP 7.2.12 does not appear available on the http://php.net site!
However, it appears in the "Current (pre-release) ChangeLog for x86_64".

ponce 11-08-2018 02:01 AM

Quote:

Originally Posted by teoberi (Post 5923950)
PHP 7.2.12 does not appear available on the http://php.net site!
However, it appears in the "Current (pre-release) ChangeLog for x86_64".

it's not listed but it's actually available there

http://php.net/distributions/php-7.2.12.tar.xz

it also had been tagged in their git repository 45 hours ago (at the time of writing this)

http://git.php.net/?p=php-src.git;a=...ads/PHP-7.2.12

Didier Spaier 11-08-2018 04:53 AM

blackbox packaging
 
Hello,

The new Slackware blackbox package still bundles blackbox and bbkeys, which implies to install blackbox onto the file system before building bbkeys.

Personally I am not comfortable installing stuff in the process of package building, which additionally prevents to use fakeroot when running the SlackBuild, which some users prefer.

Maybe consider shipping bbkeys in a separate package instead?

dugan 11-08-2018 08:57 AM

Quote:

Originally Posted by Didier Spaier (Post 5923987)
The new Slackware blackbox package still bundles blackbox and bbkeys, which implies to install blackbox onto the file system before building bbkeys.

No it doesn't imply that. The source SlackBuild installs BlackBox and bbkeys into the same package root, in that order, and then runs "makepkg" on that root.

This is how SlackBuilds involving more than one source tarball typically work.

orbea 11-08-2018 09:55 AM

Quote:

Originally Posted by dugan (Post 5924058)
No it doesn't imply that. The source SlackBuild installs BlackBox and bbkeys into the same package root, in that order, and then runs "makepkg" on that root.

This is how SlackBuilds involving more than one source tarball typically work.

In this case it seems to really mean that, the blackbox.SlackBuild contains the following.

Code:

# Install onto filesystem - needed for bbkeys to find libbt:
make install || exit 1

https://mirrors.slackware.com/slackw.../xap/blackbox/

And while I don't have fakeroot installed, it will fail with sandbox.

Code:

make[2]: Leaving directory '/tmp/blackbox-0.74/util'
make[2]: Entering directory '/tmp/blackbox-0.74'
make[2]: Leaving directory '/tmp/blackbox-0.74'
make[1]: Leaving directory '/tmp/blackbox-0.74'
Making install in data
make[1]: Entering directory '/tmp/blackbox-0.74/data'
Making install in styles
make[2]: Entering directory '/tmp/blackbox-0.74/data/styles'
make[3]: Entering directory '/tmp/blackbox-0.74/data/styles'
make[3]: Nothing to be done for 'install-exec-am'.
 /usr/bin/mkdir -p '/usr/share/blackbox/styles'
 * ACCESS DENIED:  mkdir:        /usr/share/blackbox
/usr/bin/mkdir: cannot create directory ‘/usr/share/blackbox’: Permission denied
make[3]: *** [Makefile:374: install-dist_styleDATA] Error 1
make[3]: Leaving directory '/tmp/blackbox-0.74/data/styles'
make[2]: *** [Makefile:446: install-am] Error 2
make[2]: Leaving directory '/tmp/blackbox-0.74/data/styles'
make[1]: *** [Makefile:460: install-recursive] Error 1
make[1]: Leaving directory '/tmp/blackbox-0.74/data'
make: *** [Makefile:472: install-recursive] Error 1
 * --------------------------- ACCESS VIOLATION SUMMARY ---------------------------
 * LOG FILE: "/tmp/sandbox-19001.log"
 *
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute Path (not canonical)
FORMAT: R - Canonical Path
FORMAT: C - Command Line

F: mkdir
S: deny
P: blackbox
A: /usr/share/blackbox
R: /usr/share/blackbox
C: /usr/bin/mkdir -p /usr/share/blackbox styles
 * --------------------------------------------------------------------------------

https://slackbuilds.org/apps/sandbox/

timsoft 11-08-2018 01:47 PM

exfat support (fuse-exfat and exfat-utils see sbo)

exfat is being used more often for memory sticks to allow >4GB individual file sizes, so it would be nice to have the support there in slackware.

bassmadrigal 11-08-2018 02:36 PM

Quote:

Originally Posted by timsoft (Post 5924164)
exfat support (fuse-exfat and exfat-utils see sbo)

exfat is being used more often for memory sticks to allow >4GB individual file sizes, so it would be nice to have the support there in slackware.

Unfortunately, this likely won't happen because of patents. While there are open-source implementations for exfat, they likely can't be legally included in distributions in certain countries, which would get Slackware in hot water.

USUARIONUEVO 11-08-2018 03:19 PM

gimp-2.10.8
https://download.gimp.org/pub/gimp/v...2.10.8.tar.bz2

USUARIONUEVO 11-08-2018 05:13 PM

cups-2.2.9
https://github.com/apple/cups/archive/v2.2.9.tar.gz

USUARIONUEVO 11-08-2018 08:38 PM

meson-0.48.2
https://github.com/mesonbuild/meson/.../0.48.2.tar.gz

pycairo-1.18.0
https://github.com/pygobject/pycairo...v1.18.0.tar.gz

nobodino 11-09-2018 01:20 AM

this site : https://fossies.org/linux/misc/ is a mine to track source package update.

gmgf 11-09-2018 01:57 AM

bison-3.2.1:

http://git.savannah.gnu.org/cgit/bison.git/log/
http://ftp.gnu.org/gnu/bison/bison-3.2.1.tar.xz

quietguy47 11-09-2018 05:37 AM

How many people work on Slackware development?

Didier Spaier 11-09-2018 06:08 AM

Quote:

Originally Posted by quietguy47 (Post 5924413)
How many people work on Slackware development?

Four:
  • Pat
  • Mr Patrick Volkerding
  • volkerdi
  • Johnson
Of course there are also contributors, but no official list of them that I am aware of.

Didier Spaier 11-09-2018 06:09 AM

(duplicate post)

ehartman 11-09-2018 06:13 AM

Quote:

Originally Posted by Didier Spaier (Post 5924426)
Four:
  • Pat
  • Mr Patrick Volkerding
  • volkerdi

Which, of course, is only one person <grin>

cwizardone 11-09-2018 09:26 AM

Quote:

Originally Posted by ehartman (Post 5924429)
Which, of course, is only one person <grin>

All one and the same, including Johnson.
Long story, maybe someone else is interested in tracking down the series of posts that resulted in that appellation. :)
At the moment I need coffee.....
:)

lougavulin 11-09-2018 09:43 AM

Quote:

Originally Posted by cwizardone (Post 5924472)
All one and the same, including Johnson.
Long story, maybe someone else is interested in tracking down the series of posts that resulted in that appellation. :)
At the moment I need coffee.....
:)

I did not know, so I looked for...

Thank you ! :D

montagdude 11-09-2018 11:32 AM

While Patrick is the BDFL, I don't think it's accurate to say he's the only person who works on Slackware development. There is a list of contributors somewhere, but I can't find it right now. Anyone? I know Robby Workman, Eric Hemeleers, and drmozes (don't remember his actual name), among others, are on that list.

NonNonBa 11-09-2018 11:47 AM

Hi,

Quote:

Originally Posted by Didier Spaier (Post 5923987)
Hello,

The new Slackware blackbox package still bundles blackbox and bbkeys, which implies to install blackbox onto the file system before building bbkeys.

Personally I am not comfortable installing stuff in the process of package building, which additionally prevents to use fakeroot when running the SlackBuild, which some users prefer.

Maybe consider shipping bbkeys in a separate package instead?

With this, bbkeys seems to find its kittens back:

Code:

--- blackbox.SlackBuild.orig    2018-11-08 00:02:31.000000000 +0100
+++ blackbox.SlackBuild 2018-11-09 18:45:23.173545291 +0100
@@ -110,9 +110,6 @@
 # Build:
 make $NUMJOBS || make || exit 1
 
-# Install onto filesystem - needed for bbkeys to find libbt:
-make install || exit 1
-
 # Install into package:
 make install DESTDIR=$PKG || exit 1
 mkdir -p $PKG/etc/X11/xinit
@@ -154,6 +151,14 @@
  \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
  -exec chmod 644 {} \;
 
+# The blackbox's libbt won't be met. We could make the LIBBT_CFLAGS and
+# LIBBT_LIBS environment to point in the temporary root, but we will
+# rather try to keep going with pkg-config, in case the requirements are
+# updated in the future.
+export PKG_CONFIG_PATH="$(pwd)/pkgconfig.$$"
+mkdir "$PKG_CONFIG_PATH"
+sed "s,=/usr,=$PKG/usr," "$PKG/usr/lib${LIBDIRSUFFIX}/pkgconfig/libbt.pc" >"$PKG_CONFIG_PATH/libbt.pc"
+
 # Configure:
 CFLAGS="$SLKCFLAGS" \
 ./configure \

:)

bassmadrigal 11-09-2018 12:07 PM

Quote:

Originally Posted by montagdude (Post 5924511)
drmozes (don't remember his actual name)

Stuart Winter

Quote:

Originally Posted by montagdude (Post 5924511)
There is a list of contributors somewhere, but I can't find it right now. Anyone? I know Robby Workman, Eric Hemeleers, and drmozes (don't remember his actual name), among others, are on that list.

From SlackDocs:

Quote:

Eric Hameleers (aka AlienBOB), Robby Workman (aka rworkman), Stuart Winter (aka MoZes), Eric Jan Tromp (aka alphageek), Alan Hicks, Mark Post, Fred Emmott, Vincent Batts, Heinz Wiesinger (aka pprkut) and several more.
I'm not sure if the list is up-to-date.

ZhaoLin1457 11-09-2018 12:29 PM

We debated in 14 pages that off-topic posts must be righteously punished with life-long sentences of banning.

And what are you doing here?

jakedp 11-09-2018 01:02 PM

Provoking more to get life long bans. :-p

philanc 11-10-2018 02:18 PM

Quote:

Originally Posted by bassmadrigal (Post 5924524)
Stuart Winter

From SlackDocs:
Quote:

Eric Hameleers (aka AlienBOB), Robby Workman (aka rworkman), Stuart Winter (aka MoZes), Eric Jan Tromp (aka alphageek), Alan Hicks, Mark Post, Fred Emmott, Vincent Batts, Heinz Wiesinger (aka pprkut) and several more.
I'm not sure if the list is up-to-date.

A slightly more complete list is in http://www.slackware.com/~alien/tdos...-slackware.pdf (~ page 12) - this is dated Oct-2009:
Code:

Patrick Volkerding - volkerdi@
Eric Hameleers    - alien@
Piter PUNK        - piterpunk@
Robby Workman      - rworkman@
Stuart Winter      - mozes@
Mark Post          - markkp@
Fred Emmott        - fred@
Vincent Batts      - vbatts@
Alan Hicks        - alan@
Amritpal Bath      - amrit@
Erik Jan Tromp    - alphageek@
Karl Magnus Kolstø - karlmag@
Leopold Midha      - netrixtardis@
John Jenkins      - mrgoblin@


SCerovec 11-10-2018 03:19 PM

Quote:

Originally Posted by ZhaoLin1457 (Post 5924529)
We debated in 14 pages that off-topic posts must be righteously punished with life-long sentences of banning.

And what are you doing here?

we seem to be checking HR(*) dependencies are meet for the most next Slackware yet


(*)- human resources

:hattip:

Didier Spaier 11-11-2018 02:53 AM

It seems that a joke I made contributed to derail this thread. I apologize for that, now let's put it back on tracks.

gmgf 11-12-2018 03:22 AM

libtiff-4.0.10:

https://gitlab.com/libtiff/libtiff/b...ster/ChangeLog
https://download.osgeo.org/libtiff/tiff-4.0.10.tar.gz

th_r 11-12-2018 04:03 AM

Hi.

In package net-snmp-5.8-i586-1 library /usr/lib/perl5/vendor_perl/auto/NetSNMP/agent/agent.so is broken.

ldd /usr/lib/perl5/vendor_perl/auto/NetSNMP/agent/agent.so
linux-gate.so.1 (0xb7f7b000)
libnetsnmpmibs.so.30 => not found
libnetsnmpagent.so.30 => not found
libnetsnmp.so.30 => not found
libc.so.6 => /lib/libc.so.6 (0xb7d56000)
/lib/ld-linux.so.2 (0xb7f7d000)

Please rebuild it.

Thanks

orbea 11-12-2018 12:20 PM

I wanted to remove all my haskell packages.
Code:

# removepkg haskell-*
/sbin/removepkg: line 317: [: too many arguments
/sbin/removepkg: line 331: [: too many arguments
basename: extra operand '/var/lib/pkgtools/packages/haskell-aeson-1.4.1.0-x86_64-1_SBo'
Try 'basename --help' for more information.
No such package: . Can't remove.

With adding some quotes to lines 317 and 331 it will now remove a single haskell package.
Code:

--- removepkg.orig        2018-11-12 10:09:30.810016947 -0800
+++ removepkg        2018-11-12 10:17:51.059847322 -0800
@@ -314,7 +314,7 @@
  # we don't enforce this policy.  If there's more than one, only one will
  # be removed.  If you want to remove them all, you'll need to run
  # removepkg again until it removes all the same-named packages.
-  if [ ! -e $ADM_DIR/packages/$PKGNAME ]; then
+  if [ ! -e "$ADM_DIR/packages/$PKGNAME" ]; then
    # Short name not found - finally try looking for full name - e.g. foo-1.0-arm-1
    pushd $ADM_DIR/packages > /dev/null
    # Don't set PKGNAME if there are no matches:
@@ -328,7 +328,7 @@
    popd > /dev/null
  fi
 
-  if [ -r $ADM_DIR/packages/$PKGNAME ]; then
+  if [ -r "$ADM_DIR/packages/$PKGNAME" ]; then
    if [ ! "$WARN" = true ]; then
    echo "Removing package: $(basename $ADM_DIR/packages/$PKGNAME)"
    fi

Given this comment from removepkg I suppose this is the correct behavior?
Code:

# If we don't have a package match here, then we will attempt to find
# a package using the long name format (name-version-arch-build) for
# which the base package name was given.  On a properly-managed machine,
# there should only be one package installed with a given basename, but
# we don't enforce this policy.  If there's more than one, only one will
# be removed.  If you want to remove them all, you'll need to run     
# removepkg again until it removes all the same-named packages.



All times are GMT -5. The time now is 08:08 AM.