Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  do we have an inx conflict between debian and siduction?  (Read 3516 times)

Offline michaa7

  • User
  • Posts: 2.300
I am posting this here although this is not really breaking your system. But as someone might use inxi on IRC and it is unclear how this is configured in the Debian version it seems appropriate to post it here. Currently I have still installed the siduction version:

Quote
# apt-cache policy inxi
inxi:
  Installiert:           1.9.7~siduction.1
  Installationskandidat: 1.9.7-1
  Versionstabelle:
     1.9.7-1 0
        900 http://http.debian.net/debian/ sid/main i386 Packages
 *** 1.9.7~siduction.1 0
        900 http://packages.siduction.org/base/ unstable/main i386 Packages
        100 /var/lib/dpkg/status


But the one queued up for installation seems to have different recommends (and capabilities and/or configuration? It *is* different in installed size):
Quote
# apt-cache show inxi
Package: inxi
Version: 1.9.7-1
Installed-Size: 431
Maintainer: Unit 193 <unit193>
Architecture: all
Depends: bash (>= 3.0), gawk, pciutils, procps
Recommends: dmidecode, file, hddtemp, iproute, lm-sensors, mesa-utils, module-init-tools, net-tools, sudo, usbutils, x11-utils, x11-xserver-utils
Description-en: full featured system information script (forked from infobash)
 Inxi is a system information script that can display various things about
 your hardware and software to users in an IRC chatroom or support forum.
 It runs with the /exec command in most IRC clients and /inxi in quassel.
Homepage: http://code.google.com/p/inxi/
Description-md5: 1562a56d82390cd36e9105d4c1c7012b
Section: misc
Priority: extra
Filename: pool/main/i/inxi/inxi_1.9.7-1_all.deb
Size: 122602
MD5sum: c5a5cb98c64728202ed8af1e3e37cce1
SHA1: dbd040a62461b203217d548b4d7288935b6c2693
SHA256: 7361cbecac48a6e38b2bb16c7477f7cee6bb9f50e855 c7b003f30b505900a680

Package: inxi
Version: 1.9.7~siduction.1
Architecture: all
Maintainer: Torsten Wohlfarth <towo>
Installed-Size: 425
Depends: bash (>= 3.0), gawk, pciutils, procps
Recommends: ceni, dmidecode, file, hddtemp, iproute, lm-sensors, mesa-utils, module-init-tools, net-tools, sudo, usbutils, x11-utils, x11-xserver-utils, irssi | xchat | konversation | quassel
Homepage: http://code.google.com/p/inxi/
Priority: extra
Section: admin
Filename: pool/main/i/inxi/inxi_1.9.7~siduction.1_all.deb
Size: 117026
SHA256: ec6799c77c5c10dd160d0665ddeec4afb71938cae83b 3387b467b8f1b7d87a43
SHA1: 684edda298f796edb3446a2533aeb5d85db0d73d
MD5sum: 3ed4bd187331fe5cd134c5447c755a2b
Description: System info script for irc
 Inxi is a system information script for IRC (Internet Relay Chat) clients.
 A system information script can display all kinds of things about your
 hardware and software to users in a chatroom,  so they can help you diagnose
 problems, ... or just marvel at your system specs and kernel version ;)
 It was created to serve the need for a infoscript that isn't dependent on a
 particular irc client. Because most irc clients support the /exec command, a
 script that runs with /exec would be most portable.
 .
 inxi is a fork of infobash 3.02, the original bash sys info script by locsmif
 As time permits functionality improvements and recoding will occur.
 .
 inxi is tested with Irssi, Xchat, Konversation, BitchX, KSirc, ircII,
 Gaim/Pidgin, Weechat, KVIrc and Kopete.


So probably we should put inxi on hold until it is clarified whether or not *we* should stick to the siduction version or move on to the Debian version.
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline DeepDayze

  • User
  • Posts: 457
RE: do we have an inx conflict between debian and siduction?
« Reply #1 on: 2013/06/10, 15:27:43 »
Good question...was it h2 that may have submitted inxi for inclusion in Debian?

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.358
    • Land of the Buckeye
RE: do we have an inx conflict between debian and siduction?
« Reply #2 on: 2013/06/10, 16:00:04 »
Being accepted in Debian, I thought the risk would be slight.  So, after d-u this morning, I checked it and all is working good:

Code: [Select]
root@imerabox:/# apt-cache policy inxi
inxi:
  Installed: 1.9.7-1
  Candidate: 1.9.7-1
  Version table:
 *** 1.9.7-1 0
        500 http://ftp.us.debian.org/debian/ unstable/main amd64 Packages
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
     1.9.7~siduction.1 0
        500 http://packages.siduction.org/base/ unstable/main amd64 Packages                                                      
root@imerabox:/# exit                                                                                                            
exit                                                                                                                              
don@imerabox:~$ inxi -v3                                                                                                          
System:    Host: imerabox Kernel: 3.9-5.towo-siduction-amd64 x86_64 (64 bit, gcc: 4.7.3)                                          
           Desktop: KDE 4.10.4 (Qt 4.8.4) Distro: aptosid 2011-02 Ἡμέρα - kde-lite - (201107131633)                              
Machine:   Mobo: ASUSTeK model: P6X58D-E version: Rev 1.xx Bios: American Megatrends version: 0602 date: 03/24/2011              
CPU:       Quad core Intel Core i7 CPU 950 (-HT-MCP-) cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 33737.5
           Clock Speeds: 1: 1600.00 MHz 2: 1600.00 MHz 3: 1600.00 MHz 4: 1600.00 MHz 5: 1600.00 MHz 6: 1600.00 MHz 7: 1600.00 MHz 8: 1600.00 MHz
Graphics:  Card: NVIDIA GF100 [GeForce GTX 480] bus-ID: 05:00.0 X.Org: 1.12.4 driver: nvidia Resolution: 1920x1200@59.9hz
           GLX Renderer: GeForce GTX 480/PCIe/SSE2 GLX Version: 4.3.0 NVIDIA 319.23 Direct Rendering: Yes
Network:   Card: Marvell 88E8056 PCI-E Gigabit Ethernet Controller driver: sky2 ver: 1.30 port: d800 bus-ID: 06:00.0
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: 20:cf:30:5c:41:1d
Drives:    HDD Total Size: 2136.5GB (3.8% used) 1: model: OCZ
           2: model: KINGSTON_SS100S2 3: model: OCZ 4: model: WDC_WD1002FAEX 5: model: WDC_WD1002FAEX
Info:      Processes: 309 Uptime: 1 day Memory: 1380.2/5966.3MB Runlevel: 5 Gcc sys: 4.7.3
           Client: Shell (bash 4.2.45) inxi: 1.9.7
System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO

Offline DeepDayze

  • User
  • Posts: 457
RE: do we have an inx conflict between debian and siduction?
« Reply #3 on: 2013/06/10, 17:53:35 »
Same here dibl...no problems at all so its great to see inxi in the debian archive itself. H2 should be proud of that too!

Wonder if his smxi/sgfxi/svmi tools would do well in debian too?

Smon

  • Guest
RE: do we have an inx conflict between debian and siduction?
« Reply #4 on: 2013/06/10, 17:55:53 »
Important are the dependencies and they are the same?

recommend means "empfehlen", where is the problem?!?

Offline piper

  • User
  • Posts: 1.785
  • we are the priests ... of the temples of syrinx
RE: do we have an inx conflict between debian and siduction?
« Reply #5 on: 2013/06/10, 18:10:15 »
apt-cache depends inxi
Code: [Select]
inxi
  Depends: bash
    bash:i386
  Depends: gawk
    gawk:i386
  Depends: pciutils
    pciutils:i386
  Depends: procps
    procps:i386
  Recommends: dmidecode
  Recommends: file
    file:i386
  Recommends: hddtemp
  Recommends: iproute
  Recommends: lm-sensors
  Recommends: mesa-utils
  Recommends: module-init-tools
  Recommends: net-tools
  Recommends: sudo
    sudo-ldap
  Recommends: usbutils
    usbutils:i386
  Recommends: x11-utils
    x11-utils:i386
  Recommends: x11-xserver-utils
apt-cache rdepends inxi
Code: [Select]
inxi
Reverse Depends:
  siduction-irc
  siduction-irc
apt-cache policy
Code: [Select]
inxi:
  Installed: 1.9.7-1
  Candidate: 1.9.7-1
  Version table:
 *** 1.9.7-1 0
        500 http://ftp.us.debian.org/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
     1.9.7~siduction.1 0
        500 ftp://ftp.gtlib.gatech.edu/pub/siduction/base/ unstable/main amd64 Packages
inxi -F
Code: [Select]
System:    Host: x1 Kernel: 3.9-5.towo-siduction-amd64 x86_64 (64 bit)
           Desktop: KDE 4.10.4 Distro: siduction 12.2.0 Riders on the Storm - kde - (201304191610)
Machine:   Mobo: Gigabyte model: GA-970A-UD3 version: x.x Bios: Award version: F7 date: 10/22/2012
CPU:       Hexa core AMD FX-6300 Six-Core (-MCP-) cache: 12288 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm)
           Clock Speeds: 1: 1400.00 MHz 2: 1400.00 MHz 3: 1400.00 MHz 4: 1400.00 MHz 5: 1400.00 MHz 6: 1400.00 MHz
Graphics:  Card: NVIDIA GF106 [GeForce GTS 450] X.Org: 1.12.4 driver: nvidia Resolution: 1920x1200@60.0hz
           GLX Renderer: GeForce GTS 450/PCIe/SSE2 GLX Version: 4.3.0 NVIDIA 319.17
Audio:     Card-1: NVIDIA GF106 High Definition Audio Controller driver: snd_hda_intel
           Card-2: Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA) driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture ver: k3.9-5.towo-siduction-amd64
Network:   Card: Realtek RTL8111/8168 PCI Express Gigabit Ethernet controller driver: r8169
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: 90:2b:34:a5:99:2d
Drives:    HDD Total Size: 2820.6GB (50.6% used) 1: id: /dev/sda model: ST3500630AS size: 500.1GB
           2: id: /dev/sdc model: ST31000528AS size: 1000.2GB 3: id: /dev/sdb model: ST3320620AS size: 320.1GB
           4: id: /dev/sdd model: ST31000528AS size: 1000.2GB
Partition: ID: / size: 255G used: 46G (18%) fs: reiserfs ID: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap
Sensors:   System Temperatures: cpu: 30.6C mobo: N/A gpu: 39C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 178 Uptime: 22:35 Memory: 1494.4/7973.6MB Client: Shell (bash) inxi: 1.9.7
Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck