Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debian jessie: no zfs 0.6.5.3 #181

Closed
Pentium100MHz opened this issue Nov 2, 2015 · 129 comments
Closed

Debian jessie: no zfs 0.6.5.3 #181

Pentium100MHz opened this issue Nov 2, 2015 · 129 comments

Comments

@Pentium100MHz
Copy link

Hi,
The latest version available for Debian Jessie is 0.6.5.2-2. 0.6.3 Was released some time ago, why isn't it in the repository?

@FransUrbo
Copy link
Contributor

Because I've been busy with moving and personal issues and haven't got a new home for my development environment yet.

I'm working on it, and with a little bit of luck, I'll get something in the next few weeks.

@amitie10g
Copy link

Regarding 0.6.5.3, keep in mind openzfs/spl#490 (spl-dkms build error with linux 2.6.32, under RHEL/Fedora/Centos).

Ubuntu users have 0.6.5.3 available in PPA already. Please test and report any issues (don't forget to make snapshots!).

@amitie10g
Copy link

There is another problem by releasing spl-dkms 0.6.5.3 but not zfs-dkms 0.6.5.3 together. I accidentally updated spl-dkms, and I noticied that when zfs-dkms 0.6.5.2 failed to build. So, I needed to downgrade spl-dkms and the both spl-dkms and zfs-dkms 0..6.5.2 built successfuly.

As I mentioned in other issues, DON'T update dkms packages if the both spl-dkms and zfs-dkms don't have the same version available, and always make snapshots!

@FransUrbo, do the best you can do, but please fix this issue as soon as possible.

@ggzengel
Copy link

@FransUrbo how are you? What's about your DevEnv?

@mailinglists35
Copy link

@FransUrbo any ETA of packaging & releasing 0.6.5.4? I see just four issues with milestone 0.6.5.4 (in zfs; spl have none) and all they seem to have a patch merged in master.

@behlendorf
Copy link
Member

@mailinglists35 0.6.5.4 isn't quite tagged yet, but it should be soon. As for the Debian packaging it's my understanding that @FransUrbo's development environment isn't currently available so you may need to roll your own 0.6.5.4 when it's tagged.

@FransUrbo
Copy link
Contributor

It doesn't look like it's going to happen in the forceable future :(

I'm still in the process of migrating to the UK and all my stuff (especially the computer/development hardware) is in storage. I had a small chance of having parts of it at a friends house, but that didn't happen, so I'll have to wait until the move is complete. How long that will take in practice, is anyones guess and mine is "hopefully no longer than six months, at the worst a year"… :(

So don't hold your breath for a new version :(

Besides, Debian GNU/Linux is hopefully soon going to release it into the repository, so with a little luck, we'll have it in the correct repository "soon".

It's finally migrated to the "New" queue (after laying in "Incoming" for years :) - https://ftp-master.debian.org/new.html. Since the two major showstoppers (the license and the package names) have been resolved, "The General Opinion™) is that it will now be accepted as soon as the FTP maintainers have time to review it. How long THAT will take is anyones guess (considering that they took two years to deal with it, which they really didn't - "The Leader" had to step in and more or less force it into "New").

Also have a look at the official ticket about getting ZoL into Debian GNU/Linux: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447 (it's long and full of "opinions" and "conjectures" - some of them wrong IMO, but it's something).

Considering that it will NEVER be accepted into Jessie (it's released and no new software is going in there), I MIGHT be supporting Jessie in the ZoL name/repositories once my hardware is up and running again, but that'll be a decision I'll take when that day comes…

FYI, IF someone in the South West UK (London and/or surroundings) have an interest to sponsor this job (providing server space and 'Net access for my servers so I can keep doing packages), I'm all for discussing the issue (do this in private if so). Otherwise, everyone just have to wait until I've solved it myself.

@lnxbil
Copy link

lnxbil commented Jan 3, 2016

Only for reference to others and until something official is available:

I switched to use the ZFS packages provided by Proxmox, which is an addition to Debian Jessie (amd64 only) using their Ubuntu LTS 4.2 kernel. It only adds a few packages and works great.

@FransUrbo
Copy link
Contributor

Version 0.6.5.4-1 was accepted into Unstable on January 10.

Eventually, I might do a couple of Jessie packages, but don't hold your breath. I'm still in the process of relocating to the UK, and I don't expect to be up and running before summer :(.

@kernelOfTruth
Copy link

I feel ya,

moving is a PITA, just did a move at the end of December and things still aren't working as before :/

@tobox
Copy link

tobox commented Jan 19, 2016

@FransUrbo I cannot find any 0.6.5.4 packages in Debian Unstable for amd64.
Were you talking about Ubuntu Unstable? Or am I doing something wrong?

@ggzengel
Copy link

Only spl-linux is in unstable and now testing. The most problematic package zfs-linux is still waiting.

https://qa.debian.org/[email protected]

@behlendorf @happyaron Isn't it possible to put the packages from Aron XU inside ZoL repository?

@mailinglists35
Copy link

@FransUrbo is it difficult to transfer the know-how to somebody else? or did you not find someone to replace you during this period? it's quite frustrating to know the packaging depends on a single person and that person is going to be unavailable for such a long time...

@fajarnugraha
Copy link
Contributor

Try http://list.zfsonlinux.org/pipermail/zfs-discuss/2016-January/024430.html

Note that it's only intended as temporary workaround

@markdesouza
Copy link

@FransUrbo feel for you, moving let alone immigrating is a long and painful process.

With regard to the packaging, I might be missing something but couldn't the building of packages just be done on EC2? From memory archive.zfsonlinux.org is already hosted on S3. Whilst slow, a micro.t2 instance should be able to package and upload the package in a reasonable timeframe and is free for a year.

Also if the debian packages are not going to be upgraded in the short term, it might be a good idea to put a note on http://zfsonlinux.org/debian.html

@amitie10g
Copy link

So, I'm trying the packages from PPA (0.6.5.4-1). I'll tell if them work properly.

@FransUrbo
Copy link
Contributor

I've said it before, but I'll say it again: ANYONE caught using the Ubuntu (or any other package not intended to Debian GNU/Linux proper) packages will be completely on their own!! I just can't stress that enough!! I will not in any way help when problems occurs!

@happyaron
Copy link

I can help on putting my package on zol.org, just want to know how the binaries are published. Well I'm currently trying hard to push the package into Debian's official repo but it appears the work isn't progressing well.

@nikil
Copy link

nikil commented Feb 4, 2016

Aron - I see that the the ZFS package is no longer listed under "new" in the Debian master FTP. Is that because it was rejected? If so can you say why?

FransUrbo if you could assist Aron is publishing his packages that would be great. I hope your move is going OK.

@happyaron
Copy link

Debian FTP Team found some files are licensed under BSD license but those ones were not included in debian/copyright file, so it was rejected.

@nikil
Copy link

nikil commented Feb 4, 2016

Sounds like fun! But that doesn't sound like fundamental a blocking issue? It's just a matter of jumping through all their hoops? Granted it took them 3 weeks to find this issue...

@AceSlash
Copy link

AceSlash commented Feb 8, 2016

@FransUrbo Very sorry about your issues. In the meantime, do you have some instruction on how you made the builds/test for the Debian packages? Or can you tell us what do you need to generate the packages? If the issue is server environment only, maybe we could give you access to some hardware.

@mailinglists35
Copy link

Does anyone else finds this ridiculous that the packaging depends on one person
who happens to be unavailable for a long time and he has no replacement nor has
published his work so anyone can take over until he recovers?!

Sent using CloudMagic [https://cloudmagic.com/k/d/mailapp?ct=pi&cv=7.2.19&pv=8.4]
On Mon, Feb 8, 2016 at 11:37 pm, AceSlash [email protected] wrote:
@FransUrbo [https://github.com/FransUrbo] Very sorry about your issues. In the meantime, do you have some instruction on
how you made the builds/test for the Debian packages? Or can you tell us what do
you need to generate the packages? If the issue is server environment only,
maybe we could give you access to some hardware.


Reply to this email directly or view it on GitHub
[https://github.com//issues/181#issuecomment-181523451] .[https://github.com/notifications/beacon/AB9YnjvtFDfMQKN3OB2gnYsEirvMe38tks5piPQLgaJpZM4GaFDR.gif]

@nikil
Copy link

nikil commented Feb 9, 2016

@happyaron I believe this page has some instructions as to how the packages are published: https://github.com/zfsonlinux/pkg-zfs

@FransUrbo Please help Aron with uploading his packages. If it may take months before a) they are accepted into Debian, or b) you can personally build and upload a new version of Debian ZFS, it would really help out your users to assist Aron with getting his already built packages out sooner.

@markdesouza
Copy link

@mailinglists35 Whilst I do agree with that the situation is not ideal, I think we should thank @FransUrbo for the work he has done in the past.

@behlendorf Is there a reason why Debian packaging is handled out of the make branch. Can deb packaging not be included in the main project?

@lnxbil
Copy link

lnxbil commented Feb 10, 2016

@behlendorf That is a really good question. Normally it only consists of a directory named debian.

@azeemism
Copy link

azeemism commented Apr 4, 2016

Here is an example of the extras that @FransUrbo may consider putting into his Debian releases (openzfs/zfs#4474 (comment)). This take not only expertise and experience, but also familiarity with ZoL and current issues. This type of active package maintenance is something that can only come from ZoL. I hope for easier maintenance in the future @fallenguru #181 (comment) suggestions can be utilized with this and other fixes/extras used for Debian.

@FransUrbo
Copy link
Contributor

How many really, really want Wheezy packages of the 0.6.5.6 version?

Don't reply, just "Like" this comment (upper right corner there's a smiley - click that and there's a "Like").

I'm not promising anything anyway, but it will give me an idea how many want it. Please only "Like" if you consider this very (or "extremely") important!

@FransUrbo
Copy link
Contributor

Update: 0.6.5.6-1 for Jessie just pushed to the repo. Should be available as soon as S3 syncs up (can take up to an hour).

I'll start the Wheezy package tomorrow. Enjoy!

@nicko88
Copy link

nicko88 commented Apr 5, 2016

I think I'll switch my servers to Ubuntu 16.04 when it's out since they will be the first distribution to support ZFS

It's not the first I wouldn't say. Proxmox has supported ZFS out of the box and with all the latest updates and such. They are essentially just Debian as well.

Heck, you can even install Proxmox to a ZFS root pool right from the installer ISO through the installer GUI. Seems pretty well supported and baked in.

@da-tex
Copy link

da-tex commented Apr 5, 2016

Great news, @FransUrbo! I'm waiting for this update, because of a kernel panic issue.

Is it really available now? At the moment my machine (debian jessie) still doesn't find it.

@nicko88
Copy link

nicko88 commented Apr 5, 2016

Yeah, it's up since last night.

root@nick-server:~# apt-get upgrade -V
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
libnvpair1 (0.6.5.2-2 => 0.6.5.6-1)
libuutil1 (0.6.5.2-2 => 0.6.5.6-1)
libzfs2 (0.6.5.2-2 => 0.6.5.6-1)
libzpool2 (0.6.5.2-2 => 0.6.5.6-1)
spl (0.6.5-pve3~jessie => 0.6.5.6-1)
spl-dkms (0.6.5-1 => 0.6.5.6-1)
zfs-dkms (0.6.5.2-2 => 0.6.5.6-1)
zfsutils (0.6.5.2-2 => 0.6.5.6-1)
8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 2,457 kB of archives.
After this operation, 122 kB of additional disk space will be used.

@FransUrbo
Copy link
Contributor

I just pushed the Wheezy packages as well. Give it an hour or so.

Enjoy!

@markdesouza
Copy link

@FransUrbo Well done and thanks for your hard work.....

@azeemism
Copy link

azeemism commented Apr 6, 2016

Note (0.6.5.6-1): Debian Jessie users may be thrown into BusyBox on system startup, if using ZFS as the root fs. see: #200.

I did not run into this issue under 0.6.5.2-2 Debian Jessie release.

@Fabian-Gruenbichler
Copy link

@FransUrbo Not sure whether to report this here, as a seperate issue in pkg-zfs or somewhere else (the pkg-spl repo does not have issues enabled)..

Is it possible you made an error when updating pkg-spl? The tag 'master/debian/jessie/0.6.5.6-1' seems to be based on the packaging for the last 0.6.4 release, and not the last 0.6.5 release.. The spl upstream part itself looks good to me, but the gbp.conf and changelog are plain wrong, and there are a lot of changes regarding the dkms and module packaging that I did not check in detail yet..

@FransUrbo
Copy link
Contributor

Checking out master/debian/jessie/0.6.5.6-1 gives me:

DebianZFS-Jessie-Devel-Released:/usr/src/pkg-spl# head debian/changelog
spl-linux (0.6.5.6-1) jessie; urgency=low

  * New upstream release

 -- Turbo Fredriksson <[email protected]>  Mon, 28 Mar 2016 17:12:52 +0200

spl-linux (0.6.4-1b) wheezy; urgency=low

  * Update the spl-dkms dkms config file to make sure it rebuilds the initrd
    if needed.

So the changelog is correct. However, you're right about the gbp.conf file. Oups! I'll do a new update, should be available "shortly".

DebianZFS-Jessie-Devel-Released:/usr/src/pkg-spl# grep ^upstream debian/gbp.conf
upstream-branch=spl-0.6.4
upstream-tag=spl-0.6.4

@FransUrbo
Copy link
Contributor

I'm going to close this now. Any other issues with the packages, please report a new issue on pkg-spl (or pkg-zfs respectivly).

@Fabian-Gruenbichler
Copy link

But that means that the following changelog entries from 0.6.4-1b..0.6.5-1 are silently dropped (and it seems, also the packaging changes that were included in those releases?):

spl-linux (0.6.5-1) jessie; urgency=low

  * New upstream release

 -- Turbo Fredriksson <[email protected]>  Thu, 17 Sep 2015 13:36:22 +0200

spl-linux (0.6.4-8-8ac6ff) jessie; urgency=low

  * Package zfs-modules-source needs to conflict and replace zfs-dkms
    and vise versa.
  * New upstream GIT version.

 -- Turbo Fredriksson <[email protected]>  Tue, 18 Aug 2015 12:29:48 +0200

spl-linux (0.6.4-7-4699d7) jessie; urgency=low

  * New upstream GIT version.

 -- Turbo Fredriksson <[email protected]>  Mon, 27 Jul 2015 17:54:47 +0200

spl-linux (0.6.4-6-37d7cd) jessie; urgency=low

  * New upstream GIT version.

 -- Turbo Fredriksson <[email protected]>  Sat, 18 Jul 2015 18:11:26 +0200

spl-linux (0.6.4-5-3c8216) jessie; urgency=low

  * New upstream GIT version.

 -- Turbo Fredriksson <[email protected]>  Fri, 26 Jun 2015 00:43:30 +0200

spl-linux (0.6.4-4-234536) jessie; urgency=low

  * New upstream GIT version.

 -- Turbo Fredriksson <[email protected]>  Thu, 11 Jun 2015 20:38:58 +0200

spl-linux (0.6.4-3-a876b0) jessie; urgency=low

  * New upstream GIT version.

 -- Turbo Fredriksson <[email protected]>  Thu, 11 Jun 2015 09:54:06 +0200

spl-linux (0.6.4-2-62e2eb) jessie; urgency=low

  * New upstream GIT version.
    + Remove module package stuff.

 -- Turbo Fredriksson <[email protected]>  Tue, 12 May 2015 14:18:13 +0200

The 0.6.5.6-1-wheezy spl-linux source package on archive.zfsonlinux.org does include all those changes and seems to be based on 0.6.5-1-wheezy, not 0.6.4-1b (the 0.6.5.6-1 wheezy tag does not seem to be pushed to pkg-spl by the way). Sorry for pestering you about this, I just want to make sure this was intentional and not by accident ;)

@mailinglists35
Copy link

https://tracker.debian.org/news/767706

zfs-linux (0.6.5.6-1) accepted in sid

@mailinglists35
Copy link

@FransUrbo do you plan on releasing dkms based on 0.6.5.8?

@FransUrbo
Copy link
Contributor

No. But Debian GNU/Linux will.

@janmuennich
Copy link

What about Wheezy? That is not supported by Debian.

@FransUrbo
Copy link
Contributor

Unless someone have the interest in creating their own repo, backporting the Debian GNU/Linux packages and maintain all that, Wheezy won't happen either :(

@janmuennich
Copy link

How much was the work you have put into this? Is there any way to pay you for maintaining Wheezy for another year until our migration to a newer platform is finished?

@nicko88
Copy link

nicko88 commented Oct 4, 2016

Is there a reason you can't just build the debs for Wheezy yourself?

I didn't find anything about it particularly difficult and everything just worked great.

You only have to build the packages once and then you can deploy them to all your machines running Wheezy (assuming they are all on the same Kernel)

https://github.com/zfsonlinux/zfs/wiki/Custom-Packages

@mailinglists35
Copy link

@nicko88 you can't produce dkms builds for wheezy, only kmods

@nicko88
Copy link

nicko88 commented Oct 6, 2016

I guess I didn't realize kmods was a problem.

It seemed to make sense that if you are maintaining ZFS on many Debian machines that building it once as kmod and installing those packages on all the machines would be easier.

@mailinglists35
Copy link

yes it would be easier until next kernel update when you'd have to rebuild & distribute again

@nicko88
Copy link

nicko88 commented Oct 6, 2016

But Debian only updates the kernel once every 2 years. Unless you are using backports I suppose but I think most people stick to the main kernel.

@FransUrbo
Copy link
Contributor

How much was the work you have put into this? Is there any way to pay you for maintaining Wheezy for another year until our migration to a newer platform is finished?

I've been thinking about this all week, but I just don't have the time!

I started a new job on Monday and I have my hands full at home with setting up my new Openstack cluster (which is/was supposed to give me more time to do ZoL development - oh, the irony!!).

I'm also busy trying to get my two major PRs in shape for merging by going through the reviews I've finally got on them..

So I have to say no :(. I simply don't have the time to do this.

@janmuennich
Copy link

No worries! I can totally understand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests