Re: dislocker package broken, fix in 'sid'. How long 'til in backports?

2020-02-03 Thread Greg Wooledge
On Sun, Feb 02, 2020 at 02:49:55PM -0500, Michael Bonert wrote:
> Thank you for the comments!  I emailed the developer.
> 
> As the dislocker packages don't seem to have dependencies - that aren't part
> of stable (buster),
> I decided to create a so-called "FrankenDebian" (
> https://wiki.debian.org/DontBreakDebian )

Why?

Just backport it yourself.



Re: dislocker package broken, fix in 'sid'. How long 'til in backports?

2020-02-02 Thread Michael Bonert

Thank you for the comments!  I emailed the developer.

As the dislocker packages don't seem to have dependencies - that  
aren't part of stable (buster),
I decided to create a so-called "FrankenDebian" (  
https://wiki.debian.org/DontBreakDebian )



Here is hack:

I downloaded the (amd64) debs:
 https://packages.debian.org/sid/amd64/dislocker/download
 https://packages.debian.org/sid/amd64/libdislocker0.7/download

I then in the directory of the '.deb's did this:
# apt install ./dislocker_0.7.1-5_amd64.deb
# apt install ./libdislocker0.7_0.7.1-5_amd64.deb

If done properly - you should see this with 'dpkg --list'
#  dpkg --list |grep dislocker
ii  dislocker  0.7.1-5  
amd64read/write encrypted BitLocker volumes
ii  libdislocker0.70.7.1-5  
amd64read/write encrypted BitLocker volumes  
(shared library)


dislocker now works for me. :-)


If there is an easier more elegant (less hack-ish) way to do the  
above... I am all ears.



Michael





Re: dislocker package broken, fix in 'sid'. How long 'til in backports?

2020-02-02 Thread Andrei POPESCU
On Du, 02 feb 20, 00:27:54, Michael Bonert wrote:
> I am running Debian stable (buster).
> 
> The dislocker backport doesn't work for files from Windows 10 1903 (as noted
> here: 
> https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1710592.html
> )

According to https://packages.debian.org/search?keywords=dislocker there 
is no backport for buster, only for stretch.
 
> I noted that the latest version of dislocker in 'sid' (unstable) is 0.7.1-5
> ( https://packages.debian.org/sid/utils/dislocker )
> 
> The release notes for 0.7.1-5 ( 
> https://metadata.ftp-master.debian.org/changelogs//main/d/dislocker/dislocker_0.7.1-5_changelog
> )
> say:  "Added new patches to support Support Windows 10 1903 and fix build
> issues.Thanks to haobinnan " - sounds like exactly what
> I'd like to have.
> 
> How long will it take for 0.7.1-5 to appear as a backport?

It has already migrated to testing (bullseye), so this is one 
pre-condition already fulfilled.

On the other hand buster has 0.7.1-4+b1. Depending on the complexity of 
the change it might qualify for a stable update (i.e. 
buster-proposed-updates and buster proper on the next point release).

You should ask the package maintainer(s) about their plans, if any.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature


Re: dislocker package broken, fix in 'sid'. How long 'til in backports?

2020-02-01 Thread Keith Bainbridge

On 2/2/20 4:27 pm, Michael Bonert wrote:

I am running Debian stable (buster).

The dislocker backport doesn't work for files from Windows 10 1903 (as 
noted here: 
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1710592.html 
)


I noted that the latest version of dislocker in 'sid' (unstable) is 
0.7.1-5 ( https://packages.debian.org/sid/utils/dislocker )


The release notes for 0.7.1-5 ( 
https://metadata.ftp-master.debian.org/changelogs//main/d/dislocker/dislocker_0.7.1-5_changelog 
)
say:  "Added new patches to support Support Windows 10 1903 and fix 
build issues.Thanks to haobinnan " - sounds like 
exactly what I'd like to have.


How long will it take for 0.7.1-5 to appear as a backport?

Thanks,
Michael

PS -
I will trying making my own backport ( 
https://wiki.debian.org/DontBreakDebian / 
https://wiki.debian.org/SimpleBackportCreation ) but prefer to avoid 
that... if isn't too long a wait.





Another suggestion I read somewhere is, include the src repo for sid in 
your sources-list. After an update, seems you will have the code to 
build it yourself, and ensure that you don't need anything untoward. 
Never tried it my self, but sounds interesting.


To answer you question directly, not long.I used a vbox to test 
upgrading from bullseye to sid, a couple of weeks ago, to see how much 
difference there is. About 20 packages.


--
Keith Bainbridge

keith.bainbridge.3...@gmail.com
0447 667 468



dislocker package broken, fix in 'sid'. How long 'til in backports?

2020-02-01 Thread Michael Bonert

I am running Debian stable (buster).

The dislocker backport doesn't work for files from Windows 10 1903 (as  
noted here:  
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1710592.html  
)


I noted that the latest version of dislocker in 'sid' (unstable) is  
0.7.1-5 ( https://packages.debian.org/sid/utils/dislocker )


The release notes for 0.7.1-5 (  
https://metadata.ftp-master.debian.org/changelogs//main/d/dislocker/dislocker_0.7.1-5_changelog  
)
say:  "Added new patches to support Support Windows 10 1903 and fix  
build issues.Thanks to haobinnan " - sounds like  
exactly what I'd like to have.


How long will it take for 0.7.1-5 to appear as a backport?

Thanks,
Michael

PS -
I will trying making my own backport (  
https://wiki.debian.org/DontBreakDebian /  
https://wiki.debian.org/SimpleBackportCreation ) but prefer to avoid  
that... if isn't too long a wait.