DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
deb http://ftp.debian.org/debian/ wheezy-backports main
Quote:
Dear users and supporters of the backports service!
The Backports Team is pleased to announce the next important step
on getting backports more integrated. People who are reading
debian-infrastructure-announce[1] will have seen that there was an
archive maintenance last weekend: starting with wheezy-backports the
packages will be accessible from the regular pool instead of a separate
one, and all backports uploads will be processed through the regular
upload queue (including those for squeeze-backports and
squeeze-backports-sloppy).
== For Users ==
What exactly does that mean for you? For users of wheezy, the
sources.list entry will be different, a simple substitute of squeeze
for wheezy won't work. The new format is:
So it is debian instead of debian-backports, and offered through the
regular mirror network. Feel invited to check your regular mirror if
it carries backports and pull from there.
== For Contributers ==
What does it mean for contributing developers? Uploads for backports
are no longer to be pushed to backports-master but to
ftp.upload.debian.org, like any other regular package. Also, given that
the packages are served from the same archive install there is no need
to include the original tarball in the upload any longer because the
archive knows it (Squeeze and beyond).
Also, given that the upload goes to the same upload queue, there is
only one keyring used anymore, so no more pain with expired or replaced
keys. We though still keep the rule of adding your UID to an ACL list
(this also includes DM additions). This is mostly only to give us the
chance to remind you that uploads to backports are directly available
for installation onto stable systems and you thus should take special
care there. We carefully tried to take over the old ACLs, in case you
can't upload anymore, please tell us[4] so we can look into the issue.
I've mentioned wheezy-backports (and squeeze-backports-sloppy) a few
times here already, and you might wonder when it will be available.
Technically, it is available from now on. Practically, while you could
already upload to it, the set up of the buildd network is more painful
than expected, so please allow the Buildd Team some days for setting
them up.
The upload rules for wheezy-backports are the same: packages that are
in the next suite are accepted. Given that Jessie isn't created yet, we
want you to think about whether the package you want to upload will go
into Jessie final, and that you are taking a closer look once Jessie is
created and the package entered there about the upgradeability. For the
time until the suite is available, you can see this as relaxed upload
rule.
The same goes for squeeze-backports-sloppy: packages from two suites
after Squeeze are acceptable, which turns it into the same relaxed rule
as wheezy-backports above. Please also keep in mind that uploads to
squeeze-backports-sloppy usually should be accompanied by uploads to
wheezy-backports so people are able to upgrade from
squeeze-backports-sloppy to wheezy with wheezy-backports.
== Thanks ==
Finally, we want to thank the FTP-Master Team for their fine work on
making this happen.
The documentation on backports-master[2] has been updated, and in
case of any doubt or question, feel free to ask them on either the
debian-backports mailinglist[3], or in case of sensitive topics ask
us[4] directly.
deb http://ftp.us.debian.org/debian/ wheezy main
deb-src http://ftp.us.debian.org/debian/ wheezy main
deb http://security.debian.org/ wheezy/updates main
deb-src http://security.debian.org/ wheezy/updates main
# wheezy-updates, previously known as 'volatile'
deb http://ftp.us.debian.org/debian/ wheezy-updates main
deb-src http://ftp.us.debian.org/debian/ wheezy-updates main
Last edited by JLndr; 07-19-2013 at 11:50 AM.
Reason: Small edit.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
A few months ago I commented out the deb-multimedia repositories and I don't seem to have any problems. I did so so that any dependency issues I had I could link definitively to the Debian repositories.
What do the deb-multimedia repositories contain nowadays that isn't in the main repositories?
Distribution: Debian Wheezy, Jessie, Sid/Experimental, playing with LFS.
Posts: 2,900
Rep:
libdvdcss2, w32-codecs and w64-codecs is all I can really think of off the top of my head that I need. There are other packages such as m4baker that are useful though if you are into making audiobooks that people with iProducts can use.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
Quote:
Originally Posted by k3lt01
libdvdcss2, w32-codecs and w64-codecs is all I can really think of off the top of my head that I need. There are other packages such as m4baker that are useful though if you are into making audiobooks that people with iProducts can use.
Thanks, it appears I may need to reinstate deb-multimedia then as I have the libdvdcss package still.
Distribution: Debian Wheezy, Jessie, Sid/Experimental, playing with LFS.
Posts: 2,900
Rep:
I created my own repo with reprepro and have that and other packages I need in it, saves having multiple repositories in my sources.list apart from the standard Debian repositories.
I'm running Debian Testing, with this fairly simple sources.list file:
Code:
deb http://ftp.be.debian.org/debian/ testing main contrib non-free
deb-src http://ftp.be.debian.org/debian/ testing main contrib non-free
deb http://security.debian.org/ testing/updates main contrib non-free
deb-src http://security.debian.org/ testing/updates main contrib non-free
deb http://ftp.be.debian.org/debian/ testing-updates main contrib non-free
deb-src http://ftp.be.debian.org/debian/ testing-updates main contrib non-free
In fact, I didn't create it manually, but I wrote a bash script that generated it for me (primarily as a learning exercise, really). The script assumes that, the first time you run it, the sources.list file has not been edited yet, and is exactly how the Debian installer created it. It saves a copy of the file, and then creates three additional versions, which look just like what I show above: the first version will use the current Debian release, the second one will use the "stable" distribution, and the third and final one (cfr. above) will use "testing". The script then lets you select which version you want to use, and set it up for you.
I'll attach a copy of the script to this post, just in case anyone is curious.
deb http://ftp.gr.debian.org/debian/ sid main non-free contrib
Feel a bit guilty about using non-free firmware but i am stuck with a laptop which leaves me no way around it.
At the risk of going offtopic - so I'll keep it short - your PC is already full of non-free firmware. In fact it's less free than the non-free firmware provided with the Linux kernel as most of it cannot be freely distributed. Firmware is loaded onto the device itself, it's not a Linux binary and cannot be executed by the OS.
So if you buy, for example, an Atheros wifi NIC and find that it does not require firmware - it probably does, but it's already on the device - same with your motherboard, same with optical drives, hard disk drives, etc.
Debian's stance on firmware is just silly and pedantic.
The non-free firmware might become easier in the future, splitting up non-free.
Quote:
1. Split up non-free?
---------------------
Yes - need to work out details.
This is an idea that various folks have been considering for a while,
and the ftpmasters have already said they're OK with. We need to work
out the exact details of the split, at the very least. Currently
suggested:
* Split non-free into non-free-firmware, non-free-doc,
non-free-other(?)
* Same split, but use "/" as a separator for $reasons
(non-free/firmware, non-free/doc, non-free-other(?), etc.)
but I heard multiple other options too. Splitting seems to be
generally accepted as a reasonable idea. This way, we'll be able to
allow people to *just* use non-free firmware on their machines without
adding extra pollution of non-free applications. But: what's a good
level of split? While we're doing this work anyway, I'd personally
like to have a non-free docs area too for things like GFDL docs and
RFCs; others suggested a non-free-drivers (e.g. for the Nvidia binary
drivers); somebody else suggested a total per-package split(!) to
allow maximum resolution. That seems likely to cause more harm than
good, so no! :-)
We should move ahead with this split, and work out the best way to
carve things up. Various tools that work on the archive (dak,
debian-cd, ...) will need to be updated to match the new layout,
obviously.
*IMPORTANT*: We need to make sure that the messaging about this split
is clear; just because we're splitting non-free firmware out of the
default non-free area, that doesn't mean that we're suddenly endorsing
it as a concept!
harry@biker:~
$ inxi -r
Repos: Active apt sources in file: /etc/apt/sources.list.d/antix.list
deb http://antix.daveserver.info/jessie jessie main nosystemd
Active apt sources in file: /etc/apt/sources.list.d/debian.list
deb http://ftp.us.debian.org/debian/ jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
harry@biker:~
$ cd /etc/apt/preferences.d
harry@biker:/etc/apt/preferences.d
$ ls
00systemd
harry@biker:/etc/apt/preferences.d
$ cat 00systemd
Package: *systemd*
Pin: origin ""
Pin-Priority: -1
harry@biker:/etc/apt/preferences.d
last part in code tags is to explain a little the nosystemd repo entry I have in my sources.list.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.