On 25/06/12 14:34, Phillip Susi wrote:
> On 6/25/2012 4:25 AM, Dmitrijs Ledkovs wrote:
>> Your decision whether you upload into Debian experimental or unstable
>> should not be affected by other derivative distribution policies. You
>> can request syncing packages from experimental into Ubuntu, but
On 6/25/2012 4:25 AM, Dmitrijs Ledkovs wrote:
Your decision whether you upload into Debian experimental or unstable
should not be affected by other derivative distribution policies. You
can request syncing packages from experimental into Ubuntu, but the
package will still land in Ubuntu's new que
On Sun, Jun 24, 2012 at 09:14:47PM -0400, Phillip Susi wrote:
> Exactly. I was planning on announcing it once it's in the archive to call
> for testing and feedback. The usage of experimental is still unclear to me.
If it's of release quality, then use unstable. If it needs wider
testing before
On 25/06/12 02:14, Phillip Susi wrote:
>> Generally, Debian packages stable releases of software. At the current
>> state is this package ready for unstable or better suited for
>> experimental? Has it seen wider testing / user base? (e.g. did you post
>> an announce to ext-dev mailing lists? LWN.n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/24/2012 07:41 PM, Dmitrijs Ledkovs wrote:
>> There is already an ext4-specific (depends on creation with -O extent)
>> e4defrag
>> tool in e2fsprogs since 1.42~WIP-2011-07-02-1. Is there a reason you would
>> use
>> one tool over the other?
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/24/2012 07:40 PM, Dmitrijs Ledkovs wrote:
> Let me rephrase.
>
> Is upstream aware of the above bugs which affected the last version of
> defrag in debian, which were not fixed in the upstream code?
They appear to fall into 3 categories: ftbs,
On 24/06/12 23:58, Nicholas Breen wrote:
> On Sun, Jun 24, 2012 at 02:31:23PM -0400, Phillip Susi wrote:
>> On 06/24/2012 12:00 PM, Roger Leigh wrote:
>>> This was always a tool which needed to be used with great caution,
>>> and was removed for good reason. Is this safe to use with all
>>> ext2,
Dear Phillip,
Thank you for replying to all the comments and resolving issues quickly.
I haven't checked them yet, but I am sure they are fine now.
See further comments:
On 24/06/12 03:50, Phillip Susi wrote:
>
>> Bugs there were closed due to removing the package from the archive
>> should be
On Sun, Jun 24, 2012 at 02:31:23PM -0400, Phillip Susi wrote:
> On 06/24/2012 12:00 PM, Roger Leigh wrote:
> > This was always a tool which needed to be used with great caution,
> > and was removed for good reason. Is this safe to use with all
> > ext2, ext3 and ext4 filesystems?
>
> Obviously th
On Mon, 25 Jun 2012 00:48:37 +0300, Phillip Susi wrote:
How about at least an overview of the complaints that e2fsck had? And I
It's output went off the scroll buffer, sorry. But it was quite a long
list.
assume that e2defrag finished without error?
Yes, at least I saw nothing in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/24/2012 05:25 PM, Eugene Paskevich wrote:
> I wasn't very cautious to preserve any data before or after the defrag,
> even more I've killed the file system already.
> Sorry, I won't be useful in debugging.
How about at least an overview of the c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/24/2012 04:36 PM, Eugene Paskevich wrote:
> Just my 2 cents...
> Tried to use it on my non-critical ext3 FS. The FS structure was corrupted,
> fsck recovered some data (about 1%) into lost+found, 80% of data is lost w/o
> any trace.
> Well, it's
On Sun, 24 Jun 2012 19:00:10 +0300, Roger Leigh
wrote:
This was always a tool which needed to be used with great caution,
and was removed for good reason. Is this safe to use with all
ext2, ext3 and ext4 filesystems?
Just my 2 cents...
Tried to use it on my non-critical ext3 FS. The FS str
On Mon, 25 Jun 2012 00:13:15 +0300, Phillip Susi wrote:
Could you provide more details? Also an e2image of the fs ( preferably
before defrag ) would be helpful in debugging.
I wasn't very cautious to preserve any data before or after the defrag,
even more I've killed the file system already
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/24/2012 12:00 PM, Roger Leigh wrote:
> Have you taken over upstream maintainership as well?
Yes.
> This was always a tool which needed to be used with great caution,
> and was removed for good reason. Is this safe to use with all
> ext2, ext3
On Sat, Jun 23, 2012 at 05:03:39PM -0400, Phillip Susi wrote:
> I am looking for a sponsor for my package "e2defrag". This package used to
> be known as defrag, and was removed from the archive back in 2008 due to
> being abandoned by its authors and rotting for many years. I have taken over
> ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/23/2012 07:27 PM, Dmitrijs Ledkovs wrote:
> The ITP was not sent to the debian-devel mailing list. Please use
> report-bug in the future or add pseudo-header:
> X-Debbugs-CC: debian-de...@lists.debian.org
>
> Please forward your ITP to debian-de
Hello Phillip,
Thanks for picking up this package.
Here are some comments
== ITP ==
The ITP was not sent to the debian-devel mailing list. Please use
report-bug in the future or add pseudo-header:
X-Debbugs-CC: debian-de...@lists.debian.org
Please forward your ITP to debian-devel.
== bugs ==
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "e2defrag". This package used to be
known as defrag,
and was removed from the archive back in 2008 due to being abandoned by its
authors and r
19 matches
Mail list logo
