LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 12-27-2019, 06:51 PM   #1
floppy_stuttgart
Member
 
Registered: Nov 2010
Location: Stuttgart, Germany
Distribution: Debian like
Posts: 809
Blog Entries: 2

Rep: Reputation: 76
how to update my raspberry PI (still wheezy) ?


Hello,
I have following error after apt-get update:
Quote:
OK http://archive.raspberrypi.org wheezy Release.gpg
OK http://archive.raspberrypi.org wheezy Release
OK http://archive.raspberrypi.org wheezy/main armhf Packages
Ign http://archive.raspberrypi.org wheezy/main Translation-de_DE
Ign http://archive.raspberrypi.org wheezy/main Translation-de
Ign http://archive.raspberrypi.org wheezy/main Translation-en
Paketlisten werden gelesen... Fertig
W: Duplicate sources.list entry http://archive.raspberrypi.org/debian/ wheezy/main armhf Packages (/var/lib/apt/lists/archive.raspberrypi.org_debian_dists_wheezy_main_binary-armhf_Packages)
W: Probieren Sie »apt-get update«, um diese Probleme zu korrigieren.
Do you know how to solve this?
This is a small printer server running and running since months and years.
Due to the connection of a Win10 client to it, I have to start few updates (samba etc.).
I modified the sources because the old raspbian were not ok anymore. Now I am stuck at this.
Any help is very welcome (christmas time is IT-update time..).
 
Old 12-27-2019, 08:39 PM   #2
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 15,879
Blog Entries: 27

Rep: Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668
Debian Wheezy reached end of life some while ago.
 
Old 12-27-2019, 10:58 PM   #3
uteck
Member
 
Registered: Oct 2003
Location: Elgin,IL,USA
Distribution: GalliumOS on Chrombook
Posts: 335

Rep: Reputation: 63
You can upgrade to Debian 8 Jessie this way:
edit your /etc/apt/sources.list and change all the references from wheezy to jessie.
then 'apt-get update' 'apt-get upgrade' 'apt-get dist-upgrade'

Reboot and you should be on Debian 8, but that goes end of life in 6 months, so will want to upgrade to Strech for 2 more years of support. Just replace jessie with streach and run the commands again.
 
Old 12-28-2019, 06:42 AM   #4
floppy_stuttgart
Member
 
Registered: Nov 2010
Location: Stuttgart, Germany
Distribution: Debian like
Posts: 809

Original Poster
Blog Entries: 2

Rep: Reputation: 76
Quote:
Originally Posted by frankbell View Post
Thanks.
Is there any possibility to update my system to the latest released version of wheezy? (I understand now, I will have to upgrade later and should not keep that Wheezy for longer).
And: I will create in parallel a new SD card with the latest debian (it will take time for me to setup the whole system again; upgrading to Jessie from a Wheezy system with a broken "update" status is a kind of hot for me)
 
Old 12-28-2019, 08:52 AM   #5
michaelk
Moderator
 
Registered: Aug 2002
Posts: 19,533

Rep: Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139
What version of samba is currently running on your Pi and do you know it isn't the latest available in the Wheezy repositories? 3.5 or 3.6? Have you tried setting

max protocol = SMB2

As a work around if you have "control" of the Windows 10 computers you can print directly using cups ipp protocol instead of samba.
 
Old 12-28-2019, 12:28 PM   #6
floppy_stuttgart
Member
 
Registered: Nov 2010
Location: Stuttgart, Germany
Distribution: Debian like
Posts: 809

Original Poster
Blog Entries: 2

Rep: Reputation: 76
Quote:
Originally Posted by michaelk View Post
What version of samba is currently running on your Pi and do you know it isn't the latest available in the Wheezy repositories? 3.5 or 3.6? Have you tried setting

max protocol = SMB2

As a work around if you have "control" of the Windows 10 computers you can print directly using cups ipp protocol instead of samba.
Thanks.

VERSION OF SAMBA
aptitude versions samba
Quote:
Paket samba:
i 2:3.6.6-6+deb7u15 100

Paket samba-common:
i A 2:3.6.6-6+deb7u15 100

Paket samba-common-bin:
i 2:3.6.6-6+deb7u15
I dont know if this is the latest Wheezy version since I dont know where the Wheezy repositories are.

I dont see max protocol = SMB2 in /etc/samba/smb.conf so this is not implemented.
Where to include it? in the GLOBAL area of smb.conf?

The server has already several linux PCs and notebook connected to it. Preferably I would like not to change to CUPS IPP (perhaps I dont understand something here; I think I run CUPS SAMBA with all PCs but not sure how to check this).
 
Old 12-28-2019, 12:54 PM   #7
michaelk
Moderator
 
Registered: Aug 2002
Posts: 19,533

Rep: Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139
From what I can find that is the latest wheezy version. Yes that directive would go in the global section.
 
Old 12-28-2019, 06:25 PM   #8
floppy_stuttgart
Member
 
Registered: Nov 2010
Location: Stuttgart, Germany
Distribution: Debian like
Posts: 809

Original Poster
Blog Entries: 2

Rep: Reputation: 76
Quote:
Originally Posted by michaelk View Post
From what I can find that is the latest wheezy version. Yes that directive would go in the global section.
done. not much progress; so far, I achieved:
the printer is installed on the win10 client.
cups can be accessed via http://192.168.178.50:631/printers/Deskjet_2540 in a browser on the win10 client.
the test print fail.
I am starting the install of a newest debian version on the server in a separate SD of the raspPI server. will see if it helps. why?
according https://wiki.samba.org/index.php/Set...indows_Clients
Quote:
Supported Windows Printer Drivers

Samba only supports the printer driver model version 3 that is supported in Windows 2000 to 10 and Windows Server 2000 to 2016.

To use package-aware drivers:

Run Samba 4.7 and later
Enable the spoolssd service. For details, see Enabling the spoolssd Service.

The driver model version 4, introduced in Windows 8 and Windows Server 2012, is not supported in Samba. Use version 3 drivers instead.
any advise is welcome.
 
Old 12-28-2019, 08:54 PM   #9
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 15,879
Blog Entries: 27

Rep: Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668
Quote:
Is there any possibility to update my system to the latest released version of wheezy? (I understand now, I will have to upgrade later and should not keep that Wheezy for longer).

Wheezy has been EOL for so long that attempting to do that would probably not be feasible.
 
Old 12-29-2019, 06:07 AM   #10
pan64
LQ Guru
 
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 13,599

Rep: Reputation: 4358Reputation: 4358Reputation: 4358Reputation: 4358Reputation: 4358Reputation: 4358Reputation: 4358Reputation: 4358Reputation: 4358Reputation: 4358Reputation: 4358
yes, better to use a new version, without upgrade. But I'm afraid you still need to play with the protocol/interface to make it work.
 
Old 12-29-2019, 07:28 AM   #11
michaelk
Moderator
 
Registered: Aug 2002
Posts: 19,533

Rep: Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139
Here is how to setup ipp printer
https://zedt.eu/tech/windows/install...in-windows-10/
 
Old 12-29-2019, 10:10 AM   #12
floppy_stuttgart
Member
 
Registered: Nov 2010
Location: Stuttgart, Germany
Distribution: Debian like
Posts: 809

Original Poster
Blog Entries: 2

Rep: Reputation: 76
Quote:
Originally Posted by michaelk View Post
Thanks.
I am still looking at the configuration of SAMBA. Who knows..
My smb.conf file is below. if anybody has a working conf file with win10 PCs, I would appreciate a posting here.

Quote:
[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
server string = %h server

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = yes
wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
#; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Cap the size of the individual log files (in KiB).
max log size = 1000

# include this according https://www.linuxquestions.org/quest...zy-4175666641/
max protocol = SMB2

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
# security = user

# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam

obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
printing = cups
printcap name = cups

############ Misc ############
; include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
# domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes

# added according https://wiki.samba.org/index.php/Set...oolssd_Service
rpc_server:spoolss = external
rpc_daemon:spoolssd = fork

#======================= Share Definitions =======================

[homes]
comment = Home Directories
browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
# guest ok = no
guest ok = yes
read only = yes
create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes

# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom
 
Old 12-29-2019, 02:28 PM   #13
michaelk
Moderator
 
Registered: Aug 2002
Posts: 19,533

Rep: Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139Reputation: 3139
As a frame of reference although it isn't a Pi I do have a debian wheezy virtual machine that I still keep around that was up to date at EOL with samba version 3.6.6. I added max protocol = SMB2 and I was able to connect from a Windows 10 PC by manually typing the URL in the Windows file browser.

What do you mean by "the old raspbian were not ok anymore"? Microsoft removed support for SMB version 1 which also removed netbios network browsing.

https://support.microsoft.com/en-us/...ult-in-windows
 
Old 12-30-2019, 03:29 AM   #14
floppy_stuttgart
Member
 
Registered: Nov 2010
Location: Stuttgart, Germany
Distribution: Debian like
Posts: 809

Original Poster
Blog Entries: 2

Rep: Reputation: 76
finally, the access was wrong to the raspberry pi: by giving the correct link in the win10 machine, with an user name and password, it works.
the link I putted in the win10 menue for printer installation is

Code:
http://anuserwithaccessto_server:passwordofthatuser@192.168.178.xx:631/printers/Deskjet_88888
(the previous link was without
Code:
"anuserwithaccessto_server:passwordofthatuser@"
)

print page is out.
job done.
thanks to all for the helps and remarks and hints
(no need to upgrade my raspberry pi with > Wheezy for the next 20years.. wheezy will stay.. other things in life to do.. next task identified).

Last edited by floppy_stuttgart; 12-30-2019 at 03:33 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Raspberry Pi: Combine a Raspberry Pi with up to 4 Raspberry Pi Zeros for less than US$50 with the Cluster HAT LXer Syndicated Linux News 0 07-05-2019 01:03 PM
[SOLVED] How do I update Squeeze to Wheezy when I can't update? jbruyet Linux - Software 15 08-22-2014 02:29 AM
[SOLVED] Now I've done it - Debian dual boot (Sid, Wheezy) grub overwritten, lost Wheezy? ShaneRoach Debian 23 02-02-2014 03:28 PM
Finding Module Dependencies...(Still loading...still loading..still loading..HANG!!!) Aeudian Linux - General 3 08-11-2003 04:31 PM
Finding Module Dependencies.....(still loading....Still loading....still loading) Aeudian Linux - Newbie 1 07-28-2003 03:27 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 10:16 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration