[Bug 367695] Re: Problem installing postresql
I just hit the same... google lead me to http://www.mydatabasesupport.com/forums/postgresql/359831-general-file-system-level-backup-32bit-64bit.html which seems to match my use case -- I've moved DB from 32bit box to 64 -- so I guess that is the reason for me. Is it the same in your case? -- Problem installing postresql https://bugs.launchpad.net/bugs/367695 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 123916] Re: fail2ban will not start if fail2ban socket is present
guys -- how long would you keep chating before you simply sync from Debian 0.8.2-3: * Assure that /var/run/fail2ban exists upon start (LP: #222804, #223706) On Sat, 17 May 2008, schnollk wrote: > I understand this is not a security vulnerability but since it is highly > security relevant I suggest to put high importance on this bug. I would > have done it myself but cannot see how or am not allowed to. -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- fail2ban will not start if fail2ban socket is present https://bugs.launchpad.net/bugs/123916 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 110132] Re: Permission denied when user belongs to group that owns group writable or setgid directories mounted via nfs
unfortunately yet again bug report is closed with some excuses and without actually doing a valid resolution of the problem... here you can find an answer on how problem can actually be solved (many kudos to C Shore) http://ubuntuforums.org/showpost.php?p=5042655&postcount=4 And here are the details from a man page of rpc.mountd: -g or --manage-gids Accept requests from the kernel to map user id numbers into lists of group id numbers for use in access control. An NFS request will normally (except when using Kerberos or other cryptographic authentication) contains a user-id and a list of group-ids. Due to a limitation in the NFS protocol, at most 16 groups ids can be listed. If you use the -g flag, then the list of group ids received from the client will be replaced by a list of group ids determined by an appropriate lookup on the server. Note that the ’primary’ group id is not affected so a newgroup command on the client will still be effective. This function requires a Linux Kernel with ver‐ sion at least 2.6.21. Does problem persists (ie current configuration doesn't address it)? YES Does ubuntu come now with kernel > 2.6.21? YES Is it possible to solve the problem without much sweat? YES Is default installation anyhow addresses or hints on possible solution? NO afaik -- Permission denied when user belongs to group that owns group writable or setgid directories mounted via nfs https://bugs.launchpad.net/bugs/110132 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 110132] Re: Permission denied when user belongs to group that owns group writable or setgid directories mounted via nfs
ah... nothing to worry about... Debian people have fixed it (as of nfs-utils 1.1.4-1) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493059 -- Permission denied when user belongs to group that owns group writable or setgid directories mounted via nfs https://bugs.launchpad.net/bugs/110132 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 123916] Re: fail2ban will not start if fail2ban socket is present
me? not exactly. it was aimed to be like that: if for some reason socket is present while application is not running -- there could have been some abrupt interruption of the process -- and the admin has to check WTF and may be fix the cause, clean up leftovers of fail2ban's operation (altered /etc/hosts.deny, iptables, etc) before attempting to blindly start it again. What I think I will do for the next debian release - I would provide "force-start" action which would indeed use fail2ban-client -x to overcome problem of the present socket file. but once again -- "start" action will remain as is On Thu, 18 Oct 2007, Soren Hansen wrote: > On Mon, Oct 15, 2007 at 09:48:07PM -, Nicolas Valcárcel wrote: > > In this bug it would be better to patch the "/etc/init.d/fail2ban" or > > make that on crash it remove the socket? > Init-script definitely. If an application crashes, it's usually pretty > difficult to tell it to clean up after itself. :) > Will you create a patch for this? -- .-. =-- /v\ = Keep in touch // \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] -- fail2ban will not start if fail2ban socket is present https://bugs.launchpad.net/bugs/123916 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 136283] fail2ban not creating pid file
FWIW - fail2ban > 0.7 doesn't create a pidfile iirc. All actions (start/stop/etc) are initiated by the fail2ban-client which either starts fail2ban-server or sends requests to the running -server via the socket file. On Fri, 31 Aug 2007, bryan986 wrote: > Public bug reported: > Binary package hint: fail2ban > When fail2ban is running, there is no pid file in /var/run. I haven't > been able to find it anywhere else either. > I tried adding the pidlock setting to the fail2ban.local configuration > file, but that did not help. I'm not even sure if that setting exists > anymore. > I am using 0.7.6-3ubuntu1 from apt > Did they remove this in newer versions? > ** Affects: fail2ban (Ubuntu) > Importance: Undecided > Status: New > ** Description changed: > Binary package hint: fail2ban > When fail2ban is running, there is no pid file in /var/run. I haven't > been able to find it anywhere else either. > I tried adding the pidlock setting to the fail2ban.local configuration > file, but that did not help. I'm not even sure if that setting exists > anymore. > + I am using 0.7.6-3ubuntu1 from apt > + > Did they remove this in newer versions? -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- fail2ban not creating pid file https://bugs.launchpad.net/bugs/136283 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 196854] [NEW] fail2ban doesn't handle leap years
o boy... for that one: dapper (net): bans IPs that cause multiple authentication errors [universe] 0.6.0-3: all you better install some backport from sid/lenny. 0.6 is heavily insecure and imho no sense to have this issue fixed there On Fri, 29 Feb 2008, Eythian wrote: > On Friday 29 February 2008 16:29:05 Yaroslav Halchenko wrote: > > see > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468382 > > apply patch provided and please verify that it works after... > That patch won't apply because it's for a significantly different version of > fail2ban than the one in dapper, and the file it's patching doesn't exist. On > the flip side, the one in dapper doesn't take 100% CPU, it just doesn't work. -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- fail2ban doesn't handle leap years https://bugs.launchpad.net/bugs/196854 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 196854] [NEW] fail2ban doesn't handle leap years
> Fair enough, although I might wait for tomorrow given the debian one has > worse > issues. what worse issues? let me know -- I will have it fixed ;-) > However, if the dapper one has real security issues shouldn't it be > updated there at some stage, given it's still supported for servers, where > this kind of thing matters? gy gy -- ask Canonical about that... just teasing ;-) or may be MOTUs? -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- fail2ban doesn't handle leap years https://bugs.launchpad.net/bugs/196854 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 196854] Re: fail2ban doesn't handle leap years
it is running well since it is already 1st of March ;-) On Sat, 01 Mar 2008, smicha wrote: > Hi, > I have the same problem as Eythian. > I use the version "Fail2Ban v0.6.0" > I have solved that problem with following trick. > (Quick and dirty ;-) > cat /dev/null > /var/log/auth.log > cat /dev/null > /var/log/fail2ban.log > /etc/init.d/fail2ban restart > Before you "flush" the auth.log and fail2ban.log, make a copy ;-) > After that, fail2ban is running wel. > Best regards > Michael Schleicher -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- fail2ban doesn't handle leap years https://bugs.launchpad.net/bugs/196854 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 196854] [NEW] fail2ban doesn't handle leap years
see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468382
apply patch provided and please verify that it works after...
On Fri, 29 Feb 2008, Eythian wrote:
> Public bug reported:
> Binary package hint: fail2ban
> Today is the 29th of February. restartd tells me fail2ban is failing to
> start. The log says:
> 2008-02-29 16:10:00,988 ERROR: Fail2Ban got an unhandled exception and died.
> 2008-02-29 16:10:00,989 ERROR: Type: 'ValueError'
> Value: ('day is out of range for month',)
> TB: [('/usr/bin/fail2ban', 47, '?', 'fail2ban.main()'),
> ('/usr/share/fail2ban/fail2ban.py', 519, 'main', 'e =
> element[1].getFailures()'), ('/usr/share/fail2ban/logreader/logreader.py',
> 143, 'getFailures', 'for element in self.findFailure(line):'),
> ('/usr/share/fail2ban/logreader/logreader.py', 174, 'findFailure', 'date =
> self.getUnixTime(timeMatch.group())'),
> ('/usr/share/fail2ban/logreader/logreader.py', 213, 'getUnixTime', 'date =
> list(time.strptime(value, self.timepattern))'),
> ('/usr/lib/python2.4/_strptime.py', 425, 'strptime', 'julian =
> datetime_date(year, month, day).toordinal() - \\')]
> and isn't actually starting the process.
> This is in dapper, and not something I think will come up a whole lot,
> but perhaps should be fixed upstream if it isn't already as it does have
> some security implications.
> ** Affects: fail2ban (Ubuntu)
> Importance: Undecided
> Status: New
--
Yaroslav Halchenko
Research Assistant, Psychology Department, Rutgers-Newark
Student Ph.D. @ CS Dept. NJIT
Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171
101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102
WWW: http://www.linkedin.com/in/yarik
--
fail2ban doesn't handle leap years
https://bugs.launchpad.net/bugs/196854
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 121374] Re: Denial of service through log injection in fail2ban
checked the 0.7.6-3 -- indeed it had the bug but it was fixed later on so debian package is not shipped with it any longer ;-) On Wed, 12 Dec 2007, Yaroslav Halchenko wrote: > I never said 'prior to 0.6'. I said that it is fixed in etch version > which is 0.7.5-2, where failregex looks like > failregex = (?:(?:Authentication failure|Failed [-/\w+]+) for(?: [iI](?:llegal|nvalid) user)?|[Ii](?:llegal|nvalid) user|ROOT LOGIN REFUSED) .*(?: from|FROM) > which is different from the reported in the bugreport against ubuntu package > So please clarify what actual failregex in what versions of fail2ban > shipped with ubuntu you have... and if they are different to corresponding > ones > in debian. > On Wed, 12 Dec 2007, Jamie Strandboge wrote: > > Yaroslav, your comment toward the end of the debian bug report says that > > this is fixed in debian prior to 0.6, but here you say it is still > > vulnerable. Since ubuntu uses debian source packages, I am confused by > > your statements. Can you clarify? > > ** Changed in: fail2ban (Ubuntu Edgy) > >Status: Confirmed => Incomplete > > ** Changed in: fail2ban (Ubuntu Dapper) > >Status: Confirmed => Incomplete -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- Denial of service through log injection in fail2ban https://bugs.launchpad.net/bugs/121374 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 121374] Re: Denial of service through log injection in fail2ban
I never said 'prior to 0.6'. I said that it is fixed in etch version which is 0.7.5-2, where failregex looks like failregex = (?:(?:Authentication failure|Failed [-/\w+]+) for(?: [iI](?:llegal|nvalid) user)?|[Ii](?:llegal|nvalid) user|ROOT LOGIN REFUSED) .*(?: from|FROM) which is different from the reported in the bugreport against ubuntu package So please clarify what actual failregex in what versions of fail2ban shipped with ubuntu you have... and if they are different to corresponding ones in debian. On Wed, 12 Dec 2007, Jamie Strandboge wrote: > Yaroslav, your comment toward the end of the debian bug report says that > this is fixed in debian prior to 0.6, but here you say it is still > vulnerable. Since ubuntu uses debian source packages, I am confused by > your statements. Can you clarify? > ** Changed in: fail2ban (Ubuntu Edgy) >Status: Confirmed => Incomplete > ** Changed in: fail2ban (Ubuntu Dapper) > Status: Confirmed => Incomplete -- Yaroslav Halchenko Ph.D. Student CS Dept. NJIT -- Denial of service through log injection in fail2ban https://bugs.launchpad.net/bugs/121374 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 121374] Re: Denial of service through log injection in fail2ban
> This seems to allow any non-whitespace characters after , which I > believe is the nature of the vulnerability described in CVE-2006-6302. > Please correct me if I'm wrong. being not anchored at the end of the string is the real reason for such vulnerability imho -- Yaroslav Halchenko Ph.D. Student CS Dept. NJIT -- Denial of service through log injection in fail2ban https://bugs.launchpad.net/bugs/121374 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 121374] Re: Denial of service through log injection in fail2ban
and actually since .* is greedy, vulnerability is not there actually...
could you test on example?
On Wed, 12 Dec 2007, Chris Fryer wrote:
> This is the relevant line from /etc/fail2ban.conf when fail2ban 0.6.0-3
> is installed on Ubuntu 6.06 LTS (Dapper).
> failregex = : (?:(?:Authentication failure|Failed [-/\w+]+) for(?:
> [iI](?:llegal|nvalid) user)?|[Ii](?:llegal|nvalid) user) .* from
> (?:::f{4,6}:)?(?P\S*)
> This seems to allow any non-whitespace characters after , which I
> believe is the nature of the vulnerability described in CVE-2006-6302.
> Please correct me if I'm wrong.
--
Yaroslav Halchenko
Research Assistant, Psychology Department, Rutgers-Newark
Student Ph.D. @ CS Dept. NJIT
Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171
101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102
WWW: http://www.linkedin.com/in/yarik
--
Denial of service through log injection in fail2ban
https://bugs.launchpad.net/bugs/121374
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 121374] Re: Denial of service through log injection in fail2ban
ain all those versions properly? that was a rhetoric question -- no follow up is necessary) On Wed, 12 Dec 2007, Jamie Strandboge wrote: > Sorry, I didn't give the complete regexes, only the ROOT LOGIN REFUSED > part. > Anyway, since these are the Debian package versions, do you know if they > are indeed affected? Simply put, Ubuntu did not make any changes to > failregex, so are these versions of the Debian packages affected? -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- Denial of service through log injection in fail2ban https://bugs.launchpad.net/bugs/121374 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 213227] [NEW] fail2ban package is missing "whois" package dependancy
package with a fix (recommends: whois) was uploaded to debian 0.8.2-2 On Mon, 07 Apr 2008, Nicorac wrote: > Public bug reported: > Binary package hint: fail2ban > The package fail2ban-0.8.1-1 should have whois as a dependence. > Whois is needed to include IP address details into warning emails. > ** Affects: fail2ban (Ubuntu) > Importance: Undecided > Assignee: Yaroslav Halchenko (yarikoptic) > Status: New > ** Changed in: fail2ban (Ubuntu) > Assignee: (unassigned) => Yaroslav Halchenko (yarikoptic) -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- fail2ban package is missing "whois" package dependancy https://bugs.launchpad.net/bugs/213227 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 121374] Re: Denial of service through log injection in fail2ban
0.8.0-2 is still affected. either upcomming -3 or 0.8.1 should fix the problem On Thu, 21 Jun 2007, Chris Fryer wrote: > ** Description changed: > Binary package hint: fail2ban > According to CVE 2006-6302 > (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2006-6302) fail2ban 0.6.1 and > below is vulnerable to log injection techniques, which can lead to the > wrong IP address being banned. This can result in denial of service. > Ubuntu 6.06 (Dapper) uses fail2ban-0.6.0-3.deb > - Ubuntu 6.10 (Edgy) uses 0.6.1-8.deb > + Ubuntu 6.10 (Edgy) uses fail2ban-0.6.1-8.deb > Both are still vulnerable. > There is a very similar vulnerability reported here: > http://www.ossec.net/en/attacking-loganalysis.html#fail2ban > However, I am unsure whether this is specific to fail2ban version 0.8 -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- Denial of service through log injection in fail2ban https://bugs.launchpad.net/bugs/121374 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62759] Re: This extension is incompatible with Firefox 2.0b2
This issue had been closed in 1.0.2-2 in debian unstable (and now event in testing) -- so might be 1 step away from edgy -- This extension is incompatible with Firefox 2.0b2 https://launchpad.net/bugs/62759 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 81408] dapper fail2ban 0.6.0-3 0 do not ban
it reported empty IP? so the problem got resolved with newer version of fail2ban (0.6.1-8), correct? dapper version is way too oldish... -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- dapper fail2ban 0.6.0-3 0 do not ban https://launchpad.net/bugs/81408 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 81408] Re: dapper fail2ban 0.6.0-3 0 do not ban
> No the ip was filled. The problem is that when an ip is banned a few > seconds after it's unban. and that is with the same config file as it comes with edgy? what was bantime value option set to? > Ok so just put the edgy one under dapper. You are supposed to provide a long > term support so to have fully operationnel system for three years. > To me the problem is solved but I just wanted you to be informed. I am a Debian Developer and a maintainer of fail2ban for Debian I am too new to Ubuntu way to handle things -- I am not sure if that is a good practice to have complete backport from next release propagate into the previous one, especially such elderly one. I would need to check if there are any specific instructions on that.. -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- dapper fail2ban 0.6.0-3 0 do not ban https://launchpad.net/bugs/81408 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 81408] Re: dapper fail2ban 0.6.0-3 0 do not ban
> >and that is with the same config file as it comes with edgy? >what was > >bantime value option set to? > it was set to -1. Yes it worked with the edgy conf file. I have not tested > dapper conf with edgy fail2ban. interesting permanent banning was added in 0.6.1: - Added permanent banning. Set banTime to a negative value to enable this feature (-1 is perfect). Thanks to Mannone so dapper version 0.6.0-3 is not intended to have that one I checked dapper version and it has it set to 600, so you must have used config from newer version (or changed manually) -- so it is not fail2ban's fault :-P > Ok i understand that. Why not trying to ake the last stable version of > fail2ban and to make a deb file from it and to make some test on it > after that. Maybe that is an option. well - do you mean 0.6.2? I don't think that such a jump (from 0.6.0 to 0.6.2) would be ok... may be someone who knows ubuntu policies better can correct me and do that for fail2ban... in any case - I think that people should use 0.7.x branch of fail2ban which probably would become stable very soon (and it is the one which is present in Debian etch) -- it is better designed and organized. > I hope I was not too hard in my speaking. ( If that the case sorry I > didn't mean it.) that is ok -- emails are bad as for describing emotions and intent so I am trying to take them having positive intent as the base ;-) -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- dapper fail2ban 0.6.0-3 0 do not ban https://launchpad.net/bugs/81408 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66865] Re: Lacks support for other programs (VSFTPD)
vsftpd is present in the 0.7.x branch of fail2ban and was present in latest 0.6.x debian releases -- Lacks support for other programs (VSFTPD) https://launchpad.net/bugs/66865 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76662] Re: Preferences dialog is empty in Firefox
I am not sure if that is imagezoom extension problem since I remember having the same issue with another extension. For me - it opens fine on the 2nd try (after I close that first tiny one and click on preferences once again) -- could you confirm that it works for you the same way? -- Preferences dialog is empty in Firefox https://launchpad.net/bugs/76662 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76663] Re: Removing mozilla-imagezoom corrupts Firefox's global configuration
can't confirm - don't experience the same effect. it might be helpful if you include what versions of firefox/imagezoom you are experiencing the problem with (doesn't ubuntu has some standard way to report bugs similar to debian's reportbug?) -- Removing mozilla-imagezoom corrupts Firefox's global configuration https://launchpad.net/bugs/76663 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791981] Re: X Server session crash for "No space left on device"
exactly the same issue as for Ben Echols on a Debian system with recent nvidia drivers. Initially I suspected some racing within systemd, thus filed (and later closed for now) https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=945158 which has supporting documentation. Did not find a workaround yet, besides making sure that laptop is fully suspended before closing the lid. Here is the relevant diff of journalctl output (with dates etc replaceD) between two sessions (-good, +bad) which highlights the disconnect Ben was talking about and then "out of cheese" error: - lena gnome-shell[]: Window manager warning: Overwriting existing binding of keysym 60 with keysym 2f7259c9 (keycode 31). + lena systemd-logind[]: Lid closed. + lena gsd-color[]: failed to set screen _ICC_PROFILE: Failed to open file “/home/yoh/.local/share/icc/edid-aae8f9ad98a49dd9b5e20a8dfbf85689.icc”: Permission denied + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-0: disconnected + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-0: Internal DisplayPort + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-0: 2660.0 MHz maximum pixel clock + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-1: disconnected + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-1: Internal DisplayPort + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-1: 2660.0 MHz maximum pixel clock + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-2: disconnected + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-2: Internal TMDS + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-0: disconnected + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-0: Internal DisplayPort + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-0: 2660.0 MHz maximum pixel clock + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-1: disconnected + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-1: Internal DisplayPort + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-1: 2660.0 MHz maximum pixel clock + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-2: disconnected + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-2: Internal TMDS + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock + lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): lena systemd[]: Reached target Sleep. lena systemd[]: Starting NVIDIA system suspend actions... lena suspend[]: nvidia-suspend.service ... lena acpid[]: 1 client rule loaded + lena /usr/lib/gdm3/gdm-x-session[]: (EE) modeset(G0): failed to set mode: No space left on device + lena /usr/lib/gdm3/gdm-x-session[]: (EE) + lena /usr/lib/gdm3/gdm-x-session[]: Fatal server error: + lena /usr/lib/gdm3/gdm-x-session[]: (EE) EnterVT failed for gpu screen 0 + lena /usr/lib/gdm3/gdm-x-session[]: (EE) + lena /usr/lib/gdm3/gdm-x-session[]: Please consult the The X.Org Foundation support + lena /usr/lib/gdm3/gdm-x-session[]: at http://wiki.x.org + lena /usr/lib/gdm3/gdm-x-session[]: for help. + lena /usr/lib/gdm3/gdm-x-session[]: (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. + lena /usr/lib/gdm3/gdm-x-session[]: (EE) + lena systemd[]: Starting Refresh fwupd metadata and update motd... + lena fwupdmgr[]: Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz ... lena avahi-daemon[]: Leaving mDNS multicast group on interface wlp82s0.IPv4 with address 10.31.123.112. - lena /usr/lib/gdm3/gdm-x-session[]: (II) event1 - Sleep Button: is tagged by udev as: Keyboard - lena /usr/lib/gdm3/gdm-x-session[]: (II) event1 - Sleep Button: device is a keyboard + lena /usr/lib/gdm3/gdm-x-session[]: (EE) Server terminated with error (1). Closing log file. lena avahi-daemon[]: Interface wlp82s0.IPv4 no longer relevant for mDNS. ** Bug watch added: Debian Bug tracker #945158 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945158 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791981 Title: X Server session crash for "No space left on device" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791981] Re: X Server session crash for "No space left on device"
Filed a question within nvidia forum: https://devtalk.nvidia.com/default/topic/1066963/linux/if-laptop-lid-is- closed-during-suspend-quot-failed-to-set-mode-no-space-left-on-device- quot-upon-resume/post/5406357/ so far no closure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791981 Title: X Server session crash for "No space left on device" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 954453] Re: fail2ban in precise defaults to gamin, does not work
inotify backend had already merged into upstream's master branch post 0.8.6 release but there were no upstream release yet. There is an issue reported against functionality of this backend: https://github.com/fail2ban/fail2ban/issues/44 and it would be great if you could give it some testing. I have updated 'Features' page to refer to github's issues page which would have more information On Mon, 21 May 2012, alp wrote: > Some background: > RedHat ported fail2ban to use pyinotify instead of gamin which seems the > way forward (https://bugzilla.redhat.com/show_bug.cgi?id=658849 and > https://bugzilla.redhat.com/show_bug.cgi?id=551895). > Switching to pyinotify is apparently on the fail2ban roadmap for 0.9.0 > at http://www.fail2ban.org/wiki/index.php/Features so it's probably not > worth backporting this feature at this point. > As such the gamin patch should be a reasonable stopgap measure. > ** Bug watch added: Red Hat Bugzilla #658849 >https://bugzilla.redhat.com/show_bug.cgi?id=658849 > ** Bug watch added: Red Hat Bugzilla #551895 >https://bugzilla.redhat.com/show_bug.cgi?id=551895 -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954453 Title: fail2ban in precise defaults to gamin, does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/954453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66727] Re: Can't boot ubuntu/sparc64 if installed on mirroring md device with installer
I wonder what was the resolution here -- I am pretty much in 100% identical situation ;-) so if anyone could comment on -- I would appreciate! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/66727 Title: Can't boot ubuntu/sparc64 if installed on mirroring md device with installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/silo/+bug/66727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 956071]
(In reply to comment #3) > Does debian carry any patches? yes. See http://patch-tracker.debian.org/package/xorg-server/2:1.12.3-1 for details > if so, can you reproduce this with a vanilla X > server? I just vt-switched about 50 times with 1.12.99.902 but it doesn't > happen here. Never happened for me while switching VT. although I do not do that regularly... ok -- switched to VT 1 and back (Ctrl-Alt-1 and then randomly Alt-left/right till reaching X) quite a few times (around 10) -- no problem. With suspend I think I would have experienced it by then. Also, may be of relevance: if X crashes during suspend and I end up again at the kdm login prompt -- I would still have my 'half-moon' light blinking until I switch to e.g. VT 1 -- then it would finally suspend. > What desktop environment is this? happened originally with KDE4 + awesome... now it is XFCE + awesome -- the same story > something is trying to change the property > after the VT switch, so I'd need a similar setup here. my ~/.xsession has awesome & sleep 3 xfce4-session > Finally, if you can reproduce it easily, can you try running X through > valgrind > to see if you get any invalid writes? It is reproducible on around 5-10th occasion on random -- never yet tried to cause it on purpose -- I thought to give it excessive troubleshooting one day... if I get a moment I will run it through valgrind... although if it is some kind of a race condition between threads, it might not get triggered -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/956071 Title: Xorg crashed with SIGSEGV in XIGetDeviceProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/956071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 956071]
(In reply to comment #6) > yaroslav: could you try reverting the synaptics driver to, say, 1.5.99.902 or > .903 and test if you can reproduce the crash? A similar crash has been filed > on > ubuntu, and there it was discovered that reverting to that version stopped the > crashes. yes -- I saw those and also thought to revert BUT IIRC those ubuntu reports were primarily about (similar) crash upon resume, while mine is consistently occurring upon suspend; so I was not sure if that would be it. Today, while connected via usb-serial port thought to replicate to get better interactive gdb session so I could possibly figure out more but tried around 10 times to suspend/resume -- didn't happen :-/ heh-- but I guess it might be worth anyways -- if it crashes, I would get to the same point if I would be ready to debug ;) if not -- then you might not hear from me for a week or so since as I said it would be difficult to say for sure that it helped without waiting for so long ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/956071 Title: Xorg crashed with SIGSEGV in XIGetDeviceProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/956071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 956071]
ok -- downgrade to xserver-xorg-input-synaptics 1.5.99.902-1 (debian package) built with -O0 -- no crashes within a week -- so I guess it is indeed synaptics to blame. If I find a chance I will "upgrade" to 1.6.0 and see if crash comes back... I would hate to do such silly bisection but I guess it would be better than doing nothing and simply waiting ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/956071 Title: Xorg crashed with SIGSEGV in XIGetDeviceProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/956071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 956071]
I have upgraded xorg server quite a while ago and it had not resolved the issue at that time. Just for the completness: /var/log/dpkg.log.1:2012-07-03 09:53:04 status installed xserver-xorg:amd64 1:7.6+13 /var/log/dpkg.log.1:2012-07-03 09:53:04 status installed xorg:amd64 1:7.6+13 /var/log/dpkg.log.1:2012-07-11 14:56:36 status installed xserver-xorg-core:amd64 2:1.12.1.902-1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-video-vesa:amd64 1:2.3.1-1+b1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-video-intel:amd64 2:2.19.0-4 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-video-fbdev:amd64 1:0.4.2-4+b3 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-video-dummy:amd64 1:0.3.5-2+b1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-video-apm:amd64 1:1.2.3-3 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-input-void:amd64 1:1.4.0-1+b1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-input-synaptics:amd64 1.6.2-1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-input-evdev:amd64 1:2.7.0-1+b1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg:amd64 1:7.7+1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xorg:amd64 1:7.7+1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-dev:amd64 2:1.12.1.902-1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xorg-dev:all 1:7.7+1 /var/log/dpkg.log.1:2012-07-16 11:43:34 status installed xserver-xorg-core-dbg:amd64 2:1.12.1.902-1 /var/log/dpkg.log.1:2012-07-16 11:43:34 status installed xserver-xorg-video-intel-dbg:amd64 2:2.19.0-4 /var/log/dpkg.log.1:2012-07-21 15:35:55 status installed xserver-xorg-core:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-21 15:35:55 status installed xserver-xorg-core-dbg:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-21 15:35:55 status installed xserver-xorg-dev:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-25 09:18:55 status installed xserver-xorg-dev:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-25 09:18:55 status installed xserver-xorg-core:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-25 09:18:57 status installed xserver-xorg-core-dbg:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-25 09:19:58 status installed xserver-xorg-dev:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-25 09:19:58 status installed xserver-xorg-core:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-25 09:20:00 status installed xserver-xorg-core-dbg:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-26 20:15:33 status installed xserver-xorg-core-dbg:amd64 2:1.12.3-1 /var/log/dpkg.log:2012-08-08 23:12:08 status installed xserver-xorg-input-synaptics:amd64 1.6.2-1 /var/log/dpkg.log:2012-08-09 11:00:56 status installed xserver-xorg-input-synaptics-dev:all 1.5.99.902-1 /var/log/dpkg.log:2012-08-09 11:00:56 status installed xserver-xorg-input-synaptics:amd64 1.5.99.902-1 /var/log/dpkg.log:2012-08-15 12:45:23 status installed xserver-xorg-input-synaptics-dev:all 1.6.2+git44-ge28575b-1~yarik0 /var/log/dpkg.log:2012-08-15 12:45:23 status installed xserver-xorg-input-synaptics:amd64 1.6.2+git44-ge28575b-1~yarik0 as you see I have built and installed current master of the synaptics but had no chance yet to restart X to see if crash comes back... I will report back whenever that happens -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/956071 Title: Xorg crashed with SIGSEGV in XIGetDeviceProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/956071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 954453] Re: fail2ban in precise defaults to gamin, does not work
On Tue, 22 May 2012, Mark Schroeder wrote: > I'm not sure what you want tested. I know that polling is guaranteed to work ;) sorry if I wasn't clear -- I wondered if you could test current development version which is in git which should use inotify by default (to replace gamin)... but I guess it might be not that trivial, so nevermind -- thanks for the feedback anyways. > I briefly tried gamin with ssh, and it worked, at least for a bit. > Another friend tried it and reports that his postfix rules > did not result in a ban as expected, though. > I then put it back to 'polling', and that failed to be effective > until I rebooted and restarted the fail2ban service. > At that point, it seemed to work (with polling) again. > - > Mark Schroeder -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954453 Title: fail2ban in precise defaults to gamin, does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/954453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 954453] Re: fail2ban in precise defaults to gamin, does not work
On Thu, 07 Jun 2012, Mark Schroeder wrote: > I'm a developer and at least aware that there is additional > complexity to wrap a standard "tar" source into an Ubuntu .deb. > I see these: > http://packages.ubuntu.com/precise/fail2ban (standard, ubuntu wrapped) > https://github.com/fail2ban/fail2ban (development) yes -- correct git url > patches applied, not sure if I have all the build dependencies, etc. I don't think there is any build-dependencies besides run dependencies which is pretty much just python ;) > And are the Ubuntu patches correct for the development version? dunno -- I am not tracking them that closely and in Debian I have not that many patches: $> quilt series deb_manpages_reportbug ... and that one could be dropped (it would conflict since I also changed those manpages in the master branch) well... what if I simply generate a package for you to try... damn github refuses to accept my lovely file so here you go: http://www.onerussian.com/tmp/fail2ban_0.8.6~+git69-gb4099da-1_all.deb and then gpg signature to verify authenticity http://www.onerussian.com/tmp/fail2ban_0.8.6~+git69-gb4099da-1_all.deb.asc no guarantees though... didn't even test it anyhow I have made it versioned 0.8.6~ (which is before 0.8.6) so it would then automatically upgraded to 0.8.6 happen you decide to upgrade your system > If you can confirm the URLs above are the right starting points > for the development version, and outline the steps to build a > package .deb for Ubuntu, I'll try it if I have time. > It will take a while. Polling is working and it isn't a priority > for me right now. -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954453 Title: fail2ban in precise defaults to gamin, does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/954453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 346735] Re: FTBFS in jaunty
I've tried to build pymvpa 0.4.0-1 with Python 2.6 in Jaunty, that's the result: o boy -- 0.4.0 is way too old -- please use 0.4.7 -- builds for it for jaunty are available from neurodebian repository, see http://neuro.debian.net/pkgs/python-mvpa.html On Wed, 10 Aug 2011, Bug Watch Updater wrote: > ** Changed in: pymvpa (Debian) >Status: New => Fix Released -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/346735 Title: FTBFS in jaunty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pymvpa/+bug/346735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 802110] [NEW] package python-mvpa (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/mvpa-prep-fmri', which is also in package python-mvpa-lib 0:0.4.2-1
0.4.2 ... I do not remember already how life was back then... just use our http://neuro.debian.net repository (visit site for details), remove python-mvpa and python-mvpa-lib you got and install 0.4.7 from neurodebian. Enjoy On Sun, 26 Jun 2011, GregoryHuey wrote: > Public bug reported: > A popup dialog box gave me this error message: > E: /var/cache/apt/archives/python-mvpa_0.4.2-1_all.deb: trying to > overwrite '/usr/bin/mvpa-prep-fmri', which is also in package python- > mvpa-lib 0 -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802110 Title: package python-mvpa (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/mvpa-prep-fmri', which is also in package python-mvpa-lib 0:0.4.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pymvpa/+bug/802110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 515224] Re: iptables creation error on Ubuntu 8.10
it just needs banaction = iptables-multiport which is the default since 0.7.6-2 On Fri, 29 Jul 2011, Daniel T Chen wrote: > 8.10 is EOL, marking as rejected > ** Changed in: fail2ban (Ubuntu) >Status: New => Won't Fix > ** Changed in: iptables (Ubuntu) >Status: New => Invalid -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/515224 Title: iptables creation error on Ubuntu 8.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/515224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 719214] [NEW] import fails in natty
oy -- we are still ok in Debian, phew On Tue, 15 Feb 2011, Michael Vogt wrote: > Public bug reported: is public also fixes them in Ubuntu? -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719214 Title: import fails in natty -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 752443] Re: package python-mvpa (not installed) failed to install/upgrade: Versuche, »/usr/bin/mvpa-prep-fmri« zu überschreiben, welches auch in Paket python-mvpa-lib 0:0.4.2-1 ist
*** This bug is a duplicate of bug 695351 *** https://bugs.launchpad.net/bugs/695351 Hint: get recent package of pymvpa in 0.4.x series pre-built for Ubuntus on http://neuro.debian.net Enjoy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/752443 Title: package python-mvpa (not installed) failed to install/upgrade: Versuche, »/usr/bin/mvpa-prep-fmri« zu überschreiben, welches auch in Paket python-mvpa-lib 0:0.4.2-1 ist -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858446] [NEW] majority of packages get into "unknown" instead of e.g. universe
Public bug reported: If you visit https://popcon.ubuntu.com/ and download "universe" (https://popcon.ubuntu.com/universe/by_inst.gz) and "unknown" (https://popcon.ubuntu.com/unknown/by_inst) you will see that many packages which are in universe (e.g., git-annex) are not present in "universe" but rather in "unknown": universe: $> zcat <(wget -q -O- https://popcon.ubuntu.com/universe/by_inst.gz) | nl | tail 18208 18197 mythbuntu-diskless-client 1 0 1 0 0 (Michael Haas) 18209 18198 roxen4-doc 1 0 0 0 1 (Turbo Fredriksson) 18210 18199 zorroutils 1 0 1 0 0 (Aurélien GÉrÔme) 18211 18200 fai-nfsroot0 0 0 0 0 (Thomas Lange) 18212 18201 gforge-theme-starterpack 0 0 0 0 0 (Christian Bayle) 18213 18202 libslurm11-dev 0 0 0 0 0 (Gennaro Oliva) 18214 18203 ppmtofb0 0 0 0 0 (Chris Lawrence) 18215 18204 rhkbf 0 0 0 0 0 (Dmitry E. Oboukhov) 18216 -- 18217 18204 Total 447833653 271213 332353797 22489 115186154 $> zcat <(wget -q -O- https://popcon.ubuntu.com/universe/by_inst.gz) | grep git-annex unknown: $> wget -q -O- https://popcon.ubuntu.com/unknown/by_inst | nl | tail 296594 296583 zope-zaaplugins0 0 0 0 0 (Unknown) 296595 296584 zope-zattachmentattribute 0 0 0 0 0 (Unknown) 296596 296585 zope-zpatterns 0 0 0 0 0 (Unknown) 296597 296586 zope-zshell0 0 0 0 0 (Unknown) 296598 296587 zope2.11-sandbox 0 0 0 0 0 (Unknown) 296599 296588 zope2.6-verbosesecurity0 0 0 0 0 (Unknown) 296600 296589 zope2.7-sandbox0 0 0 0 0 (Unknown) 296601 296590 zopex3-sandbox 0 0 0 0 0 (Unknown) 296602 -- 296603 296590 Total 1319985827 2097898 913982492 122381 403783056 $> wget -q -O- https://popcon.ubuntu.com/unknown/by_inst | nl | grep git-annex 23764 23753 git-annex747 6 740 1 0 (Unknown) 129581 129570 elpa-magit-annex 5 0 5 0 0 (Unknown) 138155 138144 elpa-git-annex 4 0 4 0 0 (Unknown) 168880 168869 git-annex-standalone 2 0 2 0 0 (Unknown) whenever git-annex is in universe: https://packages.ubuntu.com/disco /git-annex NB original motivation for inspecting ubuntu popcon is because in NeuroDebian we saw slow decrease (but not complete disappearance) of popcon submissions from Ubuntu systems: see http://neuro.debian.net/popularity.html#popularity-contest . We know that it doesn't reflect reality since the number of "subscriptions" (downloads of our APT configuration lines) is dominated by Ubuntu boxes: http://neuro.debian.net/popularity.html#repository-subscriptions . So there is yet another mystery to be resolved. ** Affects: popularity-contest (Ubuntu) Importance: Undecided Status: New ** Tags: neurodebian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858446 Title: majority of packages get into "unknown" instead of e.g. universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popularity-contest/+bug/1858446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858446] Re: majority of packages get into "unknown" instead of e.g. universe
regarding the original issue + NB: additional point of information: $> zgrep neurodebian-popularity-contest by_inst* by_inst:14151 neurodebian-popularity-contest 726 341 1 681 (Neurodebian Team) by_inst_ubuntu_unknown.gz:18478 neurodebian-popularity-contest 1326 0 29 0 1297 (Unknown) so there is ~2k popcon submitters on ubuntu, but for some submissions get into unknown, and we receive probably only 10% of them at our popcon server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858446 Title: majority of packages get into "unknown" instead of e.g. universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popularity-contest/+bug/1858446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
