[FFe][karmic] Please update verlihub to 0.9.8e-r2 version

Bug #391279 reported by Artur Rona
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
verlihub (Debian)
Invalid
Undecided
Unassigned
verlihub (Ubuntu)
Invalid
Wishlist
Unassigned

Bug Description

Binary package hint: verlihub

2009-07-10 netcelli (0.9.8e-r2)
  * Updated current date
  * Do not track Makefile changes

2009-07-05 netcelli (0.9.8e-r1)
  * Fixed a possible crash
  * Re-added hub_version variable
  * Fixed a crash on FreeBSD with pluginterface

2009-05-16 chaos/netcelli (0.9.8e)

  * Fixed possible reg exploit if an user is admin
  * Added OS detection in configure script
  * Removed trigger execution (it doesn't work very well and it's not secure)
  * Send $BassPass only if user is really regged
  * Change max length of send_as column to 25
  * !getip, !getinfo, !gethost, !hidekick and !unhidekick return same info 2 times if the argument is followed by a space
  * Added frequency meaning (thx to Seth)
  * Check if $Key is already sent
  * Don't report wrong password if user is not regged
  * Call OnUserLogout when user is really logged in
  * Detect BotINFO extension and check if that extension is set when an user sends $BotINFO
  * Force !ccbc argument to be upper case and sent a message back to user when message is sent
  * Fixed CC zone limit bug (thx to T@R@24): OP cannot enter if CC zone limit was set
  * Removed hub_version variable because not used anymore
  * Fixed configure script error
  * Removed !flood command: it's not useful and block the hub
  * Fixed output for !gc [file] command (where file is the value of file column in SetupList table; default is config)
  * Added message for !hublist command
  * Removed !proto*_any cmd
  * Fixed opchat and hubsecurity registration: it was possible to reg both of them
  * Fix: connection was not closed if user sends password before nick
  * Do not send $ForceMove if there is no redirect
  * Nick column length was always set to 30. Now it uses the value of max_nick variable
  * Fixed triggers exploit :
  * It's impossible to trigger files outside VerliHub config folder
  * dbconfig file can't be triggered
  * Added GetPath, FilterPath and ExpandPath method
  * Regenerated configure and Makefile scripts again because I forget to remove diakritika plug from configure.ini
  * Fixed mispelling in cchatconsole.cpp
  * Moved diaktritika plugin outside Verlihub core
  * Fixed leading zero in %[ss],%[mm], %[DD], %[MM] and %[HH] variables for triggers
  * Fix: !(add|mod)conntype doesn't work if -d option is set
  * Added !whocc command
  * Added custom redirect on invalid key
  * Added drop_invalid_key variable; now VerliHub checks invalid keys
  * Fixed NMDC encoding function
  * Added disable_report_cmds variable (default value 0) to disable reports
  * Added !serverinfo cmd
  * Added !regsearch cmd
  * Added HubINFO in $Support
  * Fixed tag_max_hs_ratio that was never replaced
  * Fixed mail ban
  * Added mysql autoreconnection option
  * Fixed wrong MYSQL SOCKET (now set with MYSQL_UNIX_PORT)
  * Fix: reg_op was never set if the user regs with autoreg
  * Added UTF8 support
  * Fixed and extented vh_runhub script; vh_restart is deprecated
  * Added new config variables: int_search_reg_pass, min_share_use_hub_reg, min_share_use_hub_vip (thk to Raider)
  * Added OnDelReg event handler function
  * Added OnNewReg event handler function
  * Added OnUnBan event handler function
  * Added OnNewBan event handler function
  * Added OnHubName event handler function
  * Patched for GCC >=4.3.
  * Fixed socket for WIN32
  * Fix: bc_reply was automatically set to robot nick that just sent a bc
  * Removed email ban
  * Fixed share ban
  * Fixed IP-Range and CC zones
  * Fixed password_min_len that was always set to 6
  * Fix: tag_min and max version variables never worked with DGUI client
  * Fix: converted tag_min_version_* from int to double
  * Fixed !regdisable that never worked; it's also impossible to disable master accounts
  * Fixed syntax error for reg commands
  * Fix: plug replacer path was wrong
  * Fixed wrong value replace for %[YY] variable
  * Fixed wrong usercount value showed with !hubinfo command
  * Fixed a crash if verlihub tries to load plugin with no path set
  * Fixed !addplug command that crashes the hub if no options are provided
  * Fixed of addding and removing of master users with AddRegUser and DelRegUser API
  * Make -p option mandatory or hub may crash because it tries to load a non-existing plugin
  * Updated !*plug help if the command is wrong
  * Fixed wrong regex for !add/modplug command
  * Fixed share and bw conversion for !hubinfo command (thx to Intruder)
  * Fixed syntax error for !hubinfo output (thx to Intruder)
  * Custom redirect (!add/mod/delredirect)
  * Added !hcmd (this will help owner for ex. with triggers and custom redirects)
  * Fixed random redirect because pseudo-random number generator was never re-initialized with a valid seed
  * Added custom redirect(!add/mod/delredirect)
  * Fix: Master class is now immune from kick and ban
  * Added GetTempRights
  * Added DelRegUser API
  * Added AddRegUser API
  * Fixed hide share (now it blocks the user to download filelist)
  * Renamed few API functions because it makes confusion
  * Added GetVerliPath API
  * Added GetTotalShareSize API
  * Added Ban API that was never implemented
  * Fixed GetConfig API that returned a wrong value if config variable is empty (thx to Rolex and Frog)
  * Fixed SendDataToAll API that ignored min class and max class variables (thx to Rolex)
  * Added GetUserCC API for Lua Plugin
  * Fix: Verlihub replaces the IP in $ConnectToMe request if IP is wrong. This fix WAN to WAN and LAN to LAN connections and no drop because of wrong IP in client settings

Tags: patch upgrade
Artur Rona (ari-tczew)
tags: added: update upgrade
Artur Rona (ari-tczew)
Changed in verlihub (Ubuntu):
assignee: nobody → Artur Rona (ari-tczew)
status: New → Confirmed
status: Confirmed → In Progress
Artur Rona (ari-tczew)
Changed in verlihub (Ubuntu):
assignee: Artur Rona (ari-tczew) → nobody
status: In Progress → New
Revision history for this message
Artur Rona (ari-tczew) wrote :

verlihub (0.9.8e-0ubuntu1) karmic; urgency=low

  * New upstream release (LP: #391279).

 -- Artur Rona <email address hidden> Thu, 25 Jun 2009 11:49:38 +0200

Revision history for this message
Andrew Mitchell (ajmitch) wrote :

I just took a look at the current version in Debian, and it's to be removed soon due to lack of maintenance there (see http://bugs.debian.org/529817 for details). Are you willing to look after this package, preferably in Debian as well?

Revision history for this message
Artur Rona (ari-tczew) wrote :

OK, I can own maintenance of verlihub package. What I need to do?

Revision history for this message
Andrew Mitchell (ajmitch) wrote :

Firstly by replying to that bug in Debian & probably getting the OK from the security team that this new version isn't full of holes, and with the current maintainer seemingly not around, it shouldn't be hard to adopt the package & get the new version sponsored through mentors.debian.net. As long as this all gets done within the next 7-8 weeks we can then sync the version you get into Debian.

Revision history for this message
Artur Rona (ari-tczew) wrote :

OK, but I guess that Ubuntu can accept 0.9.8e package and Debian can wait for new maintainer, right?

Revision history for this message
Andrew Mitchell (ajmitch) wrote :

Sorry for the delay, I went to Sourceforge to get the upstream tarball & saw that they have a bugfix version 0.9.8e-r1 released, would you be able to update the packaging to this latest version & resubscribe the sponsors team? From the look of the upstream changelog, any changes you have to make should be minimal.

Revision history for this message
Artur Rona (ari-tczew) wrote :

I'm on a holiday for 2 weeks. When I back I'll make a new package.

Artur Rona (ari-tczew)
description: updated
summary: - [karmic] Please update verlihub to 0.9.8e version
+ [karmic] Please update verlihub to 0.9.8e-r1 version
Changed in verlihub (Ubuntu):
assignee: nobody → Artur Rona (ari-tczew)
status: New → Confirmed
Artur Rona (ari-tczew)
description: updated
tags: removed: update
summary: - [karmic] Please update verlihub to 0.9.8e-r1 version
+ [karmic] Please update verlihub to 0.9.8e-r2 version
Changed in verlihub (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Artur Rona (ari-tczew) wrote : Re: [karmic] Please update verlihub to 0.9.8e-r2 version
Revision history for this message
Artur Rona (ari-tczew) wrote :
Revision history for this message
Artur Rona (ari-tczew) wrote :
Changed in verlihub (Ubuntu):
status: In Progress → New
assignee: Artur Rona (ari-tczew) → nobody
Revision history for this message
Andrea Veri (av) wrote :

Artur, feel free to adopt the package before it gets removed. I won't have time to maintain it so it would be nice to have someone looking at it again.

Artur Rona (ari-tczew)
Changed in verlihub (Ubuntu):
status: New → Confirmed
Revision history for this message
Andrea Veri (av) wrote :

this package has been removed from Debian, so I don't see the point to keep having it on Ubuntu. Popcon says clearly that verlihub's users prefer to have it not-packaged so they can build it by their own hands, maybe for setting up some particular options. What do you think?

Revision history for this message
Andrea Veri (av) wrote :

removing u-u-s as subscriber for now.

Revision history for this message
Artur Rona (ari-tczew) wrote :

I think that my package can be included yet to karmic. I can get own maintenance of verlihub, so in 10.04 package should be synced from debian.

Revision history for this message
Andrea Veri (av) wrote :

as I said this package has been removed from Debian already. If you wanna keep maintaining it on Ubuntu, feel free to do it!

Artur Rona (ari-tczew)
tags: added: patch
Revision history for this message
Chris Coulson (chrisccoulson) wrote : Re: [karmic] Please update verlihub to 0.9.8e-r2 version

Artur - thank you for your work. However, after looking at the upstream changes in the new version, I think this update will probably require a Feature-Freeze exception (as we are in Feature Freeze now). The Feature Freeze exception process is detailed at https://wiki.ubuntu.com/FreezeExceptionProcess . Would you mind taking a look at that?

Thanks

Changed in verlihub (Ubuntu):
assignee: nobody → Artur Rona (ari-tczew)
importance: Undecided → Wishlist
status: Confirmed → Incomplete
Artur Rona (ari-tczew)
summary: - [karmic] Please update verlihub to 0.9.8e-r2 version
+ [FFe][karmic] Please update verlihub to 0.9.8e-r2 version
Changed in verlihub (Ubuntu):
assignee: Artur Rona (ari-tczew) → nobody
status: Incomplete → New
Revision history for this message
StefanPotyra (sistpoty) wrote :

Hi,

sorry, but -1 from me here at this time in the cycle, as it was removed from Ubuntu as well, and hence would need to be treated as new package.

I'd suggest to start maintaining this package in Debian, that way we could sync it for karmic+1.

(marking as invalid, please upload to revu, as this falls now under the catagory of a new package).

Cheers,
    Stefan.

Changed in verlihub (Ubuntu):
status: New → Invalid
Changed in verlihub (Debian):
status: New → Invalid
Revision history for this message
Andrea Veri (av) wrote :

@Stefan,

this package shouldnt be re-uploaded into Debian again, it would make no sense. Looks like users prefers to build / install it manually to enable any eventual feature. The popcon reported 30 installations in Debian, so I would suggest to not re-introduce this package again into the archive.

Revision history for this message
Artur Rona (ari-tczew) wrote :

Hmmm, maybe should packaged with options/flags which are usually using by users? And include package verlihub-plugins.

Revision history for this message
Andrea Veri (av) wrote :

problems is there all multiple builds flags / options that could be used and you know, we cannot build a package with different build options in it. So, it's up to you, but my suggestion is to not re-introduce it into the archive.

Revision history for this message
Scott Kitterman (kitterman) wrote :

I agree on -1 for now. I'd be willing to reconsider if it gets back in Debian and we could sync it from there.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.